bones261
Legendary
*
Offline Offline

Activity: 1596
Merit: 1637


My hat is in storage. https://ibb.co/YLkPgXb


View Profile Personal Message (Offline)

Ignore
October 16, 2017, 05:04:22 AM
Last edit: October 16, 2017, 05:25:00 AM by bones261



So basically we're looking at a repeat of BCH. There will be a split, BTC will dump to make room for the new token/s, then the new token/s will slowly die, bleeding back into BTC. That the long and short of it?

Unfortunately, this fork, at its current state, is much more dangerous than BCH since the S2X devs have not enabled strong replay protection at this time. AFAIK, they briefly included some bullshit opt-out protection where people would have to include some dust transaction to a certain address; if they wanted the transaction to only be played on the BTC chain. (This would have effectively bloated the BTC chain)  However, I believe even that BS has been yanked. I hope Garzik does the right thing and implements strong opt-in protection. If not, this may be a mess. We could hope that no pool dare go through with it; just like they did with XT, Classic, and BU. However, S2X has a definite coordinated block number and an "agreement" with this fork. Therefore, many pools might be emboldened to take the plunge with this fork.

I'm hoping Slush implements an easy way to split my coins in my Trezor wallet. However, I think many casual users may end up losing coins. Some of these instructions on splitting your coins made by Bitmex make my eyes glaze over. https://blog.bitmex.com/segwit2x-b2x-hardfork-protect-potentially-profit-part-1-split-coins/