segwit2x / segwit2x.github.io Goto Github PK

I personally don't care or support 1Mb (or whatever random increase SegWit provides). But people who opt-out should still be advised how to opt-out safely.

There should be clear recommendation on how to use replay protection and/or split your coins. Furthermore recommendations for exchanges should be given how to handle the transition as clear and safe as possible.

~90% of miners upgrading is a strong market signal, but it cannot (without reasonable doubt) be considered the entire market. Therefore recommendations for how to list btc1 and bitcoin core should be given. Even if the market gravitates towards btc1 almost immediately and concisely.

Regardless of the viability of the Core/NO2X chain, exchanges will continue to trade it, and if it is traded it can become viable again. It is irresponsible to not take this possibility into account, and not to advise accordingly.

IMHO advice towards exchanges should be:

1. Halt withdrawals temporarily,
2. Either list BTC/Bitcoin as the combined token (Btc1 + Core), or split the token into BTC-2X and BTC-CORE.
3. Explain how to split coins.

Then the market can decide whether BTC-2X or BTC-CORE gets the BTC/Bitcoin moniker. And then exchanges should list both accordingly.

Advice towards users should be:

1. Explain how to split coins.

enough forks already, please stop the nonsense

The least u can do is implement replay protection. Ugly people

Hi,

I just did a set of minimum changes to the core codebase according to the specifications on the segwit2x-announce site, to test a "cleanroom implementation" without looking at the btc1 codebase.

But when I ran that client on testnet5, it stalled on block 33923 and disconnected all other clients.

Turns out, 33923 is the first block exceeding MAX_PROTOCOL_MESSAGE_LENGTH in size (which is 4MB by default in core), once I increased it, things were progressing nicely again and I can confirm that core-with-some-numbers-changed indeed follows the chain.

I would suggest adding a note about this to the site, so that it can serve as a minimum specification for building a compatible client.