[Bitcoin-segwit2x] F2Pool backing out of NYA - Fork still happening?
kekcoin at protonmail.com
Sun Oct 15 12:41:33 UTC 2017
> Bitcoin2x lacks wipe-out protection
Incorrect, B2X has wipeout protection in the form of a "must be big" requirement on the hardfork-blockheight. See https://github.com/btc1/bitcoin/pull/50
Sent with [ProtonMail](https://protonmail.com) Secure Email.
> -------- Original Message --------
> Subject: Re: [Bitcoin-segwit2x] F2Pool backing out of NYA - Fork still happening?
> Local Time: October 15, 2017 12:20 PM
> UTC Time: October 15, 2017 12:20 PM
> From: bitcoin-segwit2x at lists.linuxfoundation.org
> To: David A. Harding <dave at dtrt.org>
> Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org>
> My other point was as per breadwallet"s explanation of the
> malfunctions they so far expect of their SPV wallet, which chain
> followed is chaotic and dynamic because the Bitcoin nodes will ban
> nodes that send them invalid blocks, and phone wallets select nodes
> somewhat at random from peer caches and seeds.
> It is a dynamic and high risk situation, and also existing wallets
> will be changing in a rush to avert disaster so that there is not a
> stationary behaviour to test with. (Most phone wallets have auto
> upgrade features).
> The node ban has bi-directional effect, but given Bitcoin2x lacks
> wipe-out protection there is risk of full re-org incurring funds loss
> for 2X users.
> Greg Maxwell wrote about some other scenarios here
> The full matrix of what can fail in this dynamic situation not fully
> understood and analysed (by anyone).
> Ben Davenport and James Lopp (CTO and lead architect at BitGo), are
> also warning about these kinds of issues.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bitcoin-segwit2x