^Once genesis hashes had been verified between operators as all matching, the operators restarted their nodes with the new genesis, initialising FUND-MainNet-2. At 14:00:00 UTC — the new genesis time specified in the governance proposal — the nodes began communicating with each other to propose and sign the first block. After a relatively short (and nerve-wracking) time > ⅔ Validator power reached consensus, block 1 was produced, and the new chain was born!
The update required massive cooperation, participation, and appropriately, unity among all members to enable a successful update and was able to proceed in a historic 3 hours as planned with the minimally possible downtime, continuing Unification’s stance among the most efficient Blockchains for enterprise and DeFi, which give reason to the continuation of government, consortium and corporate partners who have grown with the Foundation since the initial MainNet launch in 2020.
^ BEACON/Wrkchain state pruning
State bloat has been a long running concern for validator operators. The upgrade includes a major improvement for the BEACON and WRKChain modules to address this, with hash & timestamp state pruning. The vast majority of BEACONs and WRKChains don’t need to keep millions of hashes in-state, so it makes sense to modify the storage of old data sets to optimise network efficiency and state storage. Much like EVM smart contracts, all data submitted to mainchain is effectively archived via Transaction Events, which, with the latest in-place upgrades offered by Cosmos SDK, means event data is no longer “lost” during a chain upgrade. This means that while old data may no longer be held in the state DB, it will effectively still be accessible via transaction query filters to search for BEACON/WRKChain specific events.
Starting from the upgrade height, BEACONs and WRKChains will be allocated 50,000 in-state storage spaces — this is the equivalent to approximately 1 month’s worth of hash submissions, (assuming 1 submission per minute). During the upgrade, the 50,000 most recent submissions for each BEACON/WRKChain will be retained in the state DB, and the rest will be pruned from state. New hash/timestamp submissions will be added to the top of the stack, and old data will be pruned via FILO.
MainNet
Approx. 1 month after TestNet upgrade is executed (allowing for tests etc.) — governance proposal for MainNet 1-ibc upgrade
Voting period runs for 2 weeks
Approx. 1 week after voting period ends — MainNet upgrade executes.
Validator operators were in constant communication via Telegram and Discord, cross-referencing their SHA256 hash results of the migrated genesis, to ensure that all operators had exported and migrated correctly.
The update required massive cooperation, participation, and appropriately, unity among all members to enable a successful update and was able to proceed in a historic 3 hours as planned with the minimally possible downtime, continuing Unification’s stance among the most efficient Blockchains for enterprise and DeFi, which give reason to the continuation of government, consortium and corporate partners who have grown with the Foundation since the initial MainNet launch in 2020.
^ BEACON/Wrkchain state pruning
State bloat has been a long running concern for validator operators. The upgrade includes a major improvement for the BEACON and WRKChain modules to address this, with hash & timestamp state pruning. The vast majority of BEACONs and WRKChains don’t need to keep millions of hashes in-state, so it makes sense to modify the storage of old data sets to optimise network efficiency and state storage. Much like EVM smart contracts, all data submitted to mainchain is effectively archived via Transaction Events, which, with the latest in-place upgrades offered by Cosmos SDK, means event data is no longer “lost” during a chain upgrade. This means that while old data may no longer be held in the state DB, it will effectively still be accessible via transaction query filters to search for BEACON/WRKChain specific events.
Starting from the upgrade height, BEACONs and WRKChains will be allocated 50,000 in-state storage spaces — this is the equivalent to approximately 1 month’s worth of hash submissions, (assuming 1 submission per minute). During the upgrade, the 50,000 most recent submissions for each BEACON/WRKChain will be retained in the state DB, and the rest will be pruned from state. New hash/timestamp submissions will be added to the top of the stack, and old data will be pruned via FILO.
MainNet
Approx. 1 month after TestNet upgrade is executed (allowing for tests etc.) — governance proposal for MainNet 1-ibc upgrade
Voting period runs for 2 weeks
Approx. 1 week after voting period ends — MainNet upgrade executes.
Validator operators were in constant communication via Telegram and Discord, cross-referencing their SHA256 hash results of the migrated genesis, to ensure that all operators had exported and migrated correctly.