Author

Topic: Blockstream Core already shuffling story on SegWit2X to avoid yet another fork (Read 430 times)

legendary
Activity: 2870
Merit: 7490
Crypto Swap Exchange
Yet another delay. I think another group might create new proposal which require hard fork since BitcoinCash proven that it's way to earn free money.
But, can't we wait or use BIP 141 instead rather than wait for SegWit2x Huh
legendary
Activity: 3948
Merit: 3191
Leave no FUD unchallenged
Ultimately people can propose what they want, but that doesn't mean anything if the code people are choosing to run isn't taking that into consideration.  He can pontificate all he likes how he “expects the market concurs” with him, but preempting consensus is just presumptuous.  I'm happy to sit back and watch what happens.  Plus, if they wanted more time, then the UASF brigade shouldn't have escalated things with their little ultimatum.  This is what happens when you force peoples' hands.  You don't get to completely disregard your opponents views AND then get to bitch about it when they go off and do their own thing without you instead.  You can't have it both ways.  It's just childish.
hero member
Activity: 574
Merit: 500
Blockstream Core and Corecoin will stall forever and ever until Corecoin is dead. Thankfully we finally have Satoshis true vision in BitcoinCash and don't have to deal with toxic Core and their pathetic settlement shitcoin and stalling tactics any longer.

Buy and HODL BitcoinCash! It is the REAL Bitcoin!
legendary
Activity: 1372
Merit: 1252

It doesn't take Blockstream or any other group to try to avoid segwit2x. Segwit2x is just nonsense. Jeff Garzik wants to get anti privacy code on btc1 and they want to make btc1 take the lead.

Data shows we don't need 2MB. Mempool is fine, only not fine when Roger Ver spams the network. Rushing a hardfork in 3 months is just dumb. Let's hope miners realize their mistake so we don't have to go through a price crash thanks to big blockers again in 3 months, but that's all big blockers do: crash the price.
Jump to: