Privacy practices for ECX trades
eCash (ECX) split off from Bitcoin at block 973,728, on 29 October 2026. It keeps Bitcoin's addresses and transaction format, changes a few rules (such as how difficulty adjusts), and adds drivechains (BIP300/301): optional side chains with their own rules, whose withdrawals miners approve. It is not XEC, the older coin also called eCash. The chain is transparent like Bitcoin — sender, recipient and amount are visible to anyone. Two things are particular to eCash: an eCash address is also a Bitcoin address, and coins held before the fork, or received since from such coins, can exist on both chains, so an unprotected payment can be repeated (replayed) on the other chain. The practices below cover what you can control.
Use a fresh address every trade
This chain uses transparent addresses with no native stealth. The standard practice: use a Hierarchical Deterministic (BIP-32) wallet that derives a new receive address per request. Most modern wallets do this automatically. The cost of address reuse is severe — every trade you accept at the same address builds a public record of your activity.
Universal practices
**Use a fresh receive address for every trade.** Your wallet should support this; if it doesn't, look for one that does. Address reuse is the single biggest leak.
**Practice coin control when spending.** When sending coins later, avoid combining the trade output with coins from another source — that combines their address histories permanently.
**Broadcast through Tor or your wallet's privacy mode.** Your home IP address sees the transaction first; nodes near your IP can correlate it to you. A Tor-aware wallet broadcasts through Tor by default.
**Avoid sending trade coins to or from KYC exchanges.** Once trade coins touch a KYC exchange, the trade becomes legally identifiable by combining exchange records with chain data. If you need to bridge to fiat, route through a self-custodied intermediate step.
What to avoid
- Do not paste your same receive address into multiple trades.
- Do not send the exact amount listed on the order — Morphit's amount-randomizer toggle (the "🔐 Randomize amount" checkbox in the address-share modal) breaks this; leave it ON.
- Do not combine the trade output with coins from a different source when you later spend it.
- Do not broadcast from your home IP via a non-private wallet — use Tor.
⚠ Caveats specific to this asset
eCash is transparent like Bitcoin, and shares Bitcoin's coins from before the fork. - **Split your coins before you trade.** Coins you held before block 973,728 (29 October 2026) exist on both chains, and so can coins you received since from such coins (a payment from unsplit coins can go through on both chains). Until you have moved them on eCash with replay protection, an eCash payment from them can be repeated on Bitcoin, and a bitcoin payment from them can spend your ECX. News reports say eCash's official wallet splits them for you. The eCash node's own wallet adds no replay protection unless you set it up yourself, so assume your wallet adds none unless it says it does. - **Pay from an eCash wallet only.** An eCash address is also a Bitcoin address. A Bitcoin wallet given that address sends bitcoin, not ECX, and you may not get it back. - **Keep eCash in its own wallet, once split.** A seed that held bitcoin before the fork controls the same coins on both chains. Once your coins are split, moving your ECX to a separate eCash seed gives them their own addresses from now on, instead of your Bitcoin wallet's. The move itself is public, and the coins' history before the fork stays on both chains. - **Share fresh addresses per trade.** Reusing an address lets anyone link your trades on a transparent chain; an HD wallet gives you a new one for each trade. - **The chain is young.** A new chain can reorganize its latest blocks more easily than Bitcoin. Wait for more confirmations before you treat a payment as final. - **Network-layer privacy still matters.** Broadcasting through Tor keeps your home IP off the network's view of you.
Morphit does NOT recommend specific wallet software. Even reputable wallets have been compromised or have had hidden flaws. The privacy techniques here are protocol standards, not endorsements — your wallet, your responsibility.