Building a Bitcoin Mining Business: The Ultimate List of ...
Ultimate glossary of crypto currency terms, acronyms and abbreviations
Technical: A Brief History of Payment Channels: from Satoshi to Lightning Network
Who cares about political tweets from some random country's president when payment channels are a much more interesting and are actually capable of carrying value? So let's have a short history of various payment channel techs!
Generation 0: Satoshi's Broken nSequence Channels
Because Satoshi's Vision included payment channels, except his implementation sucked so hard we had to go fix it and added RBF as a by-product. Originally, the plan for nSequence was that mempools would replace any transaction spending certain inputs with another transaction spending the same inputs, but only if the nSequence field of the replacement was larger. Since 0xFFFFFFFF was the highest value that nSequence could get, this would mark a transaction as "final" and not replaceable on the mempool anymore. In fact, this "nSequence channel" I will describe is the reason why we have this weird rule about nLockTime and nSequence. nLockTime actually only works if nSequence is not 0xFFFFFFFF i.e. final. If nSequence is 0xFFFFFFFF then nLockTime is ignored, because this if the "final" version of the transaction. So what you'd do would be something like this:
You go to a bar and promise the bartender to pay by the time the bar closes. Because this is the Bitcoin universe, time is measured in blockheight, so the closing time of the bar is indicated as some future blockheight.
For your first drink, you'd make a transaction paying to the bartender for that drink, paying from some coins you have. The transaction has an nLockTime equal to the closing time of the bar, and a starting nSequence of 0. You hand over the transaction and the bartender hands you your drink.
For your succeeding drink, you'd remake the same transaction, adding the payment for that drink to the transaction output that goes to the bartender (so that output keeps getting larger, by the amount of payment), and having an nSequence that is one higher than the previous one.
Eventually you have to stop drinking. It comes down to one of two possibilities:
You drink until the bar closes. Since it is now the nLockTime indicated in the transaction, the bartender is able to broadcast the latest transaction and tells the bouncers to kick you out of the bar.
You wisely consider the state of your liver. So you re-sign the last transaction with a "final" nSequence of 0xFFFFFFFF i.e. the maximum possible value it can have. This allows the bartender to get his or her funds immediately (nLockTime is ignored if nSequence is 0xFFFFFFFF), so he or she tells the bouncers to let you out of the bar.
Now that of course is a payment channel. Individual payments (purchases of alcohol, so I guess buying coffee is not in scope for payment channels). Closing is done by creating a "final" transaction that is the sum of the individual payments. Sure there's no routing and channels are unidirectional and channels have a maximum lifetime but give Satoshi a break, he was also busy inventing Bitcoin at the time. Now if you noticed I called this kind of payment channel "broken". This is because the mempool rules are not consensus rules, and cannot be validated (nothing about the mempool can be validated onchain: I sigh every time somebody proposes "let's make block size dependent on mempool size", mempool state cannot be validated by onchain data). Fullnodes can't see all of the transactions you signed, and then validate that the final one with the maximum nSequence is the one that actually is used onchain. So you can do the below:
Become friends with Jihan Wu, because he owns >51% of the mining hashrate (he totally reorged Bitcoin to reverse the Binance hack right?).
Slip Jihan Wu some of the more interesting drinks you're ordering as an incentive to cooperate with you. So say you end up ordering 100 drinks, you split it with Jihan Wu and give him 50 of the drinks.
When the bar closes, Jihan Wu quickly calls his mining rig and tells them to mine the version of your transaction with nSequence 0. You know, that first one where you pay for only one drink.
Because fullnodes cannot validate nSequence, they'll accept even the nSequence=0 version and confirm it, immutably adding you paying for a single alcoholic drink to the blockchain.
The bartender, pissed at being cheated, takes out a shotgun from under the bar and shoots at you and Jihan Wu.
Jihan Wu uses his mystical chi powers (actually the combined exhaust from all of his mining rigs) to slow down the shotgun pellets, making them hit you as softly as petals drifting in the wind.
The bartender mutters some words, clothes ripping apart as he or she (hard to believe it could be a she but hey) turns into a bear, ready to maul you for cheating him or her of the payment for all the 100 drinks you ordered from him or her.
Steely-eyed, you stand in front of the bartender-turned-bear, daring him to touch you. You've watched Revenant, you know Leonardo di Caprio could survive a bear mauling, and if some posh actor can survive that, you know you can too. You make a pose. "Drunken troll logic attack!"
I think I got sidetracked here.
Bears are bad news.
You can't reasonably invoke "Satoshi's Vision" and simultaneously reject the Lightning Network because it's not onchain. Satoshi's Vision included a half-assed implementation of payment channels with nSequence, where the onchain transaction represented multiple logical payments, exactly what modern offchain techniques do (except modern offchain techniques actually work). nSequence (the field, but not its modern meaning) has been in Bitcoin since BitCoin For Windows Alpha 0.1.0. And its original intent was payment channels. You can't get nearer to Satoshi's Vision than being a field that Satoshi personally added to transactions on the very first public release of the BitCoin software, like srsly.
Miners can totally bypass mempool rules. In fact, the reason why nSequence has been repurposed to indicate "optional" replace-by-fee is because miners are already incentivized by the nSequence system to always follow replace-by-fee anyway. I mean, what do you think those drinks you passed to Jihan Wu are, other than the fee you pay him to mine a specific version of your transaction?
Satoshi made mistakes. The original design for nSequence is one of them. Today, we no longer use nSequence in this way. So diverging from Satoshi's original design is part and parcel of Bitcoin development, because over time, we learn new lessons that Satoshi never knew about. Satoshi was an important landmark in this technology. He will not be the last, or most important, that we will remember in the future: he will only be the first.
Incentive-compatible time-limited unidirectional channel; or, Satoshi's Vision, Fixed (if transaction malleability hadn't been a problem, that is). Now, we know the bartender will turn into a bear and maul you if you try to cheat the payment channel, and now that we've revealed you're good friends with Jihan Wu, the bartender will no longer accept a payment channel scheme that lets one you cooperate with a miner to cheat the bartender. Fortunately, Jeremy Spilman proposed a better way that would not let you cheat the bartender. First, you and the bartender perform this ritual:
You get some funds and create a transaction that pays to a 2-of-2 multisig between you and the bartender. You don't broadcast this yet: you just sign it and get its txid.
You create another transaction that spends the above transaction. This transaction (the "backoff") has an nLockTime equal to the closing time of the bar, plus one block. You sign it and give this backoff transaction (but not the above transaction) to the bartender.
The bartender signs the backoff and gives it back to you. It is now valid since it's spending a 2-of-2 of you and the bartender, and both of you have signed the backoff transaction.
Now you broadcast the first transaction onchain. You and the bartender wait for it to be deeply confirmed, then you can start ordering.
The above is probably vaguely familiar to LN users. It's the funding process of payment channels! The first transaction, the one that pays to a 2-of-2 multisig, is the funding transaction that backs the payment channel funds. So now you start ordering in this way:
For your first drink, you create a transaction spending the funding transaction output and sending the price of the drink to the bartender, with the rest returning to you.
You sign the transaction and pass it to the bartender, who serves your first drink.
For your succeeding drinks, you recreate the same transaction, adding the price of the new drink to the sum that goes to the bartender and reducing the money returned to you. You sign the transaction and give it to the bartender, who serves you your next drink.
At the end:
If the bar closing time is reached, the bartender signs the latest transaction, completing the needed 2-of-2 signatures and broadcasting this to the Bitcoin network. Since the backoff transaction is the closing time + 1, it can't get used at closing time.
If you decide you want to leave early because your liver is crying, you just tell the bartender to go ahead and close the channel (which the bartender can do at any time by just signing and broadcasting the latest transaction: the bartender won't do that because he or she is hoping you'll stay and drink more).
If you ended up just hanging around the bar and never ordering, then at closing time + 1 you broadcast the backoff transaction and get your funds back in full.
Now, even if you pass 50 drinks to Jihan Wu, you can't give him the first transaction (the one which pays for only one drink) and ask him to mine it: it's spending a 2-of-2 and the copy you have only contains your own signature. You need the bartender's signature to make it valid, but he or she sure as hell isn't going to cooperate in something that would lose him or her money, so a signature from the bartender validating old state where he or she gets paid less isn't going to happen. So, problem solved, right? Right? Okay, let's try it. So you get your funds, put them in a funding tx, get the backoff tx, confirm the funding tx... Once the funding transaction confirms deeply, the bartender laughs uproariously. He or she summons the bouncers, who surround you menacingly. "I'm refusing service to you," the bartender says. "Fine," you say. "I was leaving anyway;" You smirk. "I'll get back my money with the backoff transaction, and posting about your poor service on reddit so you get negative karma, so there!" "Not so fast," the bartender says. His or her voice chills your bones. It looks like your exploitation of the Satoshi nSequence payment channel is still fresh in his or her mind. "Look at the txid of the funding transaction that got confirmed." "What about it?" you ask nonchalantly, as you flip open your desktop computer and open a reputable blockchain explorer. What you see shocks you. "What the --- the txid is different! You--- you changed my signature?? But how? I put the only copy of my private key in a sealed envelope in a cast-iron box inside a safe buried in the Gobi desert protected by a clan of nomads who have dedicated their lives and their childrens' lives to keeping my private key safe in perpetuity!" "Didn't you know?" the bartender asks. "The components of the signature are just very large numbers. The sign of one of the signature components can be changed, from positive to negative, or negative to positive, and the signature will remain valid. Anyone can do that, even if they don't know the private key. But because Bitcoin includes the signatures in the transaction when it's generating the txid, this little change also changes the txid." He or she chuckles. "They say they'll fix it by separating the signatures from the transaction body. They're saying that these kinds of signature malleability won't affect transaction ids anymore after they do this, but I bet I can get my good friend Jihan Wu to delay this 'SepSig' plan for a good while yet. Friendly guy, this Jihan Wu, it turns out all I had to do was slip him 51 drinks and he was willing to mine a tx with the signature signs flipped." His or her grin widens. "I'm afraid your backoff transaction won't work anymore, since it spends a txid that is not existent and will never be confirmed. So here's the deal. You pay me 99% of the funds in the funding transaction, in exchange for me signing the transaction that spends with the txid that you see onchain. Refuse, and you lose 100% of the funds and every other HODLer, including me, benefits from the reduction in coin supply. Accept, and you get to keep 1%. I lose nothing if you refuse, so I won't care if you do, but consider the difference of getting zilch vs. getting 1% of your funds." His or her eyes glow. "GENUFLECT RIGHT NOW." Lesson learned?
Payback's a bitch.
Transaction malleability is a bitchier bitch. It's why we needed to fix the bug in SegWit. Sure, MtGox claimed they were attacked this way because someone kept messing with their transaction signatures and thus they lost track of where their funds went, but really, the bigger impetus for fixing transaction malleability was to support payment channels.
Yes, including the signatures in the hash that ultimately defines the txid was a mistake. Satoshi made a lot of those. So we're just reiterating the lesson "Satoshi was not an infinite being of infinite wisdom" here. Satoshi just gets a pass because of how awesome Bitcoin is.
CLTV-protected Spilman Channels
Using CLTV for the backoff branch. This variation is simply Spilman channels, but with the backoff transaction replaced with a backoff branch in the SCRIPT you pay to. It only became possible after OP_CHECKLOCKTIMEVERIFY (CLTV) was enabled in 2015. Now as we saw in the Spilman Channels discussion, transaction malleability means that any pre-signed offchain transaction can easily be invalidated by flipping the sign of the signature of the funding transaction while the funding transaction is not yet confirmed. This can be avoided by simply putting any special requirements into an explicit branch of the Bitcoin SCRIPT. Now, the backoff branch is supposed to create a maximum lifetime for the payment channel, and prior to the introduction of OP_CHECKLOCKTIMEVERIFY this could only be done by having a pre-signed nLockTime transaction. With CLTV, however, we can now make the branches explicit in the SCRIPT that the funding transaction pays to. Instead of paying to a 2-of-2 in order to set up the funding transaction, you pay to a SCRIPT which is basically "2-of-2, OR this singlesig after a specified lock time". With this, there is no backoff transaction that is pre-signed and which refers to a specific txid. Instead, you can create the backoff transaction later, using whatever txid the funding transaction ends up being confirmed under. Since the funding transaction is immutable once confirmed, it is no longer possible to change the txid afterwards.
Todd Micropayment Networks
The old hub-spoke model (that isn't how LN today actually works). One of the more direct predecessors of the Lightning Network was the hub-spoke model discussed by Peter Todd. In this model, instead of payers directly having channels to payees, payers and payees connect to a central hub server. This allows any payer to pay any payee, using the same channel for every payee on the hub. Similarly, this allows any payee to receive from any payer, using the same channel. Remember from the above Spilman example? When you open a channel to the bartender, you have to wait around for the funding tx to confirm. This will take an hour at best. Now consider that you have to make channels for everyone you want to pay to. That's not very scalable. So the Todd hub-spoke model has a central "clearing house" that transport money from payers to payees. The "Moonbeam" project takes this model. Of course, this reveals to the hub who the payer and payee are, and thus the hub can potentially censor transactions. Generally, though, it was considered that a hub would more efficiently censor by just not maintaining a channel with the payer or payee that it wants to censor (since the money it owned in the channel would just be locked uselessly if the hub won't process payments to/from the censored user). In any case, the ability of the central hub to monitor payments means that it can surveill the payer and payee, and then sell this private transactional data to third parties. This loss of privacy would be intolerable today. Peter Todd also proposed that there might be multiple hubs that could transport funds to each other on behalf of their users, providing somewhat better privacy. Another point of note is that at the time such networks were proposed, only unidirectional (Spilman) channels were available. Thus, while one could be a payer, or payee, you would have to use separate channels for your income versus for your spending. Worse, if you wanted to transfer money from your income channel to your spending channel, you had to close both and reshuffle the money between them, both onchain activities.
Poon-Dryja Lightning Network
Bidirectional two-participant channels. The Poon-Dryja channel mechanism has two important properties:
No time limit.
Both the original Satoshi and the two Spilman variants are unidirectional: there is a payer and a payee, and if the payee wants to do a refund, or wants to pay for a different service or product the payer is providing, then they can't use the same unidirectional channel. The Poon-Dryjam mechanism allows channels, however, to be bidirectional instead: you are not a payer or a payee on the channel, you can receive or send at any time as long as both you and the channel counterparty are online. Further, unlike either of the Spilman variants, there is no time limit for the lifetime of a channel. Instead, you can keep the channel open for as long as you want. Both properties, together, form a very powerful scaling property that I believe most people have not appreciated. With unidirectional channels, as mentioned before, if you both earn and spend over the same network of payment channels, you would have separate channels for earning and spending. You would then need to perform onchain operations to "reverse" the directions of your channels periodically. Secondly, since Spilman channels have a fixed lifetime, even if you never used either channel, you would have to periodically "refresh" it by closing it and reopening. With bidirectional, indefinite-lifetime channels, you may instead open some channels when you first begin managing your own money, then close them only after your lawyers have executed your last will and testament on how the money in your channels get divided up to your heirs: that's just two onchain transactions in your entire lifetime. That is the potentially very powerful scaling property that bidirectional, indefinite-lifetime channels allow. I won't discuss the transaction structure needed for Poon-Dryja bidirectional channels --- it's complicated and you can easily get explanations with cute graphics elsewhere. There is a weakness of Poon-Dryja that people tend to gloss over (because it was fixed very well by RustyReddit):
You have to store all the revocation keys of a channel. This implies you are storing 1 revocation key for every channel update, so if you perform millions of updates over your entire lifetime, you'd be storing several megabytes of keys, for only a single channel. RustyReddit fixed this by requiring that the revocation keys be generated from a "Seed" revocation key, and every key is just the application of SHA256 on that key, repeatedly. For example, suppose I tell you that my first revocation key is SHA256(SHA256(seed)). You can store that in O(1) space. Then for the next revocation, I tell you SHA256(seed). From SHA256(key), you yourself can compute SHA256(SHA256(seed)) (i.e. the previous revocation key). So you can remember just the most recent revocation key, and from there you'd be able to compute every previous revocation key. When you start a channel, you perform SHA256 on your seed for several million times, then use the result as the first revocation key, removing one layer of SHA256 for every revocation key you need to generate. RustyReddit not only came up with this, but also suggested an efficient O(log n) storage structure, the shachain, so that you can quickly look up any revocation key in the past in case of a breach. People no longer really talk about this O(n) revocation storage problem anymore because it was solved very very well by this mechanism.
Another thing I want to emphasize is that while the Lightning Network paper and many of the earlier presentations developed from the old Peter Todd hub-and-spoke model, the modern Lightning Network takes the logical conclusion of removing a strict separation between "hubs" and "spokes". Any node on the Lightning Network can very well work as a hub for any other node. Thus, while you might operate as "mostly a payer", "mostly a forwarding node", "mostly a payee", you still end up being at least partially a forwarding node ("hub") on the network, at least part of the time. This greatly reduces the problems of privacy inherent in having only a few hub nodes: forwarding nodes cannot get significantly useful data from the payments passing through them, because the distance between the payer and the payee can be so large that it would be likely that the ultimate payer and the ultimate payee could be anyone on the Lightning Network. Lessons learned?
We can decentralize if we try hard enough!
"Hubs bad" can be made "hubs good" if everybody is a hub.
Smart people can solve problems. It's kinda why they're smart.
After LN, there's also the Decker-Wattenhofer Duplex Micropayment Channels (DMC). This post is long enough as-is, LOL. But for now, it uses a novel "decrementing nSequence channel", using the new relative-timelock semantics of nSequence (not the broken one originally by Satoshi). It actually uses multiple such "decrementing nSequence" constructs, terminating in a pair of Spilman channels, one in both directions (thus "duplex"). Maybe I'll discuss it some other time. The realization that channel constructions could actually hold more channel constructions inside them (the way the Decker-Wattenhofer puts a pair of Spilman channels inside a series of "decrementing nSequence channels") lead to the further thought behind Burchert-Decker-Wattenhofer channel factories. Basically, you could host multiple two-participant channel constructs inside a larger multiparticipant "channel" construct (i.e. host multiple channels inside a factory). Further, we have the Decker-Russell-Osuntokun or "eltoo" construction. I'd argue that this is "nSequence done right". I'll write more about this later, because this post is long enough. Lessons learned?
Bitcoin offchain scaling is more powerful than you ever thought.
In this short post I want to set out my case for the moral justifiability of 51% attacks against proof of work cryptocurrencies. In the past, a 51% attack was a theoretical construct that most people didn´t seem to think would be practically achievable or lucrative. This has now changed, as hashpower can be rented on sites like Nicehash and Mining Rig Rentals for a few hours at a time. The attack delivers the attacker two prominent opportunities: -You can orphan blocks of ¨legitimate¨ miners. This essentially means that whatever work was produced by legitimate miners during your attack became worthless. Mine a secret chain of two hours worth of blocks, release it and you orphaned 2 hours worth of blocks by your competitors. By the time most of the miners have noticed their blocks were orphaned in an attack, their nodes will have been automatically mining on your own chain for a while and it will be too late for them to do anything about it. The amount of money they lost would be equivalent to the amount you had to spend to produce your chain. Because mining is an industry with tight margins, the economic impact on these miners can be very big. The cost may be sufficient in case of a very long attack, to persuade them to quit their endeavor and get a real job. -The more important opportunity is that you´re able to double spend your coins. This is potentially, incredibly lucrative. How lucrative it is tends to depend primarily on the inflation rate of a cryptocurrency. A low inflation rate means relatively little ¨work¨ is done to maintain the security of the system. A high inflation rate on the other hand, turns the cryptocurrency into a very poor long-term investment. As a consequence, most cryptocurrencies face declining inflation rates, that delay the problem of their ultimately unsustainability into the future. The bank of international settlements explains this issue here. When it comes to the moral justification of a 51% attack, we first have to ask ourselves why proof of work is morally unjustifiable. There are two main reasons for this: -Proof of work has an enormous environmental impact, that ensures future generations will have to deal with the dramatic consequences of climate change. There is no proper justification for this environmental impact, as it delivers no clear benefits over existing payment systems other than the ability to carry out morally unjustifiable actions like blackmail. -Proof of work is fundamentally unsustainable, because of the economic burden it places on participants in cryptocurrency schemes. Cryptocurrencies can´t produce wealth out of thin air. The people who get rich from a cryptocurrency becomes rich, due to the fact that other people step in later. In this sense we´re dealing with a pyramid scheme, but the difference from regular pyramid schemes lies in the fact that huge sums of wealth are not merely redistributed, but destroyed, to sustain the scheme. The cost of the work to sustain the scheme is bigger than you might expect, because the reality is that relatively little money has entered bitcoin. JP Morgan claims that for the crypto assets at large, a fiat amplifier of 117.5 is present, as a purported $2 billion in net inflow pushed Bitcoin’s market capitalization from $15 billion to $250 billion. You have to consider that the Digiconomist estimates that $2.6 billion dollar leaves the Bitcoin scheme on an annual basis, in the form of mining costs to sustain Bitcoin. The vast majority of retail customers who entered this scheme ended up losing money from it. In some cases this lead to suicides. The fact that proof of work is morally unjustifiable doesn´t directly lead to a moral justification for a 51% attack. After all a sane society would use government intervention to eliminate the decentralized ponzi schemes that are cryptocurrencies. There are a few things that need to be considered however: -Governments have so far failed in their responsibility to address the cryptocurrency schemes. Instead you tend to see officials insist that proof of work might suck and most cryptocurrency is a scam, but ¨blockchain technology¨ will somehow change the world for the better. Most libertarians who saw these schemes emerge insisted that it´s stupid to participate in them because the government would eventually ban them and round up the people who participated in them. This didn´t happen because of the logistical difficulty of suppressing these schemes (anyone with an internet connection can set one up) as well as the fact that suppressing them would lend credence to the anti-government anarcho-capitalist ideology on which these schemes are based. Goverments might say ¨these schemes facilitate crime, ruin the environment and redistribute wealth from naive individuals to scammers¨, but anarcho-capitalists would insist that governments have grown so tyrannical that they want to ban you from exchanging numbers on computers. -Because cryptocurrency is fundamentally an online social arrangement, governments have very limited influence over the phenomenon. Binance seeks to become a stateless organization, not subject to the jurisdiction of any particular government. Just as with regular money laundering and tax evasion that hides in small nations that can earn huge sums of money by facilitating these practises, governments are dependent on the actions of individuals to address these practices. Whistleblowers released the panama papers and the tax evasion by German individuals through Swiss bank accounts. Through such individuals, the phenomenon could be properly addressed. In a similar manner, cryptocurrency schemes will need to be addressed through the actions of individuals who recognize the damage these schemes cause to the fabric of society. -The very nature of a 51% attack means that it primarily punishes those who set up and facilitate the cryptocurrency scheme in the first place. The miners who pollute our environment to satiate their own greed are bankrupted by the fact that their blocks are orphaned. The exchange operators are bankrupted due to double-spend attacks against the scams that they facilitate. When this happens, the cryptocurrency in question should lose value, which then destroys the incentive to devote huge sums of electricity to it. Finally, there´s the question of whether 51% attacks are viable as a response to cryptocurrency. There´s the obvious problem you run into, that the biggest and oldest scams are the most difficult to shut down. In addition, cryptocurrencies that fell victim to an attack tend to move towards a checkpoint system. However, there are a few things that need to be considered here: -51% attacks against small cryptocurrencies might not have a huge impact, but their benefit is nonetheless apparent. Most of the new scams don´t require participants to mine, instead the new schemes generally depend on ¨staking¨. If people had not engage in 51% attacks, the environmental impact would have been even bigger now. -51% attacks against currencies that implement checkpointing are not impossible, if the checkpoints are decentrally produced. What happens in that case is a chain split, as long as the hostile chain is released at the right time. This would mean that different exchanges may get stuck on different forks, which would still allow people to double spend their cryptocurrency. -There are other attacks that can be used against proof of work cryptocurrencies. The most important one is the block withholding attack. It´s possible for people who dislike a cryptocurrency to join a pool and to start mining. However, whenever the miner finds a valid solution that would produce a block, he fails to share the solution with the pool. This costs money for the pool operator, but it can be lucrative for the actor if he also operates a competing pool himself. In the best case it leads to miners moving to his pool, which then potentially allows him to execute a 51% attack against the cryptocurrency. -It´s possible to put up a 51% attack bounty, allowing others to do the work for you. This works as following. You make transaction A : 100 bitcoin to exchange X, for a fee of 0.001 BTC. Once this transaction has been included in a block, you immediately broadcast a conflicting transaction with another node: You´ŕe sending those 100 bitcoin to your own wallet, but you´re also including a 50 bitcoin fee for the miners. The miners now have a strong incentive to disregard the valid chain and to start mining a new chain on an older block that can still include your conflicting transaction. Provided that pool operators are rational economic agents, they should grab the opportunity. -Selfish mining in combination with a Sybil attack allows someone to eclipse the rest of the network, while controlling less than 51% of the hashrate. Your malicious nodes will simply refuse to propagante blocks of your competitors, thereby giving you more time to release your own block. Selfish mining will always be possible with 33% of the hashrate and as far as I can tell there are no pathways known currently to make the scheme impossible for people with 25% of the hashrate. This potentially makes a 51% attacks lucrative without having to carry out double-spend attacks against exchanges. Although double spending is a form of theft, it´s not clear to me whether a selfish mining attack would get you into legal trouble or not.
The dreaded 51% attack is a morally justifiable and potentially lucrative solution to the Nakamoto scheme.
Retailers Around The World That Accept Crypto, From Pizza to Travel
News by Cointelegraph: Jinia Shawdagor Earlier on, when Bitcoin (BTC) arrived on the scene, most cryptocurrency enthusiasts held on to their coins, as there were only so many places they could be spent. Nowadays, the list of marketplaces and retailers accepting Bitcoin and other cryptocurrencies is significantly larger, providing crypto enthusiasts with more options for making real-world purchases. After all, with recognizable organizations like Microsoft and Wikipedia now accepting Bitcoin as payment, conversations about Bitcoin and the power of cryptocurrencies are becoming more prominent. Currently, several fast-food restaurants and coffee shops have started accepting Bitcoin as payment. This will likely provide traction for mass adoption as cryptocurrency payments become increasingly commonplace in day-to-day purchases. Granted, there are some jurisdictions that do not consider Bitcoin or any other cryptocurrency as legal tender. Despite this set back, even big tech companies like Facebook are coming up with payment systems that mimic cryptocurrencies. Here are some of the leading retailers, merchants and companies that will let you book flights and hotels, buy coffee or pizza, or even go to space with crypto.
Pay for a burger in Germany with crypto
The German branch of fast-food restaurant chain Burger King now claims to accept Bitcoin as payment for its online orders and deliveries, but this is not the first time Burger King has warmed up to Bitcoin as a form of payment. The company, headquartered in Florida in the United States, had its Russian branch announce in 2017 that it would start accepting Bitcoin payments, but it ultimately did not take off. The global fast-food retailer reports an annual revenue of about $20 billion and serves about 11 million customers around the world. If all its outlets move to accept Bitcoin as payment, cryptocurrency adoption would inevitably spread.
Spend crypto at Starbucks and other places
For crypto payments to gain traction, merchants need to implement systems that enable swift and easy cryptocurrency spending. Starbucks is one of the companies taking advantage of this concept through Flexa, a U.S.-based payment startup that is helping the cafe giant, as well as dozens of other companies, accept cryptocurrency payments. The company developed an app called Spedn that enables crypto holders to make purchases with merchants like Starbucks. The company’s CEO believes that by making cryptocurrencies spendable in the mainstream, commerce will realize the full benefit of blockchain technology all over the world. Crypto enthusiasts in Silicon Valley’s Palo Alto might already be familiar with Coupa Cafe for other reasons apart from its coffee and food. Through its partnership with a Facebook software developer, Coupa Cafe has been accepting Bitcoin as payment since 2013. Reports show that the cafe received a steady stream of Bitcoin revenue as soon as they started implementing crypto payments — a clear sign of how eager its customers were to pay in Bitcoin. Coupa Cafe is among the few physical businesses in Palo Alto that accept Bitcoin at the moment. The cafe owners believe that their collaboration with the Facebook software engineer will create more traction in terms of Bitcoin adoption.
Buy food with crypto
With over 50,000 takeaway restaurants listed on its United Kingdom-based site, OrderTakeaways is one of the surest ways to get a pizza paid for with crypto delivered to your doorstep. The company has been accepting Bitcoin payments for online takeout orders since 2018. And other similar services include the Korean platform Shuttledelivery as well as German-based service Lieferando and its subsidiaries in several other countries. Apart from online orders, crypto can also be spent at a regular Subway restaurants. As early as 2013, several Subway branches started accepting Bitcoin as payment. Now, for a fraction of a Bitcoin, a Subway sandwich can be purchased at select restaurants.
Pay with Bitcoin to tour space
Besides buying food and inexpensive, day-to-day items with crypto, a trip to space can now be bought with Bitcoin. That’s right. Richard Branson’s space tourism company, Virgin Galactic, started accepting Bitcoin as payment as far back as 2013. Although Branson’s predicted date for the first commercial flight has been pushed back several times, the company achieved its first suborbital space flight last year. Perhaps soon, people will be able to tour the moon on crypto’s dime.
Buy jewelry with Bitcoin
A brick-and-mortar American jewelry company called Reeds Jewelers accepts Bitcoin for both its physical and online stores. What’s more, if a purchase is worth more than $25,000, the company provides free armored delivery for safety. Other jewelry companies accepting Bitcoin include Blue Nile Jewelry, Stephen Silver Fine Jewelry and Coaex Jewelry, to name a few. A big advantage of purchasing large ticket items — like a diamond — with crypto is that it makes moving around large amounts of money cheap and effortless. Reports show that more Silicon Valley investors are buying jewelry with Bitcoin. Last year, Stephen Silver Fine Jewelry reported a 20% growth in crypto transactions, leading to a boost in the company’s sales. The company has been accepting Bitcoin since 2014.
Send and redeem gift cards with Bitcoin
Gyft, a digital platform that allows users to buy, send and redeem gift cards, was one of the first merchants enabling cryptocurrency adoption to gain traction in the real world. The mobile gift card app allows Bitcoin to be used to purchase gift cards from several retailers, some of which include Burger King, Subway, Amazon and Starbucks. The company has also partnered with popular crypto exchange Coinbase to enable users to buy gift cards from their Coinbase wallets.
Travel and pay in Bitcoin
If a traveler only has Bitcoin at their disposal, the following merchants will gladly offer services in exchange for it. TravelbyBit, a flight and hotel booking service, accepts cryptocurrencies like Bitcoin, Binance Coin and Litecoin (LTC) as payment. With a network of over 300 crypto-friendly merchants, the platform is one of the biggest supporters of crypto adoption. TravelbyBit can also alert you to upcoming blockchain events in order to interact with other crypto enthusiasts from around the globe. Other platforms to book flights with crypto include Destinia, CheapBizClass, CheapAir, AirBaltic, Bitcoin.Travel and ABitSky, among others.
Use crypto to book a five-star hotel in Zurich
If ever one finds themselves traveling to Zurich Switzerland, either BTC or Ether (ETH) can be used to pay for a stay in a five-star hotel in Zurich. In May 2019, five-star hotel and spa Dodler Grand announced that it will start accepting Bitcoin and Ether as payment. The hotel has partnered with a fintech firm Inacta as well as Bity (a Swiss-based crypto exchange) to facilitate the payment and conversion of crypto to fiat money. The hotel boasts an amazing view of the Swiss landscape among other enticing amenities that come with a five-star hotel.
Pay for electronics and more with crypto
For all the gadget lovers, there are a bunch of platforms that allow electronic purchases with cryptocurrency. Newegg, for instance, is an electronic retail giant that uses BitPay to process payments made with digital currencies. Even though one cannot get refunds for Bitcoin purchases, Newegg has a good reputation for quality items. Plus, the company boasts its being among the first merchants to support cryptocurrency adoption. Other platforms for gadget junkies include Eyeboot (a platform that sells crypto mining rigs in exchange for crypto), Microsoft, FastTech and Alza (a U.K.-based online store that sells phones and beauty products).
An ever-expanding list
It seems clear that more retailers are warming up to the idea of accepting cryptocurrencies. There is still a long way to go before full adoption can be achieved, but many companies have nevertheless benefited from being early adopters. Despite the volatile price movements of cryptocurrencies, all evidence points to a future cashless society that uses digital currencies, and crypto is leading the way.
The biggest problem with Bitcoin when it comes to cloud mining is that it’s very difficult to mine ... Always research the appropriate hash rates for the different types of rigs out there, or at least consult on online forums. Lastly, get a general feel for the company. Visit their site (and many different parts of the site), look at their About page, read the White Paper, research some of ... There are several Bitcoin Diamond mining pools from which you can choose. Learn the details about different BCD mining pools before making your choice. You need to be familiar with important details like the mining pool’s reward systems and the pool fees. Some of the popular mining pools available for BCD mining include: Btccpool; UUpool; VVpool; Step Four: Get Mining Software and Configure ... Bitcoin Mining Rigs Struggle for Profits, Despite BTC's Hashrate Reaching an All-Time High Bitcoin’s hashrate climbed to an all-time high (ATH) this week touching 166 exahash per second (EH/s ... Best way to buy bitcoin for beginners and professionals alike. 3. In-built wallets: all user accounts on the Gemini exchange comes with a wallet which is completely different from the external wallets. How to Get Started Buying Bitcoin and Crypto at Gemini. Setting up a Gemini account is easy. All you have to do is just log on to the website ... Here’s a useful video, posted Nov. 18, 2017, of BitcoinHog interviewing a miner who built an $80,000 mining rig that generates $6,000 to $8,000 per month mining ZCash. The mining operation includes 10 rigs with seven cards each, a total of 70 GPUs. The owner of the mining operation says he and his partner ran into several challenges, but perhaps the biggest challenge was dealing with heat. For Bitcoin miners that are on a budget, one of the best Bitcoin mining rigs around is the Antminer T9+. It can be picked up much more cheaply that most of the other devices on this list. However, don’t let the price tag fool you — it’s still a decent machine. High-Powered Mining Rigs Drive Bitcoin's Accelerating Hashrate . On August 19, the combined SHA-256 hashrate between the BCH and BTC networks touched a massive high of over 91 exahash per second ... Best mining rigs and mining PCs for Bitcoin, Ethereum and more By Matt Hanson , Brian Turner 14 September 2020 If you still fancy mining cryptocurrencies, these are the best pre-built rigs and PCs 3. Notable Mining Hardware Companies Bitmain Technologies. The most well-known mining hardware manufacturer around, Bitmain was founded in 2013 in China and today has offices in several countries around the world. The company developed the Antminer, a series of ASIC miners dedicated to mining cryptocurrencies such as Bitcoin, Litecoin, and Dash. Jan 17, 2018 - Explore PIRATEPOPCORNUK's board "bitcoin mining rigs" on Pinterest. See more ideas about Bitcoin mining rigs, Bitcoin mining, Bitcoin.
Ultimate BITCOIN Trading Strategy for HUGE consistent ...
Go to: https://satoshismines.com scroll down to find the video on how that can help you grow your bitcoins. Plus if you want to find out more about the tools... Bitcoin is a storm now. will it be 2M USD 2020!? The price is rising. 10x in 2017 (wow) If you want to buy/sell bit coin BTC ETH, LTC and so all you can use Binance that one of the best exchange ... TRADE BITCOIN FOR OTHER COINS: Binance: ... Mining Rig Build (Easy) Start to Finish with Tips - Duration: 42:54. Tahoe Steve 379,255 views. 42:54. Crypto Mining Farm at Apartment January 2020 ... Send Your Mining Rig Pics in Discord to be featured in upcoming Community Mining Rigs Episodes/Live Streams! Buy GPU's ... "The Bitcoin Standard": https: //geni.us/NH5spNd Donation Addresses ... How to Mining Bitcoin 2019 Bitcoin Mining in 2019 - Still Profitable? Best Cryptocurrency Market Binance https://www.binance.com/?ref=25992167 Litecoin Donat... My Mining Rig Tent Video - https://youtu.be/pebd3sSp1wg Get A Whole House Fan on Amazon - https://amzn.to/2Dg3mvx MY RIG COMPONENTS: Graphics Cards ( I love ... Join Binance Exchange Here! https://www.binance.com/?ref=13795076 Join Kucoin Exchange Here! https://www.kucoin.com/#/?r=7chr68 Mine Bitcoin and other Crypto... Should you buy a pre-built btc cryptocurrency mining rig? The answer depends, lets review the Coinmine One and discuss the status of gpu mining in 2019 and t...