ECX coin splitting and replay protection

The fork does not automatically protect every transaction

The official replay-protection guide describes an opt-in marker: nLockTime = 499999999 on an ECX transaction, with input sequence numbers below 0xffffffff so locktime is enforced. The documented rule treats this as final on eCash, while Bitcoin rejects it as non-final.

The marker protects that ECX transaction from replay onto Bitcoin. Other transactions may remain valid on both chains. Identical-looking addresses do not identify the network, and merely changing the destination address is not the documented replay-protection mechanism.

What to verify before splitting

• Confirm which snapshot and network you are using. Beta is a rehearsal; mainnet is a new fork.
• Verify the wallet or node release through official download resources. Address-format compatibility alone is not enough.
• Back up keys securely. Never paste a seed into this website, a chat, or a claim form.
• Read the current procedure before moving unsplit pre-fork BTC. Do not assume that moving BTC first resolves replay risk.

The documented order of operations

The integration guide’s operator procedure splits the ECX side first: it sends pre-fork outputs to fresh ECX addresses using protected transactions, waits for deep ECX confirmations, and only then resumes independent BTC operations. A reorganisation that reverses a split can expose the outputs to replay again.

The guide describes BitWindow support for the user-facing split. Verify that your selected release and network actually support the procedure; this overview is not a transaction-construction tool. Custodians should test their complete deposit and withdrawal workflow on Beta before mainnet, and account for each chain separately.

What if an exchange holds my BTC?

The exchange controls the relevant keys. Its support, splitting process, and crediting policy determine customer access; ecash.com cannot split an exchange’s coins for you. Consult that provider before assuming ECX will be available.

Confirmations and remaining risks

The official guide flags early-network difficulty changes and reorganisation risk. There is no universal confirmation count that makes a transaction risk-free. Use current operational guidance and verify balances against the correct chain rather than inferring one chain’s deposit from another.

For the broader timeline, read what to expect at the fork. For balance eligibility and access, see the ECX holder guide. Integrators can start with technical fast facts.