{"id":8685,"date":"2025-02-18T05:47:31","date_gmt":"2025-02-18T04:47:31","guid":{"rendered":"https:\/\/wsj-crypto.com\/?p=8685"},"modified":"2025-02-18T05:47:31","modified_gmt":"2025-02-18T04:47:31","slug":"navigating-the-journey-from-morden-to-ropsten-in-the-ethereum-ecosystem","status":"publish","type":"post","link":"https:\/\/wsj-crypto.com\/index.php\/2025\/02\/18\/navigating-the-journey-from-morden-to-ropsten-in-the-ethereum-ecosystem\/","title":{"rendered":"Navigating the Journey: From Morden to Ropsten in the Ethereum Ecosystem"},"content":{"rendered":"

<\/p>\n

\n

Testing a fork<\/h2>\n

<\/p>\n

The Spurious Dragon hardfork is slated for the upcoming week; block 2675000 is anticipated to arrive on Tuesday evening (CET). The block number for the test network “Morden” was set at block 1885000. Executing the fork in the test network before implementing it in the main network was a crucial precaution taken in the testing procedure to guarantee a seamless transition into the post-fork condition.<\/p>\n

<\/p>\n

The Morden fork took place on Nov-20-2016, 06:12:20 +UTC, at block 1885000 as intended. Shortly after, at block 1885074, a consensus conflict arose between Geth and Parity.<\/p>\n

<\/p>\n

Morden replay security<\/h2>\n

<\/p>\n

The Morden testnet has been operational since the inception of the Ethereum blockchain (July 2015). During that period, worries about replay-attacks between Morden and Mainnet were tackled by utilizing a nonce-offset. All accounts on Morden commenced with a starting nonce of 2^20<\/span> rather than 0<\/span>, ensuring that any transaction acknowledged on one chain would not be valid on the contrary chain.<\/p>\n

<\/p>\n

EIP 161<\/a> delineates new EVM protocols regarding nonces. The adoption of those protocols, paired with Morden-specific nonce-regulations, led to Geth and Parity generating incompatible blocks at block 1885074.<\/p>\n

<\/p>\n

Implications for the Main network<\/h2>\n

<\/p>\n

All problems identified during the rollout of Spurious Dragon on the test network were Morden-specific<\/em>. Presently, there are no known issues impacting the Mainnet.<\/p>\n

<\/p>\n

Initiating the new \u201cRopsten\u201d test network<\/h2>\n

<\/p>\n

Prior to the current hard forks, there had already been dialogues regarding the reboot of the test network from a new genesis block to simplify full synchronization and reduce resource consumption. Furthermore, due to the low difficulty of the testnet, the difficulty bomb<\/em> was already prompting noticeable delays in block intervals, which would exacerbate if left unaddressed. Thus, the moment is opportune to move on from Morden and commence a new test network.<\/p>\n

<\/p>\n

New clients will be issued that utilize Ropsten instead of Morden as the standard testnet.<\/p>\n

<\/p>\n

Developers eager to start with Ropsten immediately can download the genesis file here<\/a>, and initiate a client with the Ropsten network id:3<\/span><\/p>\n

<\/p>\n