Gnosis, as a closely-related fork of Ethereum, underwent a “Merge” hardfork similar to that of Ethereum. The hardfork replaced Gnosis’ former “proof-of-authority” consensus with the “proof-of-stake” system as it merged with the Gnosis Beacon Chain.
This hardfork is a critical one for Gnosis in its move towards parity with Ethereum, crucial for Gnosis’ future roadmap as an experimental playground for Ethereum features.
This change is also significant as Gnosis now is similar to Ethereum in being fully permissionless now, with the deprecation of previous “proof-of-authority” features.
You can read more on the Ethereum merge here: https://ethereum.org/en/upgrades/merge/.
How will this affect me?
You do not need to do anything. Your funds remain as-is during the transition. There were NOT be any new token issued before, during or after the Merge. The $GNO token continue to be used for staking, while the $xDai token is used as the native gas token.
Please be vigilant of scammers who may use this occasion to launch scam tokens, or phish for seed phrases.
Gnosis' “Merge” is near 1:1 to the Ethereum Merge in its impact on developers.
For a full understanding of the changes, please read “How The Merge Impacts Ethereum’s Application Layer”.
At a high level, the Merge resulted in the following changes:
BLOCKHASHopcode is mostly deprecated
DIFFICULTYopcode returns output of randomness beacon
- Block structure contains more proof-of-stake fields, zeros out proof-of-work fields
- Block time is reduced to ~5s from ~6s
- Block finalization is tracked via
Deprecation of AuRa RANDAO
The Merge result in the deprecation of the legacy AuRa RANDAO random number generator, as part of the larger deprecation of AuRa consensus.
In its place, developers are advised to move to the Beacon Chain’s Randomness, which implements EIP-4399. Please note that this randomness is still biasable, and take precautions.
EIP-4399 explains the process for developers to switch over to the new Beacon Chain Randomness, which can be accessed via the
Additionally, changes proposed by this EIP allow for smart contracts to determine whether the upgrade to the PoS has already happened. This can be done by analyzing the return value of the DIFFICULTY opcode. A value greater than 2**64 indicates that the transaction is being executed in the PoS block.
You must run a consensus client alongside your existing execution client. Not doing so will cause your node to fork and not follow the right chain. Node operators can also check out the Merge Readiness Checklist on the Staking Launchpad for more information, as many of the details apply to all node operators.
You must run an execution client alongside your existing consensus client. Not doing so will cause your node to fork and not follow the right chain. You must set a fee recipient address to receive your earned transaction fee tips/MEV. Stakers are encouraged to follow the Merge Readiness Checklist from the Staking Launchpad to ensure readiness for The Merge.