Genesis Block Requirements
Goals
- Support the RHOC/Rev Swap
- Obtain signatures from the validators on the genesis block
- Support a repeatable launch process
- Execute multiple network launches (dry runs)
- Launch the testnet
- Launch the mainnet
Background
There is a desire to launch the test net and main net in a public forum. This implies that the launch of the networks be tried and tested multiple times before the prime time launch of these networks. Furthermore, the genesis block will have hard coded transactions in it, where RHOC holders are offered a 1:1 'swap' of Rev token on the public blockchain. These transactions must be submitted for auditing well in advance of the deployment of the mainnet.
Requirements
Title | User story | Importance | Notes |
---|---|---|---|
ETH Addresses | As a RHOC token holder I must be able to access my Rev tokens by using my existing ETH private keys | Must Have |
|
Transparency | As a RHOC holder, I must be able to audit the genesis block in advance of deployment, so that I know I will get my Rev at genesis. | Must Have |
|
Repeatable & Reliable | As an RChain investor, I would like to see the genesis block deployed during the test net launch ceremony, so that I can have confidence in the launch process | Must Have |
|
RHOC balances | There must be a way to collect up the addresses and associated RHOC balances from the Ethereum blockchain. | Must Have |
|
Validator Signatures | The validators in the network need to provide cryptographic acceptance of the genesis block. Each validator must be presented the genesis block, and given the opportunity to add their signature to the block. | Must Have |
|