Links in this table points to the text file where REV balances can be checked, for Preparatory and Final Snapshot.
The balance is in raw format (revlettes), add 8 decimal places to get REV amount.
Here are the raw csv files from export process documented in Export of REV vault state RCHIP. mergeBalances.csv contains mapping between REV address and its hash which is acquired from transaction server.
Overview
Two upcoming hard forks are planned for RChain main net network. They will restart the network from fresh state with only REV vault state (balances) transferred from the old network.
The purpose of this RCHIP is to provide specification how the process of the first hard fork will be executed. Hard Fork 1 is more like a rehearsal for Hard Fork 2 which will contain many improvements and fixes. So in Hard Fork 1 are only fixes to support future block-merge release, remove inactive validators from PoS contract and a few configuration changes.
Terminology:
Snapshot - export of REV balances on specific block height (number)
Number of blocks to keep validator after withdrawal (it's zero because epoch length is already included)
Minimum bond
12,000.00000000
Minimum stake needed for bonding (REV amount)
Maximum bond
5,000,000.00000000
Maximum stake allowed for bonding (REV amount)
Bonds file used to start the new network bonds.txt.
Impact on REV holders
In short, Hard Fork will not have impact for owners of private keys for corresponding REV address, including REV on exchanges.
MultiSig REV accounts cannot be migrated and must be transferred to private key owned REV address. To our knowledge, there should be no additional MultiSig accounts other than those used in system contracts.
The impact will be on operations on the network. After Final Snapshot network will be offline for a short period for the final community validation.
The Cooperative Board established the process to transfer some of the locked RHOC tokens. Description of the adjustments is documented in the Coop Governance-Committee repository and REV balances will be published in a separate file.
Timeline
The whole proces is divided in multiple steps to ensure enough time for the community to check the balance of their REV accounts and to minimize the downtime of the main net network.
Two snapshots are planned. The first Preparatory Snapshot will leave more time for community validation because network will continue working without interruption.
In the second Final Snapshot, the network will stop and exported REV balances will serve as the initial state of the REV vault for the new network.
Before Final Snapshot, RChain Cooperative will announce block height on which snapshot will be taken and published on GitHub rchain/rchain repository in the wallets_REV_BLOCK-nnnnnn.txt file for community validation.
This is also an invite to all Coop members to check their balance in specified wallets.txt file by searching for their REV address and comparing with the balance read from any available wallet.
Risks and validation
The Cooperative encourage members to check their balances and any reported irregularities will be investigated, documented and corrected.
The whole process of REV export (snapshot) and validation is documented (Export of REV vault state (REV balances)) and supporting repository (tgrospic/rnode-rev-export-hard-fork-1) enables anyone to repeat the process, not only before Hard Fork but any time in the future. The Cooperative will ensure that state before each Hard Fork is preserved and available in the future.
New network operational
REV balances exported in the Final Snapshot will serve as the basis to start the new network through Genesis ceremony. The first block will contain deploys with initial deposits from wallets.txt file published in rchain/rchain repository.
Important dates
wallets_REV_BLOCK-896988.txt
10:41 UTC
wallets_REV_BLOCK-908300.txt
Links in this table points to the text file where REV balances can be checked, for Preparatory and Final Snapshot. The balance is in raw format (revlettes), add 8 decimal places to get REV amount.
Here are the raw csv files from export process documented in Export of REV vault state RCHIP.
mergeBalances.csvcontains mapping between REV address and its hash which is acquired from transaction server.Overview
Two upcoming hard forks are planned for RChain main net network. They will restart the network from fresh state with only REV vault state (balances) transferred from the old network. The purpose of this RCHIP is to provide specification how the process of the first hard fork will be executed. Hard Fork 1 is more like a rehearsal for Hard Fork 2 which will contain many improvements and fixes. So in Hard Fork 1 are only fixes to support future block-merge release, remove inactive validators from PoS contract and a few configuration changes.
Terminology:
List of changes for Hard Fork 1
(rewards map)
(prevent conflicts)
(1.5M REV => 5M REV)
New Main Net configuration
Proof of Stake parameters
250,0000(it's zero because epoch length is already included)
12,000.000000005,000,000.00000000Bonds file used to start the new network bonds.txt.
Impact on REV holders
In short, Hard Fork will not have impact for owners of private keys for corresponding REV address, including REV on exchanges. MultiSig REV accounts cannot be migrated and must be transferred to private key owned REV address. To our knowledge, there should be no additional MultiSig accounts other than those used in system contracts.
The impact will be on operations on the network. After Final Snapshot network will be offline for a short period for the final community validation.
The Cooperative Board established the process to transfer some of the locked RHOC tokens. Description of the adjustments is documented in the Coop Governance-Committee repository and REV balances will be published in a separate file.
Timeline
The whole proces is divided in multiple steps to ensure enough time for the community to check the balance of their REV accounts and to minimize the downtime of the main net network.
Two snapshots are planned. The first Preparatory Snapshot will leave more time for community validation because network will continue working without interruption. In the second Final Snapshot, the network will stop and exported REV balances will serve as the initial state of the REV vault for the new network.
Before Final Snapshot, RChain Cooperative will announce block height on which snapshot will be taken and published on GitHub rchain/rchain repository in the
wallets_REV_BLOCK-nnnnnn.txtfile for community validation.This is also an invite to all Coop members to check their balance in specified
wallets.txtfile by searching for their REV address and comparing with the balance read from any available wallet.Risks and validation
The Cooperative encourage members to check their balances and any reported irregularities will be investigated, documented and corrected. The whole process of REV export (snapshot) and validation is documented (Export of REV vault state (REV balances)) and supporting repository (tgrospic/rnode-rev-export-hard-fork-1) enables anyone to repeat the process, not only before Hard Fork but any time in the future. The Cooperative will ensure that state before each Hard Fork is preserved and available in the future.
New network operational
REV balances exported in the Final Snapshot will serve as the basis to start the new network through Genesis ceremony. The first block will contain deploys with initial deposits from
wallets.txtfile published in rchain/rchain repository.[pos-rho]: https://github.com/rchain/rchain/blob/44eb1194558d97e7dc4b16154af8414e6ff32525/casper/src/main/resources/PoS.rhox