[WIP] Atlantis Testnet & Mainnet Strategy

[GregTheGreek]

NOTE: this is preparation for our geth client. References to Parity are meant to be local changes for testing, not to Parity's actual repository.

In preparation for Atlantis(#18) we will need to ensure we have properly set our config(#39) for both Morden and Mainnet. Tentatively, it looks like we will be triggering the Mainnet launch much earlier (early-mid July) and the testnet this week. I have outlined a proposed go to launch strategy and more than open to suggestions:

• 1. Update Configurations (Parity and Geth)
  • 1. Update mainnet Atlantis block number to 8,500,000
  • 2. Update Morden Atlantis block number to 4,729,274
• 2. Network Simulations
  • 1. Test locally Geth<>Geth
  • 2. Test with a cloud instance of Geth<>Geth
  • 3. Test locally with a Geth<>Parity
  • 4. Test with a cloud instance of Geth (cloud) <> Parity (local)
• 3. Testnet
  • 1. Spin up ~3 Geth nodes in the cloud (Digital Ocean) for a persistent network
  • 2. Ensure that the Atlantis has triggered
  • 3. IFF all is well, tear down network, connect to the existing Morden network
  • 4. IFF all is well, get boot node and distribute to other miners (Morden Network)
  • 5. IFF all is well for X days, proceed with mainnet
• 4. Mainnet
  • IFF all goes smooth in the testnet, proceed with mainnet.
  • 1. Get participating mainnet nodes in a group(?)
  • 2. Give them constant updates on testnet progress
  • 3. Have them update X days prior to launch(?)
  • 4. IFF no bugs arise during the testnet proceed to mainnet

Edit: re-ordered a few items and added the note.

[soc1c]

Also, private testnet testing is not sufficient. We need a public test phase as specified in ECIP-1054.

[GregTheGreek]

Clarification, this is the required steps PRIOR to taking this client live. Step 3.4 outlines participating in a public testnet

[austinabell]

Would we set up the config and change parity's classic config to be compatible with ours or is that done already?

[GregTheGreek]

Would we set up the config and change parity's classic config to be compatible with ours or is that done already?

We would need to check, but this is for our own internal testing... fork it (or clone) and make the adequate updates to perform private tests.

We are not in charge of updating Parity's config. Thats up to Parity to conform, and/or the miners.

[soc1c]

multi-geth is working on it too now https://github.com/eth-classic/kensington