Should be a bit more informative than TFA.
Bitcoin – Potential Network Disruption on July 31st
101–110 of 381 posts
Re: Bitcoin – Potential Network Disruption on July 31st
#102Earlier quoted context omitted.
The doomsday scenario is that Bitcoin forks for a long period of time, but then one fork down the road, crashes in value to worthlessness. 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.
No, that's not correct. In the case of the UASF, something very frightening is possible. 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…
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.
Re: Bitcoin – Potential Network Disruption on July 31st
#103Earlier quoted context omitted.
I'm really tired of hearing the "increasing the block size won't suffice"-argument. Yes, increasing blocks to 10 MB won't give us VISA-scale, but it will allow Bitcoin to serve TEN TIMES AS MANY USERS! I can't believe how many otherwise intelligent people fail to see that this is desirable. It's like driving your car at 10 km/h per hour on the high-way and refusing to increase your speed because that would still not…
Well - increasing the block size is not costless - it is not just pushing the gas pedal a little more like in your example.
Re: Bitcoin – Potential Network Disruption on July 31st
#104Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. 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). Ho…
So this all sounds pretty scary and gloomy, so why is BTC/USD trading up $86.00 in the last 24 hours? Shouldn't it be getting hammered? Is this a buying opportunity then?
Re: Bitcoin – Potential Network Disruption on July 31st
#105It will surely affect on ransomware collectors.
Re: Bitcoin – Potential Network Disruption on July 31st
#106Earlier quoted context omitted.
I'm really tired of hearing the "increasing the block size won't suffice"-argument. Yes, increasing blocks to 10 MB won't give us VISA-scale, but it will allow Bitcoin to serve TEN TIMES AS MANY USERS! I can't believe how many otherwise intelligent people fail to see that this is desirable. It's like driving your car at 10 km/h per hour on the high-way and refusing to increase your speed because that would still not…
Well - increasing the block size is not costless - it is not just pushing the gas pedal a little more like in your example.
Re: Bitcoin – Potential Network Disruption on July 31st
#107Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. 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). Ho…
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...
Re: Bitcoin – Potential Network Disruption on July 31st
#108Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. 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). Ho…
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.
Re: Bitcoin – Potential Network Disruption on July 31st
#109Earlier quoted context omitted.
It is probably not possible to solve the scaling problems on-chain - a secure decentralized consensus on a global scale cannot be fast. Currently the bitcoin protocol processes about 7 transactions per second. Doubling the speed by doubling blocks will not make it much closer to the 50K transactions per second of a system like VISA. But it is probably possible to scale the transaction system off-chain - with https://…
A counter-argument is that the Lightening work is a proprietary development outside of bitcoin core (lead by Blockstream) and the work is even patent-encumbered. 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…
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.
Re: Bitcoin – Potential Network Disruption on July 31st
#110Well, that's a remarkably uninformative announcement. Here's an attempt at a neutral tl;dr from a Bitcoin amateur. 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). Ho…
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 (which in the past have had backdoors). They profit from using an exploit called ASICBOOST. 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 softwar…
> 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: