Ethereum Classic (ETC) Invitation: Atlantis ECIP-1054 Hard Fork Chat on Google Hangouts 4/5/2019 at 12 PM EST

This call has ended. If you want to watch the video it is located here:


After a lot of work, the ETC core developers have prepared the ECIP-1054 hard fork specification, nicknamed “Atlantis”, to integrate the “Byzantium” and “Spurious Dragon” hard forks made in Ethereum (ETH) to assure compatibility across chains.

If you are an ETC node operator, mining pool, miner, developer, general ecosystem participant, or just interested in Ethereum Classic, you are invited to a voice chat to talk about the changes, gain consensus, or discuss possible variations to Atlantis.

 
Atlantis — ECIP-1054

Following are the details:

Call Place and Time:

Agenda:

1. Current situation:

ECIP-1054 named “Atlantis” has undergone developer technical discussion and is ready for wider community discussion with node operators, miners, and the rest of network participants and users.

2. Goals:

The goals for Atlantis are:

  • To make ETC compatible with the Ethereum Foundation hard forks named “Spurious Dragon” and “Byzantium”.
  • Deploy on block 1,039,000 on Kotti — early August 2019.
  • Deploy on block 4,723,000 on Morden — early August 2019.
  • Deploy on block 8,750,000 on ETC mainnet — mid-September 2019.
  • To gain node operator and miner consensus in these goals and deployment dates.
  • To revise these goals and deployment dates ASAP in case there are objections or disagreements.

3. Description:

ECIP-1054 Atlantis includes the following changes and additions:

  • Spurious Dragon state-trie clearing.
  • Spurious Dragon contract-code size limit.
  • Byzantium EVM opcodes, namely REVERT, RETURNDATASIZE, RETURNDATACOPY, and STATICCALL.
  • Byzantium EVM precompiled contracts, namely addition and scalar multiplication on the elliptic curve alt_bn128, optimal ate pairing check on the elliptic curve alt_bn128, and BIGINT modular exponentiation.
  • Replacing the intermediate state root field in transaction receipts with the contract return status.
  • Change difficulty adjustment to target mean block time including uncle.

4. Invite creators to describe their proposal:

Developers invited to describe the changes are:

  • Isaac Ardis @ isaac
  • @ Soc1c
  • Wei Tang @ Sorpaas
  • Other devs who participated

5. Open discussion:

After developer comments, ECIP-1054 Atlantis is open for discussion.

Useful links:

Technical specifications for each EIP can be found at those documents respectively:

  • EIP 100 (Change difficulty adjustment to target mean block time including uncles)
  • EIP 140 (REVERT instruction in the Ethereum Virtual Machine)
  • EIP 161 (State-trie clearing)
  • EIP 170 (Contract-code size limit)
  • EIP 196 (Precompiled contracts for addition and scalar multiplication on the elliptic curve alt_bn128)
  • EIP 197 (Precompiled contracts for optimal ate pairing check on the elliptic curve alt_bn128)
  • EIP 198 (Precompiled contract for BIGINT modular exponentiation)
  • EIP 211 (New opcodes RETURNDATASIZE and RETURNDATACOPY)
  • EIP 214 (New opcode STATICCALL)
  • EIP 658 (Embedding transaction status code in receipts)

Code Is Law

Author: Donald McIntyre

Read about me here.