LayerTwo Labs CEO plans BTC hard fork

TLDR

LayerTwo Labs CEO Paul Sztorc is proposing a controversial Bitcoin hard fork called eCash that would create a new chain while leaving existing BTC balances unchanged.

1. Sztorc plans an August 2026 fork at Bitcoin block 964,000 into a new eCash chain, giving BTC holders a 1:1 eCash balance and adding Drivechain-style smart contract sidechains.
2. BTC itself is not touched; holders keep their coins on Bitcoin, while any eCash allocation only becomes relevant if infrastructure, exchanges, and users decide to support and claim it.
3. The main controversy is around reallocating Satoshi-linked forked coins and Bitcoins property-rights ethic, so the key thing to watch is whether miners, exchanges, and major devs back or ignore the fork.

Deep Dive

1. What The eCash Fork Proposes

Reporting from CryptoSlate describes Sztorcs plan for an eCash hard fork in August 2026 at Bitcoin block 964,000 that copies Bitcoins ledger and gives every BTC holder 1 eCash per 1 BTC held at the split. The new chain would retain Bitcoin-like proof-of-work while integrating Drivechain-style sidechains to support smart contracts, privacy tools and other applications that Bitcoins base layer does not currently support.

Coindesk notes that, unlike past forks such as Bitcoin Cash and Bitcoin SV, eCash originally proposed allocating only 600,000 of the roughly 1.1 million Satoshi-linked eCash to those addresses, directing the remaining 500,000 to early investors, which sparked accusations of theft on the new chain. Subsequent coverage from Decrypt and Yahoo Finance says Sztorc has since backed away from that reassignment after overwhelmingly negative feedback, though final tokenomics and code are still evolving.

2. Practical Impact For BTC Holders

By design, a fork like this does not move or encumber your BTC on the Bitcoin network; Sztorc has repeatedly emphasized that BTC remains governed by Bitcoin software and its private keys, which he does not control. If the fork launches and gains support, anyone holding BTC in self-custody at the fork block would see a mirrored eCash balance on the new chain, similar to past BCH and BSV splits.

The real decisions start only if eCash becomes live and listed: you would need to choose whether to claim or ignore the new coins, and any claim process that asks you to import seed phrases or keys into new software carries phishing and malware risk, as several articles warn when discussing potential scams around fork-claiming. Until audited clients, clear replay protection and reputable wallets or exchanges support it, the safest operational stance for most users is to assume BTC requires no action at all.

3. Controversy And What To Watch

Coindesk highlights that many Bitcoiners view any manual reassignment of Satoshi-linked forked coins as breaking Bitcoins social contract, even if it only happens on a new chain and does not touch actual BTC holdings. Critics argue that Satoshis untouched coins function as a symbolic guarantee that rules are the same for everyone, so selling claims on forked versions of those coins feels like exploiting that legacy for funding.

At the same time, other projects are pushing alternative approaches to issues like quantum security that do not require a fork, such as Postquant Labs Quip wallet built on Arch Network, which Coindesk presents as a forkless counterpoint to Sztorcs hardening vision. Key signals to watch are: whether any major mining pools or exchanges announce support for eCash, whether Bitcoin Core developers engage with or reject the forks Drivechain agenda, and whether final eCash clients ship with robust, independently reviewed security and replay protections.

Conclusion

Sztorcs eCash proposal is best understood as an attempt to launch a new Bitcoin-derived chain and force a debate about governance, dormant coins and scaling, rather than as a direct threat to existing BTC. For now, Bitcoins rules and balances remain unchanged; the real impact will depend on whether the broader ecosystem chooses to recognize and build around the fork or largely ignores it, as happened with several earlier Bitcoin splits.