Bitcoin – Potential Network Disruption on July 31st
bitcoin.org
bitcoin.org
Bitcoin is currently suffering from significant scaling problems, which lead to high transaction fees. Numerous proposals to fix the scaling issue have been proposed, the two main camps being "increase the block size" and "muddle through by discarding less useful data" (aka Segregated Witness/SegWit). However, any changes require consensus from the miners who create Bitcoins and process transactions, and because it's not in their best incentive to do anything to reduce those transaction fees, no change has received majority consensus.
In an attempt to break this deadlock, there is a "Bitcoin Improvement Proposal #148" (BIP148) that proposes a User-Activated Soft Fork (UASF) taking effect on August 1, 2017. Basically, everybody who agrees to this proposal wants SegWit to happen and (here's the key part) commits to discarding all confirmations that do not flag support for SegWit from this date onward. If successful, this will fork Bitcoin, because whether a transaction succeeded or not is going to depend on which side of the network you believe.
However, BIP148's odds of success look low, as many of the largest miners out there led by Bitmain have stated that they will trigger a User-Activated Hard Fork (UAHF) if needed to stop it. Specifically, if UASF appears successful, instead of complying with SegWit, they'll start mining BTC with large blocks instead: https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
Anyway, it all boils down to significant uncertainty, and unless you've got a dog in the race you'll probably want to refraining from making BTC transactions around the deadline or purchasing new BTC until the dust settles down.
And an important disclaimer: this is an extremely contentious issue in the Bitcoin community and it's really difficult to find info that's not polarized one way or the other. Most notably, Reddit's /r/bitcoin is rabidly pro- BIP148 and /r/btc is equally rabidly against it. Here's one reasonably neutral primer: https://bitcoinmagazine.com/articles/bitcoin-beginners-guide...
EDIT: Quick reference https://medium.com/@wintercooled/the-road-to-segwit-activati...
Would you support something which has not been fundamentally tested?
https://github.com/btc1/bitcoin
> ... and tested implementation.
It will go online on the testnet tomorrow
It seems rather premature to call it working before it gets properly tested. And three weeks is a woefully short time to test something like this, fix any issues that are found, and then re-test.
July 14 - Agreement Participants Install and Test Milestone
One of the most amazing properties of Bitcoin is that it's completely user driven. When it comes to the fundamental consensus rules, no amount of hashrate or corporate agreements can force a change onto the userbase. It's a system that intentionally resists central control. Any changes need to start with userbase support, and I'm just not seeing that with Segwit2x.
If I am wrong, I will find out soon enough.
All the definitions I heard are able to be manipulated easily:
-The/r/bitcoin consensus? Is mainly in existence because of censorship
-User wallets online? Can be easily created with AWS instances
-Bitcoin core? Who decides these bunch of people are in charge to represent all users and not a bunch of other developers?
One obvious alternative is to let Bitcoin follow economic incentives: Bitcoin miners gain Bitcoin, so they have a vested interest that their income is and stays valuable. Thus why not let the miners decide. This is also the only place where you can't influence/manipulate Bitcoin easily.
Quite simply, the coin price indicates support. After the split, there will be two versions of the Bitcoin network with independent prices. A non zero price indicates non-zero support, and as long as it's at least 25% of the original price, it'll probably be okay.
A high price indicates high support.
In the long term, the hashrate follows the price. Miners will mine the coin with the highest price, because they can't afford any other option. Electricity is expensive.
Isn't it at least to a large degree the other way round? That market value is following based on what is the most mined chain? If there's a split and 80% of mining power switches to one branch. Then the 20% branch loses a lot of utility for at least some time. It now has five times slower transactions until difficulty gets adjusted(or you change the proof of work of bitcoin, which itself can be precarious). And now to a minor degree the minority chain has also less safety (less hashing power).
Meanwhile why should anyone buy or send Bitcoins at the point of a split? There's a real chance that one branch will die and then you can lose the coins. The best strategy is probably to wait. So the market at least is in some way inhibited during a split.
On the other hand I'd argue miners of the minority chain have a lot of pressure to change branches. Market is not yet a good indicator only hashing power and they'll lose money if they don't continue to mine on the more profitable chain. Their safest bet is to change chains. Also they know that other miners of the minority chain think probably similarly. That's why imo in Bitcoin history every fork/split was resolved very quickly and a branch "won".
Certainly, the last of those options seems to be popular recently.
Only the 2x part of segwit2x will need user adoption, but that comes 3 months after segwit has activated (next round of drama, long on popcorn)
None of the core developers support segwit2x.
I have no bitcoins, so I have no real preference in what happens. But watching politics destroy a 'decentralised' currency is good entertainment :)
But it also reinforces for me just how not ready for primetime BTC is, and it makes me think the appreciation over the past year is truly insane.
Don't get me wrong, I think the concept is brilliant. I just don't see how nearly 10x value was created in about a year.
*Speculation
Can you explain how this jives with miners supporting Segwit2X, which brings both segwit and bigger blocks?
Segwit2X would activate effectively Bip148, though it was originally a proposal to use a different mechanism it is acceptable enough that Core is happy to have segwit activated that way.
Another aspect of the riddle is that SegWit will eliminate ASICBoost - which is an optimization developed by one of the biggest ASIC miners producer - so he is probably also against it. There is also the thing that ASICBoost is probably patented - so it has a lot of opposition in the community.
Gas can mean ETH gas, petrol gas, or gas gas.
I have seen this myself with a production blockchain and blocks that were less than 1mb. Increasing the size increases this effect and gives Chinese miners and artificial advantage.
Plus there's no congestion on the network right now. There's not a scaling problem. It was spam.
Further, segwit increases block size and efficiency so there's no reason to not activate it.
This whole issue isn't about scale, core is still ahead of the curve on what's needed to scale, it's about control, and disabling ASICBOOST and keeping transaction fees high.
Plus there's no congestion on the network right now. There's not a scaling problem. It was spam.
Woohoo! No need for anyone to do anything then. Remind me again why everyone is trying to scale bitcoin?
Everyone is trying to scale bitcoin because bitcoin is growing dramatically... that doesn't mean that the "full blocks" and "high fees" we saw recently weren't due to spam.
Please logic.
Ironically, this has actually become a real Byzantine Generals problem. Guess Bitcoin can't actually solve that problem in the real world.
From what I understand, China isn't too keen on the whole endeavor since it circumvents their (stringent) capital controls. What happens if they turn the baleful eye of their deep packet inspection onto the Bitcoin network? (serious question)
(Background for those who don't know: encryption/etc don't work against the Great Firewall, it knows what a given type of connection "looks like" in terms of packets/activity, so it can identify (eg) a VPN session even if it's "wrapped" or "tunneled" across some other protocol. They use a massive amount of machine learning hardware to profile connections in realtime to pick out "suspicious" activity and those connections will be dropped after a few moments. It's not impossible to run arbitrary connections through the firewall but it's very difficult and getting harder all the time.)
But isn't mining power already consolidated?
Without full nodes validating consensus, miners can (will) force protocol changes (eg. change 21,000,000 coin limit) on users, effectively changing the decentralized leaderless attributes to a centralized dictatorial less-efficient PayPal. At this moment, bigger blocks mean a less-free (as in speech) bitcoin.
10x the transactions is not much at all. The comparison with the VISA network is not a valid one - with micropayments the volume could be 100x or 10000x - we should be able to accommodate it.
The only solution is to begin handling transations off-chain. But the problem is that there is no one good proposal for it. Until it is clear how off-chain transactions work, we will keep seeing this sort of stuff.
This has nothing to do with the block size. The size of the chain is proportional to the number of transactions. Whether those are sliced-and-diced into small blocks or large ones is completely irrelevant to how big the chain is. The only thing the block size influences is how many transactions can be mined in one block, i.e. the rate at which transactions can be processed.
But yeah - the size of the blocks does depend on the number and size of transactions and if you don't have transactions to fill up the block in full (i.e. so that its size is just under the maximal block size) - then the transactions will be the limiting factor.
Why do you think Satoshi's gave it an artificial 1MB limit if it didn't matter?
I have no idea why Satoshi chose a 1MB limit. Probably for the same reason he chose a 21M BTC limit on the total number of bitcoins that can be mined: both are arbitrary numbers that he pulled out of a hat. But the next time I see him I'll be sure to ask.
This is eventually going to be a problem sooner or later regardless. The fundamental decentralization of Bitcoin depends on everyone having the whole blockchain. Any sort of "checkpointing" mechanism inherently relies on trusting authoritative nodes about network state, at which point it's no longer decentralized.
(However this is somewhat of a distinction without a difference. In practice you are trusting the nodes on the network anyway - the network is authoritative because everyone agrees to treat it as authoritative. If everyone agrees to trust some other blockchain as "the real truth" then you can either accept the new authoritative network or be on your own chain that nobody else accepts - which is what happened to Ethereum after the DAO hack.)
This is a fundamental limit to the Bitcoin model and will have to be addressed sooner or later. The data is already past ~100 GB (and totally incompressible) and that's with blocks so small that the network is choking due to lack of capacity. This is only a few years' worth of records, what does the big picture look like in 20 years?
Segwit is absolutely mandatory to allow interfacing other chains in a secure manner. Pretty much everyone agrees transaction malleability is a huge design flaw (apart from some Chinese farms which are abusing it via AsicBoost).
What I specifically have a problem with is the way both sides have drawn arbitrary lines here. It's not SegWit or a larger block, we can have both. And in fact the Core proposal does include a larger block, on a surface level this dispute is over how much bigger it should be (the Unlimited devs want a much larger block right away). Again, pretty much everyone agrees that transaction malleability needs to be fixed except that group of miners.
On a deeper level it's about a power struggle between the Bitcoin Core devs and the Bitcoin Unlimited devs, and between the various factions of miners.
The only proposals on the table for off chain storage add profiteering middle men to the system. I'd rather pay for storage.
Currently at 160GB or something with 1MB block, what storage do you think a node will require with 10MB block in the next 5 years when the usage will be growing?
If there were no technical and economic tradeoffs to increasing the blocksize then yes, it would hard to see how otherwise intelligent people could oppose it. Everybody loves a free lunch. But there are tradeoffs, which you conveniently omit, which are giving those otherwise intelligent people pause, rightfully so.
They state the ip is for defensive purposes only - however that is questionable given that anything they implement, automatically becomes prior-art. It is also contrary to the spirit and practice of the majority of crypto/alt projects.
It is unreasonable to attack miners for having interests, without disclosing that other interests may benefit from the current levels of network congestion that a skeptic would say are caused by having artificially small blocks.
Liquid Network and Lightening Network are different things and work in a different ways. A new version of liquid that uses some of he lightening technology enabled by segwit is probably in Blockstreams plans... but there are multiple competing open source implementations of Lightening Network being worked on.
Please link to the patents on the lightening network. I don't think you can.
There is no current network congestion. Free transactions are clearing after awhile and very low fee transactions are clearing right away.
All of the congestion of the past 3 months was from a spam campaign being run by the people who claim "bitcoin doesn't scale without larger blocks" ignoring that Segwit increases block size AND increases efficiency in using that capacity.
> Today we are excited to announce some important steps we are taking on the patent front, why these defensive steps are necessary, and our hope that others will see merit in our approach and follow our lead.
...
> Our Patent Pledge assures developers and users of our technology that we will not sue them for patent infringement, provided they comply with the terms and conditions of our pledge...
https://blockstream.com/2016/07/19/blockstream-defensive-pat...
Edit: Here is a discussion of Blockstream's patent application for side car design,
> The application, submitted on 9th May and published earlier this week, outlines “systems and methods...for transferring an asset from a parent chain to a sidechain”.
http://www.coindesk.com/bitcoin-blockstream-patent-sidechain...
Here is blockstream talking about Lightening,
> Blockstream’s work on the Lightning protocol began two years ago with the intention of enabling new applications and developing new use cases that could help further the adoption of Bitcoin and related technologies
https://blockstream.com/2015/09/01/lightning-network.html
Also presumably if segwit activates then Liquid is no longer needed?
Edit: The relationship between Blockstream and Lightning is underscored, by the fact that the largest contributor to the specification is a Blockstream employee (Rustee Russell),
https://github.com/lightningnetwork/lightning-rfc/graphs/con...
lighting is designed to be able to farm out channel enforcement to other nodes on the network to prevent cheating while preserving privacy.
lighting does require more block space to operate globally than is available. It still scales better than bitcoin though.
No, it is not only open source but a healthy mailing list with a lot of interested parties.
> lead by Blockstream
No, Poon and Dryja are not employed by the company Blockstream. The latter seems to be more focused on their sidechain solutions.
> the work is even patent-encumbered
No, there is nothing to suggest this. Patents have to be public at some point.
All the practical "here's how lightning's going to work" papers I've read so far leave me very skeptical. Here's an example: http://diyhpl.us/wiki/transcripts/scalingbitcoin/hong-kong/o...
The Q-and-A at the end in particular is interesting:
>Q: On the last slide, one of the assumptions was 3 channels per person. Assuming payment channels wouldn't be useful for retail sales, because you don't want to buy a coffee just to open immediately. Is that correct?
>A: Joseph might expand on this. Let's say you buy a coffee. You're probably buying a coffee only once, right? Well, maybe the coffee is $5, and you put $50 into the channel and leave it open. Then someone else comes to the coffee shop and she does the same thing. But she has a channel with the grocery store. There's me, coffee shop, Alice, grocery store, they all have channels. When I go to the grocery store next time, I don't have to open a channel. Payments are routed.
>Q: It sounded like everybody would have to open new channels.
>A: I am guessing the mean is going to be 3, but it will probably be an exponential distribution. Most people will probably have 1 channel, and then some might have 100s of channels open.
I don't know about you but while on paper that might work I still see a lot of hand waving, guesswork and rather unsubstantiated assumptions. Why would I decide to "lock" $50 worth of Bitcoins when I buy a $5 coffee? What's the incentive for me to do this? Where does this estimate of 3 come from exactly, I see it repeated everywhere but I can't find the maths behind it?
Here's an interesting attempt at simulating a real-scale ligtning network (why aren't there more of these? Aren't we talking about a $40bn market cap currency here?): https://hackernoon.com/simulating-a-decentralized-lightning-...
The simulation is rather unrealistic and I'm not sure how to interpret its conclusions. It seems to kinda work but there are issues:
>133,401 micropayments were attempted and 3461 (2.6%) of these failed. For successful payments the median number of hops was 19 and the median total fees were 2 bits (0.000002 btc) or 32% of the value transferred.
Now it could be caused by a bad simulation rather than a real issue with Lightning network, but frankly I can't tell at this point.
I don't have a horse in this race but as seen from the outside it all looks a bit rushed and amateurish. I don't know the whole story though, maybe I'm just poorly informed.
so if the transaction fee is $0.50, you get to transact at 1% cost
if you paid $0.50 for each coffee it would be 10%
Can you really imagine how this would work IRL?
"-Here you go sir, that'll be $32 please."
"-OK, I'm paying it Bitcoins... Oh, you don't have an open channel, I'm going to create one... Mmh, but how much to I put in? Let's say $100, I'll probably buy here again next week. But will that be enough? What if my total is just above that next time? I'll have to pay the fee twice. I guess I'll just make sure not to go over $100."
"-We also accept cash, Visa and MasterCard sir."
Again, maybe it can work, it just feels so "theoretical" so far, I haven't seen anybody paint a convincing picture of a what a "Bitcoin as Visa replacement" world would look like concretely.
Yes. This is basically the exact user experience of the Starbucks app, and it's a fine experience.
You pre-pay an amount, have a balance open, transactions reduce that balance, and you occasionally need to reload your balance with another credit card transaction.
Which is to say I don't think this is an intractable problem if there is good software with good user experiences to help out.
All that said, I'm not current on the block-size vs SegWit debate, so my analogy could be flawed.
Now take amazon, take that small shop on the street where you go twice a year because it's super expensive but it's also opened very late, take your car mechanic, take that guy on ebay you're buying a pair of socks from, take that restaurant in Berlin during your vacation where you'll probably never go back. Will you be willing to "pledge" 10 times the amount while buying there? And if not won't the fee be dissuasive? What's in it for me?
And won't that create negative side effects for competition? For instance if a new coffee shop opens next to Starbucks with your system I have an incentive to keep going to Starbucks since it already has an open channel (exactly what the Starbucks app is about, except I'm paying for it, not Starbucks), so effectively it makes it harder for newcomers to compete. Same thing for, say, amazon vs. some random ebay seller. The more popular a shop, the more likely it'll be to have an open channel pending. Isn't that going against the "completely decentralized currency" ethos? What good is it that the currency is decentralized if I can effectively only use it with a limited number of companies?
It would be pretty amusing to me to see the cyberpunk libertarian cryptocurrency turn into a glorified Costco membership.
It's much better than a Starbucks app.
And while this is an important feature of lighting, it's not actually a "feature" when compared to Visa or MasterCard and the centralized banking system from the point of view of the user. Ideally this should all be hidden away from the average customer.
People won't want to worry about graph theory when paying for a sandwich at a gas station. Existing payment solutions still wins hands down 99% of the time when it comes to convenience even if we imagine a "perfect" lightning network. I really have a hard time imagining what would drive a mainstream adoption of bitcoin over the current status-quo.
Lightning will work the same way. Nobody needs to worry about graph theory, they can just generally assume that the graph is fully connected, and that their software will be able to find a path from A to B.
What will be bitcoin's "ISPs"? Who makes sure the graph remains connected and usable? Who invests in the "infrastructure", making sure channels remain well balanced? Some say that Lightning will be self-balancing through a clever set of incentives, but that's again extremely experimental and untested.
Also note the big "net neutrality" thing going on in the US right now. What will prevent big players from teaming up and interconnecting with each other to facilitate transactions while leaving out the rest?
I don't have the answers to any of these questions, maybe it's just FUD. I'm just surprised that bitcoin is a couple of weeks from making such a huge jump into the unknown. It's extremely interesting to be sure, but I feel like some people are going to get severely hurt if this whole thing comes crashing down.
I don't see a reason that exchanges couldn't take on the role of ISP/bank in this situation. Essentially you have an account with 1500 BTC at an exchange, and you say that you want to put 500BTC into a lightning network. Then the bank centralizes itself in the lightning network graph by making connections with other large banks and some major companies.
Of course what we've just done is recreated the modern centralized payment processing scheme on top of the bitcoin network (ie. a mom and pop shop connects to square connects to BoA has my money which doesn't actually exist anywhere, and they make ledger changes and top up later).
You might even be able to make such a system work with no additional transaction fees. But I'm not sure of that.
God I wish this was still true. The internet is so fragmented now I have to have IPs in different nations for a unified experience.
It's called a credit/debit card.
You must remember that Bitcoin transactions are "settled" in that 7 TPS timescale, whereas VISA transactions are merely "recorded" in their 50K TPS rate.
In reality, it generally takes a minimum of 15 days for your VISA transaction to "settle" with your bank account. Thereby the true TPS rate is orders of magnitude lower for VISA.
Obviously in any case it will be faster than Bitcoin.
With regard to latency bitcoin is still worse in practical applications - because VISA confirms a transaction immediately even if as you write it settles after 15 days - while bitcoin more or less settles after and an hour - but the first confirmation you get only after about 10 minutes.
[1] https://usa.visa.com/dam/VCOM/download/corporate/media/visa-...
If we use the 7 TPS number that people seem to be using (even though the real number I think is slightly lower), then we end up with 220,752,000 transactions in a year; three orders of magnitude less than Visa.
Bandwidth != Latency
I think proof of work mining is extremely wasteful. But once it is in place, you can sign a merkle tree of any size. You can add as many transactions as you want. The problem is that the ledger has to grow and grow. It would be nice if something was developed where you didn't need to keep the whole history.
----
Right now there are 3 implementations of Bitcoin in the wild, and each of the 3 will react differently to different network events. The network is essentially splitting apart, with each fragment driven by a different faction.
If you don't know what the different factions are, you probably don't need to. Its needlessly involved, highly political, and full of echo-chambers and shouting matches.
What happens largely depends on how much support each faction has. Unfortunately, there's no real way to measure how much support each faction has until the fork actually occurs. Each faction thinks that its the largest by a significant margin, and thinks that the other factions have used underhanded techniques to bolster their visible support.
When the rubber meets the pavement, we will know though. If the network splits into three pieces, likely the coin price for each piece will move around violently, and one portion of the network will probably end up with a much higher coin price than the other parts. Or maybe it'll be an even three-way split, which will make things in the Bitcoin world very confusing.
----
As a huge Bitcoin fan, I hate to say this, but if you aren't clued into the various events, and you can't name the three factions or explain the beliefs of each, you should just stay away for a while. If you get pulled into the split without knowing what's going on, you are very likely to lose money. There will certainly be opportunists trying to take advantage of the situation, and you, being ignorant of the situation, will be the one who gets taken advantage of.
----
If you do know what's going on, you can name the factions, etc, then what you should do is pretty simple. When the split happens, sell all of your coins on the forks that you disagree with, and use the resulting money to buy coins on your preferred fork.
----
For anyone who cares, my alignment is with the status quo. I feel great animosity towards the hardfork faction (confusingly called Segwit2x), precisely because they have forced a situation where people who don't know what's going on are able to get hurt. They have also repeatedly, repeatedly, ignored very sound advice from the technical experts of the industry.
The UASF faction (confusingly, a 'pro Segwit' and 'anti Segwit2x' faction) has my spiritual support, but I don't think they have the numbers behind them to make a difference. I don't think running the UASF software is the right move.
I personally believe that overwhelmingly, the vast majority of people who use Bitcoin are probably largely unaware of what is happening, and are running the status-quo software (confusingly, the 'Segwit' software, or the 'Bitcoin-core' software). I'm guessing when the forks all happen, it'll be pretty dominantly vanilla Bitcoin with the highest price, and then a few weeks later it'll all be a bad memory, and nothing will have happened at all.
I guess we'll find out.
Or keep all the forked coins in case you are wrong ?
If you aren't ideologically aligned, holding onto all forks is a perfectly sane choice.
For example, in this experiment small payments for correct and "don't know" responses sharply diminished the gap between Democrats and Republicans in responses to "partisan" factual questions.
Profit comes from knowing how the markets will move before they do (and performing arbitrage), not from owning the asset that has the greatest market cap.
Make that 4...
How would you do this in practice? Most exchanges probably won't code in the ability to sell on multiple chains.
This is an unfortunate misunderstanding on the part of the miners, and the math is really simple: imagine a network on top of Bitcoin, e.g. lightning.network, which can process 10 million transactions off-chain and settle it on the Bitcoin blockchain using only a single transaction. Imagine if every one of those 10 million off-chain transactions paid just 0.01 cent in fees... this would earn the payment processor $1000, which can only be realized by publishing a Bitcoin transaction, in competition with everyone else making a lot on off-chain fees. The result is that off-chain profits (in the form of fees) would allow off-chain payment processors to pay huge blockchain fees, because they can deduce it from the profit they've made on off-chain fees. Nothing, in my opinion, will increase Bitcoin fees more than layer 2 protocols creating more users and transactions (because fees are paid per off-chain transaction).
The point some miners are missing is that one billion off-chain transactions each paying a 0.01 cent fee is more profitable than 2,000 on-chain transactions paying $1 each. And if everyone is able to earn $100,000 in fees by publishing a single Bitcoin transaction, this must push up Bitcoin fees, since people will be competing on getting into the chain with the bidding power from their earned profits.
I don't understand this. Due to what would 95% of current miners find mining unprofitable at 8MB blocks?
miners typically mine in pools. so they don't need to download the blockchain because the pool is doing it for them.
Literally the only real throughput limit is end user's download bandwidth, which means 500MB blocks or so for 10Mbps download. Spv clients are fine for those unfortunate to have monthly limits.
>making it even more profitable to mine for big investors, than smaller fish.
Both storage and bandwidth are utterly insignificant cost items in a mining operation.
SegWit was not created toward the end of increasing the blocksize, it was created to fix transaction malleability along with various other improvements. That it arranges the partitioning of witness data from transaction data to sort-of not count against the block size was a bonus, especially since a lot of dubious attempts at forking to a larger block size we're being given decent backing in terms of funds.
The point of fixing transaction malleability is that it allows for more robust smart contracts that depend on transaction validity. Once you enable these smart contracts, you start scratching at the surface of scaling methods that shift risk to the willing participants. As every Bitcoin transaction must be validated by every Bitcoin node, the entire network must inherit the risk of attempting to satisfy demand for transactions. Not just in terms of hardware requirements, but also in terms of the viability of paying for security of the network against a diminishing block creation subsidy.
The maintainers of Core, and plenty of other people in the Bitcoin community, see the scarcity of block space as a positive and as an inevitability. It's a positive in that it provides the incentive for security as the subsidy gets reduced, and inevitable as any 'spare' space in blocks can incentive superfluous transactions. There's plenty of development on the front of moving bitcoins between other chains with different consensus rules that would allow for better scaling, and for better development and testing of solutions that could eventually make their way to the main blockchain.
I'm personally of the opinion that once you allow for the transfer of bitcoins to and from second order chains, that Bitcoin can essentially enter a version freeze.
I find it hard to see how anyone could reasonably dispute it. Transactions were fast and cheap-to-free until mid-2015, when the blocks filled. Since then transactions have been slow and expensive.
https://www.reddit.com/r/Bitcoin/comments/6hzw6c/010_satoshi...
it looks like some faction was spamming the network with transactions to create a false sense of urgency about the need to scale.
A lot of ignorant people want to throw the baby out with the bath water though, so ultimately we're probably going to have two chains, one that does it the way the talent in the community says it should be done, and another that shifts responsibility around to a few scaled entities. My money is not on the latter.
Segwit will disable ASICBOOST as a side effect of improving the protocol. Therefore, BitMain has been launching FUD campaigns and numerous attempts to propose alternative software to stop segwit (XT, BU, BTC1, BTCABC etc.)
Segwit2X is a compromise-- but Bitmain does not like it because it activates segwit.
So BitMain has announced they plan to do a forcible Hard Fork of Bitcoin, splitting off into another chain, that they will privately mine-- and they intend to neutralize segwit on it.
They have publicly complained that segwit offers lower fees for transactions that use less resources.
The entire conflict (including the "scaling problems" which have recently been proven to be due to spam driving up transaction costs) is Bitmain attempting to increase and protect their near monopoly.
Please be aware that their fork, which will have nearly unlimited block size will increase their monopoly. Due to the great firewall of china, large blocks have trouble getting transmitted, so whenever a chinese miner finds a block, when the blocks are very big, they have a significant competitive advantage in finding the next block. Thus simply activating a spam campaign (which they have been doing the past 3 months or so already) will allow them to centralize mining in china because the chinese miners will start getting 2-3 blocks ahead. Further on their hard fork they can easily lower the difficulty and get many blocks ahead while private mining (but make it look like the difficulty is higher) -- admittedly a speculation but given their past exploits and announced plans to engage in further shady behavior I would not be surprised.
Here's the blog post where they announce their (very sketchy) hard fork: https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
> I think you missed the key issue. Mining is largely centralized under the control of Bitmain, both via pools and indirectly via miners they have sold
False, bitcoin mining has never been as decentralized as it is now: https://coin.dance/blocks
> Segwit2X is a compromise-- but Bitmain does not like it because it activates segwit.
False, they are signaling Segwit2X and have been open to support segwit (except the arbitrary discount).
> So BitMain has announced they plan to do a forcible Hard Fork of Bitcoin, splitting off into another chain, that they will privately mine-- and they intend to neutralize segwit on it.
As per your own link, this is a plan against the UASF fork.
> They have publicly complained that segwit offers lower fees for transactions that use less resources.
And instead they back bigger blocks and flexible transactions which would give them even lower fees? If your statement was true then they wouldn't do that.
> The entire conflict (including the "scaling problems" which have recently been proven to be due to spam driving up transaction costs) is Bitmain attempting to increase and protect their near monopoly.
No, it is because Blockstream and Core wants to retain control. Do they support Segwit2X even when 90+ of all miner power signals it? No.
Segwit as a soft fork is a crappy implementation and reduces the security of Bitcoin. See:
https://medium.com/the-publius-letters/segregated-witness-a-...
Flexible Transactions is a superior proposal:
Bitcoin mining has never been as centralized as it is right now with one man controlling over %70 of the hash rate via multiple pools. Many of those pools are just the same player operating under different names.
Segwit2X is in fact a compromise, and I linked to a blog post where Bitmain complains about it. They want to "activate segwit" but what they call segwit is not really segwit. The UAHF article I linked to is not Segwit2X it is a new hard fork they propose because they don't like Segwit2X. If they actually supported it they could just let it activate.
They back a solution that gives them more control over the network and higher fees, not lower fees. You think they will give lower fees but you're uninformed about the current fee situation.
Blockstream doesn't have control. You're pushing an uninformed narrative that makes Blockstream out as some sort of evil corporation--- the reality is block stream employees are a minority of core, core development is done in the public eye (unlike even Segwit2X and certainly any of Bitmains's hacks, like BU which was closed source for awhile before people just gave up on it.)
You keep talking as if the miners are supposed to be in control, as if that's right. It's not. Bitcoin was designed to be a balance, and the only error satoshi made was not realizing that his PoW was vulnerable to ASICs, which have resulted in centralization. You act as if there are a lot of miners and they are the bitcoin community, they are not, they are the minority. Alas they have spent a lot of money to dupe people like you into thinking they are the good guys.
Your articles are non-technical nonsense full of FUD written by people who do not understand the bitcoin code.
Here's the real threat to bitcoin-- people who are not developers are easily mislead by conspiracy theories backed up by thousands of shills posting this kind of crap narrative.
Thanks for the down vote, too bad you didn't have a technical argument.
The great firewall of china is not going away. The centralization threat is real. Segwit is the most tested code put out by core... and a whole lot better than the shitshow of alternatives we've seen put out by those who are trying to take over bitcoin.
You repeat the mistakes as outlined in this article:
https://medium.com/@johnblocke/decentralization-fetishism-is...
> They back a solution that gives them more control over the network and higher fees, not lower fees. You think they will give lower fees but you're uninformed about the current fee situation.
How so? Because bigger blocks will give lower fees than Segwit only.
> Blockstream doesn't have control. You're pushing an uninformed narrative that makes Blockstream out as some sort of evil corporation--- the reality is block stream employees are a minority of core, core development is done in the public eye (unlike even Segwit2X and certainly any of Bitmains's hacks, like BU which was closed source for awhile before people just gave up on it.)
The censorship in those channels are well documented.
> You keep talking as if the miners are supposed to be in control, as if that's right. It's not.
You don't understand the point of PoW in Bitcoin.
> You act as if there are a lot of miners and they are the bitcoin community, they are not, they are the minority.
Doesn't matter. And btw, you think UASF is the majority? Because they are not.
> Your articles are non-technical nonsense full of FUD written by people who do not understand the bitcoin code.
Where are the technical arguments against these supposed "non technical FUD pieces"? You provide none.
Who profits from high fees? Core? No. Miners. BitMain is very adamant about not wanting low fees. The idea that Segwit, which quadruples block size and offers a fee discount is an attempt to keep fees high is absurd on the face of it.
>And btw, you think UASF is the majority? Because they are not.
You're convincing me that you're operating from a script and have no technical knowledge of the situation.
Segwit2X IS a UASF.
> And btw, you think UASF is the majority? Because they are not.
Segwit2x is the majority of signaling right now. (Though it's a fake out because Bitmain plans a hard fork.)
Your personal attacks and failure to address the technical issues speak for themselves, so I have not quoted them, nor responded.
> BitMain is very adamant about not wanting low fees.
Yet Bitmain supports larger blocks, you're not making sense.
> Your personal attacks and failure to address the technical issues speak for themselves, so I have not quoted them, nor responded.
What personal attacks? Sure, continue dismiss it as "FUD" or "non-technical people".
I point out a contradiction in Bitmains position and you say that means I'm not making sense? Once again, you are arguing that your ignorance somehow trumps the facts.
And of course, you resorting to insults is all the proof I could have needed.
Go educate yourself. Start at bitcoin.org
Then you immediately launch into narrative, one that avoids detailing how Jihan doesn't control the hashrate. Individual buyers and operators of Bitmain's mining hardware do. You are attributing things in plainly incorrect ways.
>Bitcoin mining has never been as centralized as it is right now with one man controlling over %70 of the hash rate via multiple pools.
Nothing about the owners or the choices they can make with their hashrate. All some narrative about "evil Jihan."
I am not for UASF and I think it's moronic (since it will lead to chainsplit and user confusion); segwit is fine though and FlexTrans are not a serious contender
You obviously have no idea what the maleability problem is and you didn't read and understand the linked articles.
Segwit does fix malleability, and this is critical for bitcoins future, for many reasons.
I don't like the part where they rush to implement everything as fast as possible. And from apart (and I don't follow Segwit2x that much), the changeset seems too big from bitcoind.
And they say openly they plan hard-fork, not this UASF where the S is not really that S and is almost guaranteed to result in a split and confusion.
They signal Segwit in a compatible way, so it's OK. Just the timeline is crazy.
Incorrect. It would make 'stealth' ASICBoost mining improbable but still possible overall.
> Therefore, BitMain has been launching FUD campaigns.
Substantiate your claim.
> proven to be due to spam
Show it. Just show it already. Its a transparent blockchain but no one can show this spam, identify how it is malicious, show where it is coming from.
Show the spam already. Like ASICBoost its an invisible horror used to terrorize people into supporting your narrative. This is not very nice.
I've used the fee prediction engines to try to avoid low fees and still ended up waiting eight days for a transaction to process. I gave up on it during that week, only for it to go through after I paid another way.
I don't really get the debate, I mean maybe implement the solutions from both sides at once? I don't care, my local solution is to just avoid it as a payment network for now. That's its own kind of vote I guess...
I'm sure there will be a camp arguing that I just wasn't smart enough, with the corollary that UX as a discipline coddles whiners like me.
Maybe so.
The game theory of fees and congestion is still interesting, with miners always interested in an incrementally more painful network for users, until the tragedy of the commons hits and it collapses.
Bitcoin has a first mover advantage, which led to some network effects increasing its popularity. Miners are extracting some rents from that popularity right now. But there may be a weird game theory here, where users are driven to prefer newer bitcoin clones with smaller (less secure) networks, simply because the fees demanded are far lower and (more importantly) more predictable. Price volatility of newer networks is a major a downside, but there's an equilibrium. Everything has a price, even volatility/stability. If you're doing one transaction and not storing value, then your risk on a new network is bounded by how long it takes you to get money in or out of the network and process the transaction. BTC will bleed off support, under some values of: BTC fee, BTC tx processing time, processing time variation, velocity in and out of smaller network, and volatility of smaller network. (This might be asymptotic and leave BTC the leader though, no guarantees.)
While creating a lot of confusion about long term coin viability, these forces could provide a useful equilibrium on power consumption, a downward force on how much power we want validating transactions. I've been worried about the power cannibalism scenario, where BTC becomes a payments standard but we're racing to commit all new power generation simply to verifying the network. But power use puts a floor on tx fees, and users with available alternatives put a ceiling on them, so... maybe we won't build a dyson sphere dedicated only to powering one payment network after all.
HERETIC
No really, this is exactly what Segwit2x is doing, but it is still heresy for the UASF camp.
Answer me this-- if it's opposition is UASF, why did bitmain, after Segwit2X got so much support, announce they were going to hard fork anyway?
https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
The Bip148 crowd is happy with Segwit2X because it effectively activates the UASF represented by Bip-148. We don't really care which of the BIP mechanisms is used to activate segwit if segwit is (And I think they are changing 148 to activate along with Segwit2x so there's no split in the support between the two.)
Any distributed payment network will asymptotically approach unusability over time.
Otherwise miners are leaving cash on the table.
Imagine there's 11 people waiting at a bus stop, and the next bus that arrives has 10 spare seats. There's no pricing model that will allow all 11 people on to that bus, regardless of how much the people want to pay, or even how you rate the users. So it goes with bitcoin.
The level of inefficiency here is mind-boggling. Surely this must be one of the least efficient, least environmentally-friendly computing ventures ever?
Waiting. Since 2011.
OSI Model: http://www.webopedia.com/quick_ref/OSI_Layers.asp
Perhaps not the best example to use.
It's colossal because of the sliding difficulty. The block period is a big portion of why the transaction rate is what it is.
It's weird because people will argue about how bitcoin is safe because you can trust it, but it seems it's safer to pay for a centralized service and trust such a service because it's administered by very competent people with a high level of scrutiny.
If you look globally, that would mean bitcoin is much, much more expensive. It is just some kind of cool toy for people who hate the federal reserve.
Sure the exchange rate of bitcoin has grown much - but it does not make it better value store now, rather the opposite.
Scalability has improved somewhat during the past two years and most developers believe it is time to increase capacity as well. The question you refer to is how to increase capacity, within the scaling constraints.
I understand the ambition to be neutral in a contentious issue but one must be careful as not to spread misinformation. "Discarding less useful data" is not how segwit works at all. Segwit does away with the fixed blocksize and uses instead a flexible block size of up to four times the previous fixed limit.
The discarding you refer to is the backwards compatible aspect of segwit where it can communicate with older nodes that do not implement this feature by not sending them the data. It is not discarded and a supermajority of the network must use the full larger blocks in order for this to be secure. It is merely a transition method to allow for upgraded and non-upgraded nodes to briefly share the same network.
So what you refer to are two methods for larger blocks. One must be upgraded with a flag day where everyone upgrades or you lose money, and one allows for a transition with a certain amount of backwards compatibility.
It is also misleading to describe this as two "sides". The sides are mostly within social media. The technical debate has been had and there was overwhelming consensus among the developers that the backwards compatible way should be deployed first.
If the technology takes off and solutions such as Lightning prove viable, most developers agree that the non-witness part of the blocks probably needs to be upgraded as well.
Scaling is something developers care about, but in the nascent field of cryptocurrencies there probably no single solution.
It should be noted that with your credit card example, however, that credit card networks charge a percentage of the funds transferred while in the case of Bitcoin it is instead a fixed fee. Should you instead have said that it costs $5 to send $5000 it would have been equally true but sounded quite different.
That Bitcoin as it is described in the whitepaper doesn't scale to even a single US credit card network should be obvious to any reasonably informed reader. That every participant in the network store everyone else's transactions forever has its limitations. Does that mean the technology is useless? No, it means the use case is different from credit cards.
It seems possible to build payment systems on top of Bitcoin that fills those use cases, and sidechains and payment channels are research along those lines. But just as crypocurrencies were a theoretical possibility twenty years ago, one should not expect working products too soon. It's not like there is a shortage of payment solutions in the meantime. For end users, credit cards offer a negative cost, so even then we should not expect the use cases to be identical.
Not that this is a whole lot better, but the cost is $1.48 for fastest confirmation time, and $0.42 if a delay of 15-300 minutes is acceptable to you.
Source: https://bitcoinfees.21.co/
Paypal transactions, Swish (Sweden), etc. etc. are instant and often with zero fees.
* Fee is not dependent on amount of money you're sending. You can send $200M worth of Bitcoin to a company in China and it will only cost you $1.50, try doing that with a wire transfer.
* Transactions are "final": after 3-6 confirmations you can have a great degree of confidence it won't get reversed
* Compared to Western Union or MoneyGram, it's still faster and cheaper
But in its current state, bitcoin is definitely not a replacement for your Visa card when buying groceries at the store. Maybe Lightning will change that though.
2. So, if transactions cannot be reversed, and I erroneously send money, or am tricked into sending money, I can't get it back?
3. So, BitCoin wins only when compared to Western Union and MoneyGram. Oh, what an achievement.
In it's current state bitcoin isn't a replacement for anything, really
Further the almost rabid attacks against a 2mb increase are bordering on complete insanity. No serious software engineer would say that an additional 1 megabyte of traffic every 10 minutes is a problem in any way. Instead we are stuck with a proportional increase in bandwidth and processing to support segwit and a minor increase in block size, which is through some convoluted logic preventing centralization. This whole thing is a power grab, plain and simple.
Now the alternative implementations are racing to complete something the miners will agree with, the sole purpose being to wrest control away from the "Bitcoin core" development group which has made some a complete mess of governance. Anyone who invested in Blockstream has to seriously be scratching their heads and wondering why they are killing the golden goose over some ideological bs instead of making what is really a trivial change. I think at this point they have screamed so loudly for so long that back tracking would reveal them to be hypocritical in the extreme. To couch this whole debate as a rallying cry against centralized interests instead of a corporate power grab is completely absurdist.
The reason we got so far before blockchains were invented was that you've never get a paper in a CS conference if you built a distributed system that did not increase it's ability to handle more workload AT ALL when you add more nodes.
If 5 parties that don't trust each other 100% share a blockchain they get a lot of benefit from that. Upping that 5 to 500 or 5000 does not increase the value proportionately. That is, blockchains don't scale.
You might use a crypto with a fixed monetary supply, with fungible tokens, with permanent fixed inflation, etc. etc. The difference is that there's a choice and a market for these tokens.
There's also the notion that nation states wield a great deal of power through currencies, and that removing this power from nations may be desirable.
Anyone who thought that Bitcoin wouldn't be political, however, was badly missing the mark. All one has to do is see the intense ideological motivations for holding Bitcoin that many have.
For many, the consensus-generating nature of the network is the real interesting part about it.
The real issue, I think, is that the main chain must remain a practical option for those that value it. Discovering the 'fair' cost for this while maintaining a secure network is very much an open question, and ultimately the source of all the controversy.
Personally I'd like to see unlimited block sizes, where txn fees and block orphan risk reach an equilibrium, but it's very difficult to say whether this would create unworkable centralization pressure.
If you trust the developers, exchanges or even users to make decisions, then why not just make a BitcoinSQL where the servers are controlled by these groups?
Mining specifically allows for this not to happen. one-CPU-one-vote as per Satoshi's paper. No matter the rules of the protocol, the chain with most work is the one that most people agreed upon. This seems to me the only true democratic solution and I don't understand how anything else is possible.
With regards to fees being to high and miners actually liking that, that's bullshit, because miners (which are also users!) care about the health of the entire system. If something like SegWit will bring many more users, that's a win for them.
Let's not forget that anybody can be a miner! Miners aren't just these chinese groups of people. It's the only true democratic way of reaching consensus - anything else is really not a way to reach trustless consensus in my opinion.
That is false, nowadays.
> Let's not forget that anybody can be a miner!
Even if you repeat a lie a thousand times, it's not going to become true :) Bitcoin's mining algorithm is so simple that mining industry has specialized too much, and now the best technology for it is ASICs. You cannot mine (or rather, it's nowhere near profitable) if you don't have access to this kind of hardware.
And of course, claiming that anybody can have access to this hardware is very very debatable. The best indicator of how this is not accessible by everybody is how centralized this industry is nowadays (just look at the correlation between ASIC manufacturers and owners of mining pools).
IMVHO, ASIC hardware provides such a huge efficiency boost that even if everybody in this planet ran a mining raspberry pi, the ASIC manufacturers would maybe still own more than 51% of the hashrate.
At 2 MH/s per pi, times 7 billion people, you get a paltry 14 petahashes/s. That's a hair over 0.2% of the network...
You'd need three trillion raspberry pis to get half the network. Good luck with that!
[1] https://en.bitcoin.it/wiki/Non-specialized_hardware_comparis...
[2] http://lifehacker.com/how-the-raspberry-pi-3-benchmarks-agai...
Even if you repeat a lie a thousand times, it's not going to become true :)
Where is the centralization?
Also, the issue isn't as much ASICs as it is the free electricity in China.
If there was no centralization, people would still be profitable doing solo mining. Most of the pools these days are pools because they own huge mining datacenters already (not because they have a lot of miner-users).
https://medium.com/@johnblocke/decentralization-fetishism-is...
> The best indicator of how this is not accessible by everybody is how centralized this industry is nowadays
Pools do not control hash power, they merely organize it. That's not to say they don't play a major role in the politics of Bitcoin clients and rules, but to say they 'completely control' Bitcoin is wholly incorrect. These sorts of hyperbolic statements greatly degrade the quality of discourse on centralization.
However, in this case the Chinese government can take over these data centers on a whim. You can argue it's a different story when it's spread across a million basements, but highly centralized hashing power is easy to either take over or take offline.
There is very little friction to changing pools.
Which chain has more work is approximately saying 'which chain destroyed the most value in electricity'. The proof of work powering bitcoin costs hundreds of millions of dollars per year.
Nobody burns hundreds of millions per year for free. They do it because you receive Bitcoins as payment, and then you can go sell those Bitcoins to pay your electricity and hardware bills.
That means you have to be able to find someone willing to buy them. A UASF is a bunch of users saying 'we'll never buy your coins unless you follow our fork'. If only a few users say this, it's no big deal, and the miners can decide to listen to them, or they can decide not to bother.
But if 2/3rds of the userbase all agree to enforce the UASF, the miners suddenly are going to have a lot of trouble selling their non-UASF coins. Enough trouble that they probably can't pay their electricity bills. Even worse for the miners, the UASF chain has a high block reward, so they know that if they do mine the UASF chain, they actually will be able to pay their bills. And if a competing miner does it, that competing miner will have much higher margins, higher profits, and will be able to out-invest you when it comes to buying more hashrate.
Scariest of all, if the UASF chain ends up with more work than the non-UASF chain, the non-UASF chain gets completely obliterated, and its full transaction history is reversed, and all the blocks you mined as a miner are destroyed. So even if the UASF doesn't seem to have majority support, it's really bad for you as a miner and as a user if it ever eventually does gain majority support. So when the UASF has a lot of traction, really the safest move is to join the UASF, because at least then your coins aren't at risk of being eliminated entirely.
Yes, but that is only if UASF gets a significant portion of the miners to switch.
This is also why Bitmain has publicly announced the UAHF, to hard fork away from the original chain, to avoid this possible scenario.
How about Bitcoin owners instead? Your vote is proportional to how much you have.
"He who has the chips, makes the rules."
The problem with your understanding is two-fold: first, "one CPU, one vote" sounds very egalitarian, but in practice it just means people buy vote share and therefore control.
The second is the idea that democracy is a perfect consensus system. That's only true if nobody agrees to fork.
No social contract is written in stone (despite millennia of efforts to do so).
I don't have much time right now, because I am at work, but maybe later I either post more or a better link.
To be very short: Bitcoin has not been thought to give miners all the power. In the contrary, their main function is timestamping the transactions! And not much more. Full nodes (or hopefully in the not too distant future advanced-spv-nodes) that should be run by many people (at least the conomic important ones, like exchanges, ...) do also verify the correctness and reject miners if they lie or don't behave in the economically-majority intended way! Miners are there so that we know what we (full nodes) should verify (and not blindly believe). Without miners we would not know which blocks to verify (there would be near infinite opinions/blocks). Miners make the choice what to verify just smaller, it doesn't make it automatically the truth.
Here a comment that shows that it was written from day 1 like this in the whitepaper:
https://www.reddit.com/r/Bitcoin/comments/6hefd8/comment/diy...
(not the best link, but ok for now. And of course economic majority is not a clear thing, but that doesn't mean that miner alone have the power. Beside miner there are the exchanges, the users, the api-providing companies, ... often grouped in 4 categories if you look at videos from Andreas Antonopoulos)
How the software functions is the subject of the old-fashioned open source project. This is also the weak spot. If you want to increase the number of available Bitcoins, your first step is to convince all developers on the project.
You are missing one of the key economic components of Bitcoin. Mining costs a lot of money. Nobody mines for free or at a loss, because 'at a loss' means to the tune of hundreds of millions of dollars.
Miners unquestionably mine the chain that has the highest block reward. Historically, hashrate has always been a function of $hardware_efficiency * $block_reward. If the block reward goes down, hashrate goes down (except where hardware efficiency is increasing fast enough to compensate). This is a lot more visible in the altcoin world, where miners can easily jump from coin to coin, and do as the coins fluctuate in value.
So what determines the price of the coin? Well, supply and demand. If people don't like your fork, there will be low demand, and your fork will have a low coin price. This will result in low hashrate, because miners aren't going to be willing (or even capable) of mining your fork at a loss.
Consensus ends up being fundamentally driven by the economics, and the economics follow the userbase.
The very fact that miners are beholden to the economics is the key innovation in Bitcoin. It's the magic of the whitepaper.
> The incentive may help encourage nodes to stay honest. If a greedy attacker is able to assemble more CPU power than all the honest nodes, he would have to choose between using it to defraud people by stealing back his payments, or using it to generate new coins. He ought to find it more profitable to play by the rules, such rules that favour him with more new coins than everyone else combined, than to undermine the system and the validity of his own wealth.
It is precisely because miners have a vested interest in the economics of Bitcoin that they control the network. That's the magic behind 'Nakamoto consensus'.
> They vote with their CPU power, expressing their acceptance of valid blocks by working on extending them and rejecting invalid blocks by refusing to work on them. Any needed rules and incentives can be enforced with this consensus mechanism.
IMHO, the percentage of technical signalling will not even matter that much.
Two chains will get created quite quickly. And some BTC holders will try to take advantage of the situation.
Since transactions can get replayed on the other chain (and copying them from one chain to the other brings a stability advantage) the technical way things are going to occur is double-spending to different adresses.
... Which means services supporting different chains will be pitted against each other.
Users will empty out one wallet at the same time to one exchange on a chain they don't support, and to another address they control on the chain they support. In cashing out on the exchange, they will crash the market value of that chain.
... Which brings me to: exchanges should start signalling support and come to a consensus pretty quickly, in their own interest. They don't want to be the exchange everybody cashes out on.
Questions abound:
* Have they started signalling it?
* What software are they running?
* If you hold some BTCs: are you planning to double spend?
* How are you going to proceed?
* Which chain do you support, and how many BTC do you possess?
TL;DR: There will be a run. Exchanges will determine the outcome.
Exchanges should make it pretty clear on which chain they will be operating, still.
I don't think trying to process transactions on both chains would be the right move.
Why is that? Wouldn't this be the most profitable approach for an exchange?
"After the event you might end up with gold or lead it all depends if your banker believe in transmutation or not (and if transmutation is actually achievable which will be determined by the best alchemists of the kingdom that need to agree together).
So all in all the guild of merchants recommend that you don't accept gold as a payement on the last day before new moon (and for a few day after that), because you wil not be able to tell if you are getting real gold or lead during that period.
Well to be honest it won't technically be lead you would get but forked gold, a gold that could be gold but isn't until the alchemists say so. But you shall still be able to use it in a limited way with people who believe in the same alchemists dissidents.
It's totally normal if it's sound complicated, it's magic after all!"
Nobody can steal your gold, but lets say the entire world gets together at once, and decides that gold is worthless and that they are moving over to lead as the new currency. But they are keeping the name "gold". Everyone now uses the name "gold" to refer to what was previously known as "lead".
Your pile of "real gold" wasn't stolen, but it may as well have been, because now it is just a bunch of heavy, worthless, shiny, rocks. (yes, yes, there are industrial uses, but the price is way way higher than what industry justifies alone)
And it really doesn't matter that you are strenuously arguing about how this "new gold" is actually lead, because nobody cares about your opinion.
That is a similar enough analogy to how bitcoin forks work.
It doesn't prevent it. If everyone decides to sell BTC now (including the big whales owning the major portion), it's price in USD will fall, too. How is this different?
In reality, our banking system is much more chaotic than what the end-user sees it because central authorities are keeping the whole system together. and their authority is just what all of us believe in. Now, some people, for better or worse, started believing in something new.
Though, the content itself is incorrect as well. Consensus has been achieved by the miners and by a few major payment processors, but not by the userbase. Blockchains though are very resistant to moves by major players, and even the miners being at 85% are not enough to force fundamental changes like this into the network if the users do not actively want to participate in the changes.
Note the wording there. The users have to opt-in to a change like this. It's opt-in, not opt-out. I'm very doubtful that software which is not even out in the wild yet is going to be able to get a majority of users to opt-in within a 3 week timeline.
We will know soon enough for sure.
Bitcoin consensus is definitionally achieved by miner PoW. Yes, they are beholden to market pressure from users, but saying that concensus is "by the user base" is misleading. I'm using the terminology from the bitcoin white paper
If the userbase is not interested in a coin, it will not matter how much hashrate is behind the coin, or how many figureheads try to prop it up. That coin will not have value.
Can you imagine the uproar if Visa said the same thing? It would be totally unthinkable.
Bitcoin can get away with this type of "disruption" because it's not really being used for anything other than a speculative vehicle.
We are doing a hardware presale using Bitcoin, and we're going to have to stop accepting Bitcoin at that time (it's a cryptocurrency miner, 90% of our sales are in Bitcoin), and that's going to hurt us.
This whole situation is frustrating.
No, that's exactly what Visa says, they call it chargeback. That's why it is hard to buy bitcoins with bank cards.
Who do I call if bitscoins just evaporate from my wallet thanks to this fork?
Bitcoins transacted before July 31 WILL stay in your wallet. They are not going to evaporate any time soon.
But now that you bring up governance, bitcoin is essentially being steered by a handful of mining pools, not by loosely knit community of private individuals :)
If you as a business accept(ed) Visa payments in Zimbabwe's currency in 2008, or Venezuelan bolivars over the last few years, you absolutely can have its value disappear from you.
This is not a fair representation of what the article says. It doesn't only say that coins you've received may lose value, it says that there's no guarantee the network will recognize the contents of your wallet in the future.
A more accurate analogy would be me handing you a crisp $100 bill which you place in your wallet, and tomorrow when you go to retrieve it, it has vanished into thin air.
Even a turd of a currency like ZWD won't materially vanish. You just have to spend it as quickly as possibly after you receive it, while it still holds value.
In that unlikely but possible scenario: Your wallet would have received coins on Chain A, but the majority of the network now favors Chain B and as a result is ignoring Chain A.
You still have the private key to coins and can spend them on Chain A. It's just problematic because they're on a chain fewer people value. Fewer, but not zero. They will still have some value, just less, and will be able to be sold out of band for coins on Chain B if desired.
This has already happened with Ethereum [1]. Each chain has its own exchange rate.
> Even a turd of a currency like ZWD won't materially vanish. You just have to spend it as quickly as possibly after you receive it, while it still holds value.
The ZWD's rate of inflation was at one point at 79,600,000,000% [2]. We are getting pretty abstract if we're going to debate how close that is to materially vanishing.
[1] http://www.coindesk.com/ethereum-classic-explained-blockchai... [2] https://en.wikipedia.org/wiki/Zimbabwean_dollar#Withdrawal_o...
Also, you can use ZWD notes as kindling. :)
If the network splits there will 1 or 2 new types of Bitcoin.
If the exchanges decide to support the new types of Bitcoin you will be able to sell your holding on the new chains whilst still keeping coins on the main Bitcoin chain.
But to do this you need to manage your own private keys.
Alerts: BIP148/92: change title over objection
Note: I object to this change, which I think makes the alert
less clear, less forceful, and degrades alert usability.No one is betting that the current version of Bitcoin is the future of currency. They are betting that the version of Bitcoin that exists in 20 or 30 years is the future of currency.
I don't think it'll replace currencies, but I think it will serve a purpose as a means to transfer value when authorities don't want you to transfer value.
Not saying if this is a good or bad thing, but it is a real value proposition.
because using sha256 for proof of work was a mistake - it's too easily implemented in specialised hardware.
now mining power is centralising and small groups can manipulate blockchain policies in their own interest.
bitcoin should PoW-chain to a memory-hard hashing algorithm.
You talk about decentralization but it's not shown, and may not even be possible, how the LN should work without relying on centralized hubs.
That said- this is a legit notice and is probably good advice. This is a contentious upgrade.
The Segwit2X and Core factions agree on Segwit. Core doesn't like later doing a 2MB hard fork, but most of us think it's a reasonable compromise. There won't be a lot of complaining.
The real threat is Bitmain which wants to do its own hard fork, that will NOT be compatible with Segwit, which they intend to mine privately and which will have unlimited block size:
https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
That's what the original post is about. That fork is very dangerous.
If the soft fork fails, Core developer Luke-Jr said they'd change the Proof of Work algorithm and possibly create an altcoin (or bitcoin if enough follow).
This is like a Russian Roullete situation. The gun's loaded, all signs point to neither side conceding. It's the cypherpunks vs the corporate miners (plus some former devs and very credible people).
There are three factions here-- Segwit2X and Core, who both want segwit, and Bitmain which does not want segwit and which has threatened a forcible hard fork into a bitcoin that has unlimited block size-- and they are even talking about doing an ICO and things like that:
https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
And Luke's subsequent comment said if enough followed then it could still be called bitcoin.
Also Maxwell said he'd quit if BIP148 fails. If the soft fork fails, bitcoin will be something different.
There are currently two main ideas on how to scale Bitcoin. One camp is the called Bitcoin Unlimited and it's a proposal that allows the miners to adjust the block size as needed.
The other idea is called Segregated Witness or Segwit. This is a change in the way bitcoin transactions are counted towards the 1MB per block limit. It will allow slightly more transactions per block but also adds functionality that could allow other types of transactions. Those will be useful in some situations, e.g. paying the same entitiy many times over the course of the relationship.
Some people in the Segwit camp are tired of waiting so they are attempting to force the issue without the support of most miners. The date they picked is Aug 1.
Since very few miners support this move, it's not likely to succeed in my opinion, but nobody knows for sure.
I don't understand why the bitcoin.org page sounds so alarmist. If the miners are not in on it why would some special Bitcoin blockchain (with alternative rules) matter, since miners could easily DoS this chain, if they wanted to, in case they don't support it?
Anyone can create their own chain with non-agreed-upon-rules (e.g. testnet3 or regtest), but that's just not Bitcoin precisely because it's practically ignored by miners (like a UASF).
Are bitcoin.org, themselves, supporters of this UASF?
If the community is behind it, then a POW change would render the 10s/hundreds of millions of dollars in mining equipment worthless.
So the real question is whether or not the UASF side has the support of the community or economic majority.
You change the proof of work algorithm so that the existing miners can't use their fancy Bitcoin miners, and it becomes profitable to mine with GPUs instead.
Peercoin is one of the first working proof of stake implementations that has been running for close to 5 years now.
Yes.
Both sides have proposed ways forward, only to be rejected by the community. A large number of companies and miners in the space came together recently in New York to agree on a compromise. The New York Agreement (NYA) was to combine two of the proposals- Segregated Witness, a soft-fork that provides some new features and a modest capacity increase, and a 2-MB hardfork.
In response, extremists on the "small-blocker" side have declared that they'll likely force a chain-split on August 1st via a so-called "use-activated soft-fork".
Now it's time to see what the market thinks :)
The bitcoin.org page says:
> Do not trust any payments you receive after Tue Aug 01 2017 02:00:00 GMT+0200 (CEST) until the situation is resolved. No matter how many confirmations the new payment says it has, it can disappear from your wallet at any point up until the situation is resolved.
Which I don't understand, unless miners are actively trying to make this happen (by mining on two different chains with roughly the same hashing power). According to the paper[1], as long as at least 20% of the hashing power is honest, 11 confirmations should be final (in 99.9% of cases)
[1] https://bitcoin.org/bitcoin.pdf (page 8)
There is nothing that prevents 2 forks from existing for an indefinite amount of time, just look at ethereum and ethereum classic.
The question of the year is whether one side will suddenly crash down to a price of 0.
If the UASF has majority economic support (unlikely) and also the miners do not support it, initially the UASF side will be behind, and there will be multiple chains. There will be the UASF chain and the normal chain.
But since the UASF has more support, it'll have more block reward, and eventually it'll have more hashrate behind it. It'll eventually catch up to the other chain, pass the other chain, and then...
The other chain completely implodes, and stops existing. Yes, that's actually what happens, and why if you are a miner, you should be afraid of the UASF. You lose basically everything if the UASF ends up with more hashrate, and the UASF is eventually guaranteed to have more hashrate if it has a higher coin price.
----
Basically, your doomsday scenario dramatically understates the worst-case scenario.
Are you sure? If I'm not wrong, this isn't that much different from Ethereum/Ethereum Classic situation.
Ethereum Classic's price is no where near Ethereum's but it is still maintaining a good position - 5th by Market Cap and 3rd by 24hr volume.
You are saying the ALL of the mining power will eventually move over, but what if it doesn't the miners (85% of whom support Segwit2x) stay on the non-UASF fork?
UASF Bitcoin will be very weak, so I can't expect what would happen, but I'm just saying its not so simple.
ETC's price is being pumped up (some more context can be found on /r/ethereum), in some cases by taking advantage of newcomers looking to get into the ETH craze, helped by the fact that the Ethereum Foundation doesn't seem interested in maintaining ownership how the word "Ethereum" is used. There's no real technological innovation or developer interest in ETC.
>There's no real technological innovation or developer interest in ETC.
I mean, ETC guys can just push all of the new developments in ETH to their code. The codebase is the same. There probably won't be any original developments in ETC, but they don't really need much to stay on par with ETH.
Here's an intro (google around for more): https://www.reddit.com/r/ethtrader/comments/6d62td/the_story...
https://medium.com/@charlescmackay/barry-silbert-and-the-cos...
Not saying ETH is perfect, far from it, but ETC is a pumped up scam for sure. They're using "Ethereum" in the name to fool newbies, likely propping up the price at current levels. I seriously doubt anyone know is knowledgable/not in on the scam really invests in a coin that is identical to ETH but none of the leadership, community or dev interest.
Now that that's out the way, let me say the cognitive dissonance in that post is palpable. Words are conveniently placed so spin the situation into something else.
r/Bitcoin is shown to be the culprit here, just because they are the ones with the most subs and poking fun at ETH. The reality was every other altcoin community was doing the exact same thing. I was watching everything closely when as it unfolded. I can link you posts from other subreddits if you want.
>The Ethereum community stuck together, worked together, and fought back. Successfully
This is false. Quite a few of the ETH community fought for not forking. No one wants to lose money, so who wouldn't want to fork. Many vocal people invested quite a bit of their funds so it is completely understandable.
The irony here is, even the 'rogue hackers' were probably part of the ETH community. Who else would know the codebase so well? The phrase 'stuck together' is false.
>Barry Silberts co-owned exchange "Poloniex" raced to be the first exchange to start trading the coin of this old chain (ETC)
Looks like something a smart person would do. I would also capitalize on trades that people will make with ETC. You've immediately got twice the volume therefore double the fees that can be collected. This is clearly a good business decision. Doing that before other exchanges means more fees collected!
>ETC is an Attack against Ethereum
That's a bold claim. I don't see any 'attack'. Any person with half a brain can see which one is the original ETH. It is a fork, so calling it an attack is dramatic.
>It's a technological attack, and a monetary scam
Big words. I don't see any technology being used to attack ETH. Just people mining the coin they support.
>If you have bought, or holding, or still planning to buy ETC, be ready to get hit by some nasty surprises down the road ( on those days - and I can already foresee a few - I will be linking everyone back to this thread right here, as a reminder).
Now who sounds like they are spreading FUD?
-------------------
While Poloniex was made out to be the perpetrator, it has only 5% of the 24hr transaction volume. So pointing fingers at the Poloniex person was baseless and foolish.
I believe in a bright future for ETH and will probably get into it, but falsifying events is a great way to show others that the community can't self-police and is an echo chamber.
If we end up with Bitcoin and BitcoinSW, and BSW is the minority (like Etherum Classic), we'd have a situation like today. Except, if BSW were to ever catch up to Bitcoin in total work, when it passed Bitcoin (51% hashrate is enough to cause this), it would obliterate the original chain, and become the only chain.
This property is why we gave it a new name (UASF).
Nodes can continue to follow it if they feel like it, and change their code.
There is nothing that stops someone from saying "yes, this chain has less proof of work, but I don't care".
You could argue that this would cause the old chain the be less valuable, but the old chain doesn't literally get deleted from people's hard drives in all scenarios.
The Wipeout scenario is overhyped, because of how nodes can choose to follow the old chain if they feel like it.
IE, old nodes would effectively be soft forking by adding a check point onto the old chain.
The limitation is in the protocol, or rather, its current implementation with the 1MB blocksize limit. It was originally implemented to make growth a little more predictable in the beginning, nothing else. Satoshi himself said that it's only to prevent spam, which was at a time before growth, when it wasn't obvious yet how well the self regulation with TX fees works.
After Satoshi disappeared, other people took over the development, and disagreements over how to continue began. What was mostly a technical argument at one point, became a political argument after Blockstream formed, which had taken investments from banks and had most of the core developers under them.
These then not only pushed for other means of scaling than just removing the blocksize cap, but also actively pushed against that, which split the community in half.
Now we have people who (very simplified) just want the blocksize cap increased, and others who support the scaling methods of Blockstream, namely segwit and, down the road, lightning.
This endless debate with both parts of the community calling the other's solution unsafe is what is currently crippling Bitcoins potential.
1) currently, only about 6 blocks can be verified by the network per hour. That is fixed, any faster and the difficulty rises. Any slower and the difficulty declines. With the current code in use, it will always be about 6 blocks per hour.
2) currently, blocks are limited to 1MB in size. This means that only a certain number of transactions can be processed per block (apx 1200 to 2500).
Thus, only 24 * 6 * #txns_per_block => 170k to 350k transactions can be processed per day. It doesn't matter how many computers are verifying new blocks in the blockchain. This is an... issue.
Note, a "transaction" is moving BTC from one wallet to another wallet.
Remember though- if you don't have any Bitcoin under your own control (non-custodial wallet) you might not be able to trade between chains if there's a split. There are only two exchanges with announced pairs AFAIK- BitFinex and ViaBTC both have futures contracts set up.
But, eh, if crypto ever completely replaces raw mineral as a trading mechanism, I guess there's still 200x potential there. https://howmuch.net/articles/worlds-money-in-perspective
So, as long as the combined value of every version is approximately around the value of the original version, you haven't lost any money.
Then, wait for the dust to settle, sell the coins for the versions you don't like, buy coins for the versions you do like, and then resume using Bitcoin like you had originally.
The altcoin market is pretty upside down right now, even more than Bitcoin is. It's probably less safe to move to an alt than it is to just ride through the bitcoin storm.
I believe copay is okay from a brief glance, but I honestly can't tell if they give the keys to Bitpay for backup or not.
The safest wallet is bitcoin-core, though there are plenty of reasonably safe options.
I know a couple people who have some bitcoin on Coinbase and aren't too comfortable moving it to a local wallet (Coinbase is just easier for them, they don't have to worry about the security of their personal computer).
Does Coinbase allow making a local backup of private keys? I'm thinking they might not, but maybe they do.
1. Ensure that you have no BTC deposited with a Bitcoin bank or other trusted third-party before Aug 1. If there's no technical way for you to export the private keys for your BTC, then that BTC is at risk. Some Bitcoin banks may assure you that they'll definitely keep your BTC safe, but I absolutely wouldn't trust them.
2. Do not send transactions or trust received transactions starting 12 hours before Aug 1 at midnight UTC, and continue this until you hear the "all clear" from several trustworthy sources. For example, I will post a forum news item if everything is OK, or if everything is not OK and action is required.
Bitcoin is a consensus system. This means that the goal is to have everyone believe the exact same thing at all times. Bitcoin achieves this by having everyone run identical software which is able to compile a list of transactions, and from there decide what money belongs to which person.
As you can imagine, it's a problem if you have $10, and Alice believes she owns that $10, Bob believes he owns that same $10, and Charlie believes that the money was never sent to either of them. These three people can't interact with eachother, because they can't agree on who owns the money. Spending money has no meaning here.
In Bitcoin, there are very precise rules that define how money is allowed to move around. These rules are identical on all machines, and because they are identical for everyone on the network, nobody is ever confused about whether or not they own money.
Unfortunately, there are now 3 versions of the software floating around (well... there are more. But there are only 3 that seem to have any real traction right now, though even that is hard to be certain about). Currently, all versions of the software have the exact same set of rules, but on August 1st, one of those versions of the software will be running a different set of rules. So, depending, people may not be able to agree on the ownership of money. If you are running one version, and your friend is running another, your friend may receive that money, or they may not. This is of course a bad situation for both of you, and its even worse if you are working with automated systems, because an automated system likely has no idea that this is happening, and it may have no way to fix any costly mistakes.
It gets worse. The version of the software that is splitting off actually has the power to destroy the other two versions of the software. I don't know how to put this in simple terms either.
In Bitcoin, it is possible to have multiple simultaneous histories. As long as all of the histories are mathematically correct (that is, they follow all of the formal rules of Bitcoin), you know which history is the real history based on how much work is behind it. The history with the most work wins. If the history is illegal, you ignore it no matter how much work is behind it.
So, this troublemaker version of the software (the UASF version) has a compatible set of rules with the other 2 versions. Basically, everything that it does, the other versions see as valid. So if its history is the longest, the other versions will treat that history as the one true history. The thing is, this troublemaker version of the software is stubborn, and so even if the histories of the other two versions have more work, it'll ignore them and focus only on its own version of history.
So, the dramatic / problematic situation happens if the UASF software initially has less work in its history. What'll happen is a split, and two different versions of Bitcoin will exist at the exact same time. But then, if the UASF software ends up with more work after some period of time (days, weeks, etc.), the other versions of the software will prefer its version of history over their own.
Basically, what happens there is that entire days, or weeks, etc. of history get completely obliterated. The UASF history becomes canonical, and the histories built by the other versions all get destroyed. Miners lose all of their money, people who accepted payments lose those payments, people who made payments get those payments back. Basically a lot of chaos where people end up losing probably millions and millions of dollars.
----
I hope that helps. This whole situation is screwed up, and really the best thing to do is to put your coins in a cold wallet (one that you control, not an exchange), and then just not send or receive any coins for a few weeks. Let the dust settle, and then resume using Bitcoin once its clear that the turmoil is over.
----
The most likely situation here is that nothing interesting happens at all. My personal opinion is that the vast majority of people who matter in Bitcoin aren't even paying attention to the drama, and something dramatic is really only possible if the majority of Bitcoin users opt-in to doing something. I don't think that's the case at all, which means essentially nothing interesting is going to happen.
But, I could be wrong. There's a non-zero chance that something very unfortunate happens, and there's a pretty easy way to isolate yourself: don't send or receive any Bitcoins starting July 31st, and don't resume until it's clear that the storm has passed. It'll likely take less than a week to come to a well-defined conclusion.
Frankly, even if the compromise solution fails and the fork does happen on August 1, it will be a complete non-event. Bitcoin.org is biased as they are affiliated with people who support the August 1 fork, and so they're attempting to publicize it. However, the fork has practically zero support from Bitcoin miners or exchanges. On Aug 1 the vast majority of miners and exchanges will stay with the current network. Without significant miner support the forked network will run extremely slowly, and it will be vulnerable to several kinds of attacks. Without exchange support the forked network will not have economic value, and will quickly become irrelevant.
Although August 1 will likely not be a problem either way, there is another date that will. Around the end of October, another proposal to fork the network is scheduled, and this one is supported by miners and exchanges. What will happen then is much more murky. It will become clearer as the date approaches.
The threat is that BitMain, the controller of a very large amount of hashing power, something like %70 is threatening a hard fork into their own, non-segwit chain:
https://blog.bitmain.com/en/uahf-contingency-plan-uasf-bip14...
Core absolutely does not support Segwit2x, because of the hard fork later. If they do, why don't they merge it and end this standoff?
Should be a bit more informative than TFA.
1. What percentage of Bitcoin's PoW belongs to Bitmain?
2. Are the drivers for Bitmain's hardware free-as-in-freedom?
3. Is mining hardware in the same class as Bitmain's manufactured anywhere in the world other than China?
Edit: Bonus question: If all cutting edge hardware tends to be developed and manufactured in one particular spot in one particular nation state, and if Bitcoin mining efficiency now depends mainly upon the manufacture of newer, more powerful hardware, does that change any of the implicit assumptions made in the Bitcoin whitepaper? (Esp. considering that same nation state has put a hard speed limit on all data moving in/out its borders.)
Just suspend your trading near the date until this kerfuffle sorts itself out and you should be fine.
India Standard Time is something like GMT+5.
Note that the page has "2017/08/01 00:00 UTC" in the source, but uses a "Localize dates" JavaScript function to change that to your configured time zone.
https://medium.com/@jonaldfyookball/mathematical-proof-that-...
Edit: responses to the specific "proof" you linked
https://medium.com/@murchandamus/i-have-just-read-jonald-fyo...
https://medium.com/@murchandamus/some-subsidiary-points-on-l...
https://hackernoon.com/simulating-a-decentralized-lightning-...
This thread on the same story discusses other issues with LN proposals, one that stands out to me is how routing is going to work if all nodes are perfectly equal - routing on the internet relies on a hub model, seems likely that a decentralised routing protocol adds even more complexity and resource requirements.
https://news.ycombinator.com/item?id=14759965
The trouble of course is that LN is just a bunch of proposals right now, each promising to fix all of Bitcoin's issues without removing all of its unique features. When it actually exists then I'll revisit, but until then I'll treat it as another piece of vapourware.
There are multiple implementations of the spec.
Why is this happening?
85+% of miners are signaling support for segwit2x, so it's extremely unlikely that there will be any disruption. https://coin.dance/blocks