Set Spiral Mordor activation block

[diega]

No description provided.

[meowsbits]

This places the Mordor testnet activation around November 7, 2023.

[gitr0n1n]

Small detail, shouldn't our PoW testnet simply be called "Mordor Testnet", opposed to "Mordor Classic Testnet"?

[gitr0n1n]

Line 41: Change "Mordor Classic testnet" to "Mordor testnet". Thanks!

[gitr0n1n]

immaterial typo fix on testnet name.

[gitr0n1n]

I'll let one of you do the honor of the merge: @diega @meowsbits @ziogaschr .

To the pseudonyms working on this spec. Thanks for maintaining non-contentious compatibility with the greater EVM ecosystem. In doing so, you're helping to keep Ethereum Classic a state of the art EVM.

==============================================

Interoperability at the EVM level of the stack is important because this allows the application layer developers (DApps) to easily deploy their smart contracts on Ethereum Classic's mainnet and many other EVMs with minimal changes to their code. To the outside observer, think of this as updating the OS that application run on to best practices, security fixes, and removing outdated elements. The OS of Ethereum Classic has been frequently updated throughout its history. This spec is an example of those efforts.

Upgrades: https://ecips.ethereumclassic.org/ECIPs/ecip-1066

With deployment of applications on Ethereum Classic, the application layer contracts are then supported by the enormous and decentralized proof of work network hashrate protecting Ethereum Classic. This provides the developers of those applications with: permissionless accessibility, censorship resistance, and immutability. Put simply, it allows developers to build unstoppable applications. A principle the Ethereum Classic network has lived up to since initial deployment in 2015.

As the most established and secure PoW blockchain with smart contract functionality, this is a huge value to the blockchain space as a whole. Code is law.