After 15 years of being a Bitcoin-only maximalist and about a decade of promoting BIP300 as a soft fork, LayerTwo Labs CEO Paul Sztorc decided to launch Ecash: a hard fork of Bitcoin in which every BTC holder gets free coins. There's a catch, though: while everyone can claim 1 ecash for every bitcoin that they own, Satoshi can only claim half. Meaning that a returning Satoshi will only be able to claim half his coins, while the other half (550k) is currently being sold to investors in order to fund the development and bootstrapping of Ecash. What's more controversial: the hard fork or the SHAD (Satoshi Half Air Drop)? Only time will tell. But the Ecash hard fork is scheduled to happen in August 2026... unless Bitcoin activates BIP300 in the meantime. Game theory at its finest! Time stamps: 00:00:58 – Paul Sztorc announces the new Bitcoin hard fork project, eCash, sharing his motivation for launching it and setting the stage for the discussion. 00:03:02 – eCash’s technical details are explained, including its smaller 400kB block size and the integration of drivechains (BIP 300) to enhance scalability and flexibility. 00:04:55 – The initial drivechains launching with eCash are described, such as Thunder for scalability, ZSide for privacy, and additional chains like CoinShift, BitNames, and Photon. 00:09:28 – Security aspects of sidechains are discussed, covering the 256 sidechain limit, potential outcomes if sidechains fail, and the risks users face when moving coins. 00:14:26 – The project’s name, Ecash, is revealed, with a comparison to Bitcoin Cash and an explanation of the naming decision. 00:15:40 – Paul delves into the philosophy behind the hard fork, his views on Bitcoin maximalism, and his intention to remain committed to both Bitcoin and eCash. 00:20:35 – Mining dynamics are explored, including SHA256 mining competition, miner incentives, and the potential for MEV (miner extractable value) issues. 00:22:36 – Paul critiques the current state of Bitcoin, highlighting user and developer frustration, stagnation, low transaction fees, and gridlock in development. 00:29:40 – The potential for eCash to attract frustrated Bitcoin builders is considered, with references to similar migrations in crypto history. 00:31:38 – Ethereum’s rise is analyzed as a consequence of Bitcoin’s block size wars, with discussion on missed opportunities and lessons learned. 00:41:06 – The likelihood and impact of further Bitcoin hard forks are speculated upon, focusing on community fragmentation and effects on value. 00:41:49 – Hard forks are framed as healthy competition that benefits investors by providing free coins and stimulating innovation. 00:48:20 – The decision to reassign half of Satoshi’s coins for development and community incentives is explained, addressing concerns about distribution. 00:54:07 – Quantum computing threats, Satoshi’s mining behavior, and the rationale for the coin distribution are discussed in the context of long-term security. 01:36:00 – Users are advised to self-custody their Bitcoin to claim eCash, with an outline of the claiming process and best practices. 01:39:01 – Technical steps for claiming eCash using private keys are detailed, including wallet compatibility and the process for users. 01:43:26 – The potential for NFT and ordinal activity on eCash is addressed, along with how LayerTwo Labs will manage onboarding and network congestion. 01:45:35 – Drivechain security parameters are confirmed, with eCash using a 13,000-block security window in line with BIP 300’s Bitcoin implementation. 01:52:06 – The transition from a centralized project launch to decentralized development and governance. 01:54:36 – The current developer team size (about nine members) is shared, along with incentives for external developers to contribute to eCash. 01:58:26 – eCash is compared to Bitcoin Cash, with discussion on network effects, competition, and the potential for eCash to drive improvements in Bitcoin. 02:07:22 – The session concludes with future plans, a call for community engagement, and the possibility of follow-up discussions as the project evolves.
