Last updated: 2026-08-11, pre-launch.
Technical parameters come from the live drynet4 dry-run network and the drynet4 branch of ecash-com/bitcoin. Final launch parameters (fork height/hash, branch/tag, replay scheme) will be published at drivechain.info/dev.txt and ecash.com. Re-verify anything marked drynet4 before go-live.
| Asset | eCash, ticker ECX |
| What it is | Hard fork of Bitcoin by LayerTwo Labs, activating drivechains (BIP300/301). Every BTC address is credited ECX 1:1 at the fork block; BTC itself is untouched |
| Fork point | BTC block ~963,648, targeted August 22, 2026 (~15:00 UTC) |
| Consensus | SHA-256d PoW, one-time difficulty reset to minimum at fork, then normal retargeting |
| Node software | Fork of Bitcoin Core v31.1: github.com/ecash-com/bitcoin; binaries at releases.drivechain.info |
| Address/key formats | Identical to Bitcoin (1.../3.../bc1..., same WIF/xpub/xprv, secp256k1) |
| Network identity | Own network magic (0xeca5d404) and ports 8533/8532 as of drynet4, so nodes can't cross-connect with Bitcoin Core; getblockchaininfo still reports chain=main (details) |
| Replay protection | Opt-in: set nLockTime = 499999999 on eCash transactions (details) |
| Consensus quirk | 220 whitelisted "repurpose" transactions reassign Satoshi-era (Patoshi) coins without signatures |
| Mining | SHA-256d, any Bitcoin miner works. Public pool stratum+tcp://pool.drynet4.drivechain.dev:3333 (details) |
| Sidechains | 7 drivechain L2s at launch (Thunder, zSide, BitNames, BitAssets, Truthcoin, Photon, CoinShift) |
| Test network | drynet4 (live): node drynet4.drivechain.dev:8533, explorer, info hub |
| Dev contact | dev@layertwolabs.com, t.me/DcInsiders |
- Full Node Setup
- Wallets, Keys & Addresses
- Replay & Coin Splitting (read first)
- Explorers & APIs
- Sidechains & L2s (includes proposing new L2s)
- Contacts & Resources
- FAQ
- Mining / Mining Pool
- Drynet Dry-Run Networks (official per-network docs: drynet1-4, connect and mine walkthroughs, what changed between runs)
- Run a node against drynet4 now; swap to the launch branch when announced. Dedicated datadir, pinned peers, verify the fork-block hash.
- Reuse your Bitcoin pipeline (RPC, ZMQ, descriptors, electrs/mempool.space) pointed at the eCash node. Key balances by
(chain, address). - Fork week: freeze withdrawals at the fork block, split coins (eCash side first,
nLockTime = 499999999), resume with deep confirmation requirements while difficulty re-equilibrates. - Set the magic nLockTime on every ECX withdrawal, permanently.
- Decide your crediting policy for customer BTC held at the fork block; prepare comms about ECX and the Satoshi-coin reassignment.
- drivechain.info/dev.txt, the canonical fast-info file, updated frequently
- ecash.com, official site and FAQ
- drynet4.drivechain.dev/info, live test network hub
- github.com/ecash-com/bitcoin, github.com/LayerTwo-Labs
- BIP300, BIP301
Feedback Appreciated!