
Il va S'EMPARER des bitcoins de Satoshi Nakamoto ?!
Audio Summary
AI Summary
On April 24th, a developer largely unknown in the crypto space, Paul Storts, announced his intention to "fork Bitcoin." This means creating a copy of Bitcoin with a new name, a new project, and a free distribution to all current BTC holders. While Bitcoin has been forked dozens of times before, with most projects fading into obscurity, this instance is different. Storts plans to fund his project by tapping into the most revered wallet in crypto: Satoshi Nakamoto's. Over half a million Bitcoins, dormant for 15 years, are slated for redistribution on the new chain.
To understand Storts' plan, one must first grasp the concept of a fork. Bitcoin is open-source software, meaning its code is public and can be copied and modified by anyone to launch their own cryptocurrency. Litecoin, for example, originated as a fork of Bitcoin. However, possessing the code is not enough; a functional cryptocurrency requires nodes to run the software and miners to dedicate computational power to secure the network and validate transactions. Without these, the ledger isn't maintained, and the history can be rewritten.
A fork occurs when a portion of the network decides to follow different rules, causing the blockchain to split. From the point of separation, two versions of the blockchain coexist. There are two types: soft forks, which are backward-compatible with older software, and hard forks, which create an outright rupture where the two chains become incompatible, forcing users to choose sides. Storts is preparing a hard fork, which is where the complications arise. The new chain inherits the transaction history and balances but must rebuild user trust, developer attention, exchange support, and, crucially, mining power to secure its network. Without these, it becomes vulnerable to attacks, its price collapses, and the project likely dies. Bitcoin Cash in 2017 is a rare example of a surviving fork, though not an exact replica of the original.
Paul Storts is a familiar figure in Bitcoin development circles, having spent over a decade leading Layer Two Labs, a company focused on building secondary layers for Bitcoin. He also developed Truffle Coin, a decentralized prediction market. His long-standing obsession, since 2015, has been "Drivechains," a concept aimed at adding scalability and functionality to Bitcoin without altering its base layer. He formalized these ideas in Bitcoin Improvement Proposals (BIPs) 300 and 301, but the core Bitcoin developers, who maintain the official Bitcoin Core software, have consistently rejected them. Storts accuses them of "dev capture," arguing they are hindering Bitcoin's evolution. Frustrated after a decade, he decided to create his own Bitcoin.
The new project, named iCash, is set to hard fork at block number 964000, expected around August 21, 2026. Upon this split, all Bitcoin holders will automatically receive an equivalent amount of iCash, provided they hold their Bitcoin in self-custody. The name "iCash" has drawn some criticism due to prior uses in the crypto space, but Storts has acquired the domain and embraces the name. Technically, iCash will be a near-identical copy of Bitcoin Core, sharing the same mining algorithm, block structure, and transaction history up to the fork point.
iCash aims to launch with intentionally low mining difficulty to attract miners. Its key differentiator will be the immediate integration of Drivechains, which are secondary chains secured by merge mining. This means iCash miners will secure the main iCash chain and its associated Drivechains simultaneously, without additional energy expenditure, theoretically enabling more features without compromising security. The project's ambitious goal is to accommodate 8 billion users.
Storts believes Bitcoin's base layer is stagnant and that the Lightning Network, intended to solve scalability issues, has not met expectations due to its complexity and low adoption. He argues that users seek functionality and will move to other blockchains if Bitcoin fails to provide it. A hard fork, rather than a soft fork, was chosen because it bypasses the need for Bitcoin Core developer consensus. The airdrop strategy aims to instantly grant iCash a large user base and legitimacy.
The fork is scheduled for late August, with code finalization 30 days prior, preceded by bug bounty programs. The most controversial aspect of iCash is its funding strategy: reassigning Satoshi Nakamoto's dormant Bitcoins on the new chain. Approximately 500,000 to 600,000 BTC from Nakamoto's estimated holdings will be moved from their original addresses on the iCash chain to fund investors and developers. This action has led to accusations of theft, despite no Bitcoin being taken from the original Bitcoin blockchain. Critics argue this sets a dangerous precedent, potentially allowing future forks to seize any inactive wallet's funds.
Further technical concerns include the security of Drivechains, with some developers warning that a majority of hashing power could potentially divert funds from secondary chains (a 51% attack). Additionally, iCash will launch without replay protection, a mechanism preventing transactions on one chain from being duplicated on the other. Storts deliberately omitted this to pressure exchanges into listing iCash, as accidental replay attacks could create legal issues for them, forcing their involvement. While users can avoid replay attacks by not moving their iCash, this decision has been likened to blackmailing the industry.
The presence of institutional holders like Bitcoin ETFs and companies such as MicroStrategy adds another layer of complexity. These entities will face decisions on how to handle their iCash airdrop, potentially leading to significant selling pressure or complex compliance justifications. The landscape for Bitcoin forks has fundamentally changed with the rise of institutional ownership. Whether iCash succeeds or joins the graveyard of forgotten forks remains uncertain. Storts has a technically coherent project and advanced sidechains, but faces historical precedent, community opposition, and moral objections. The