gnosischain · skundu42 · Apr 6, 2026 · Mar 20, 2026 · Apr 6, 2026 · Apr 6, 2026
@@ -1,3 +1,3 @@
 save-exact=true
-minimum-release-age=3d
-trust-policy=no-downgrade
+minimum-release-age=4320
+trust-policy=no-downgrade
@@ -26,10 +26,10 @@ keywords:
 | Execution Layer RPC      | https://rpc.gnosischain.com                 |
 | More RPC endpoints       | [RPC Providers](../../tools/RPC%20Providers/README.md) |
 | Execution Layer Explorer | https://gnosisscan.io                       |
-| Execution Layer Explorer | https://blockscout.com/xdai/mainnet         |
+| Execution Layer Explorer | https://gnosis.blockscout.com/              |
 | Fork monitor             | https://forkmon.gnosischain.com             |
 | EthStats                 | https://ethstats.gnosischain.com            |
-| Forked Blocks            | https://blockscout.com/xdai/mainnet/reorgs  |
+| Forked Blocks            | https://gnosis.blockscout.com/reorgs        |
 | Faucet                   | https://gnosisfaucet.com                    |
 
 ### Consensus Layer
@@ -40,7 +40,6 @@ keywords:
 | Beacon Explorer          | https://beaconchain.gnosischain.com/                      |
 | Beacon Explorer Backup 1 | https://beacon-v1.gnosischain.com           |
 | Beacon Explorer Backup 2 | https://beacon-v2.gnosischain.com           |
-| Beacon Checkpoint Sync   | https://checkpoint.gnosis.gateway.fm        |
 | Beacon Checkpoint Sync   | https://checkpoint.gnosischain.com          |
 | Beacon Checkpoint Sync   | https://checkpoint-sync-gnosis.dappnode.io/ |
 
@@ -85,6 +84,6 @@ Gnosis maintains a [Configs Repo](https://github.com/gnosischain/configs/) that
 ## Key Contracts
 
 - [xDai Bridge](../../bridges/About%20Token%20Bridges/xdai-bridge#key-contracts)
-- [AMB Bridge](../../bridges/About%20Token%20Bridges/amb-bridge#key-contracts)
+- [AMB Bridge](../../bridges/About%20Token%20Bridges/amb-bridge)
 - [OmniBridge](../../bridges/About%20Token%20Bridges/omnibridge#key-contracts)
-- [Beacon Chain](/about/specs/gbc/README.md)
+- [Beacon Chain](/about/specs/gbc/README.md)
@@ -23,7 +23,7 @@ The table below lists differences if any.
 | [EIP-7840](https://eips.ethereum.org/EIPS/eip-7840): Add blob schedule to EL config files      | EL      | Not modified
 | [EIP-4844-pectra](https://eips.ethereum.org/EIPS/eip-4844): Collect Blob Gas Fee               | EL      | Added
 
-* See [Differences with Ethereum mainnet](#differences-with-ethereum-mainnet)
+* Differences with Ethereum mainnet are shown in the table above.
 
 
 

@@ -27,7 +27,7 @@ Check out [validator withdrawal](/node/management/withdrawals) for more details.
 
    For any type of withdrawals, a validator need to have `0x01` withdrawal credential. You’re fine if you used `--eth1_withdrawal_address` to create your validator keys. If not, tooling will be made available.
 
-   Refer to [validator withdrawal](/node/management/withdrawals#check-withdrawal-credential) for more details.
+   Refer to [validator withdrawal](/node/management/withdrawals) for more details.
 
 2. Update your clients
 

@@ -121,7 +121,7 @@ Historically, deposits on the Beacon Chain were made with a token called `mGNO`
 
 :::
 
-For those who prefer not to manage the infrastructure themselves, liquid staking providers offer the opportunity to stake without the need for personal infrastructure management. For more in-depth information about sGNO and rGNO tokens, please consult the [Stakewise](/tools/beacon-chain/liquid-staking#tokens-sgno--rgno) page.
+For those who prefer not to manage the infrastructure themselves, liquid staking providers offer the opportunity to stake without the need for personal infrastructure management. For more in-depth information about sGNO and rGNO tokens, please consult the [Stakewise](/node/participate-validator/liquid-staking) page.
 
 ### GnosisDAO Governance
 
@@ -132,4 +132,3 @@ For those who prefer not to manage the infrastructure themselves, liquid staking
 ## GNO Token Audit
 
 - [GNO Token v2.0.0 Audit](https://hackmd.io/@verilog/gno-token-v2-audit) by Verilog Solutions
-
@@ -160,7 +160,7 @@ Example: https://gnosis.blockscout.com/tx/0x5892a695860f6087a2d93140f05e6365142f
 2. `UserRequestForSignature(address recipient, uint256 value, bytes32 nonce, address token)` event is emitted from [Home xDAI bridge contract](https://gnosis.blockscout.com/address/0x7301CFA0e1756B71869E93d4e4Dca5c7d0eb0AA6). [Example](https://gnosisscan.io/tx/0xca6fa9395f734501a9497f409db12699782b0a068dc4463d736561572eda8441#eventlog)
 3. Bridge validators observe the event and call `submitSignature(bytes signature, bytes message)` function on [Home xDAI bridge contract](https://gnosis.blockscout.com/address/0x7301CFA0e1756B71869E93d4e4Dca5c7d0eb0AA6) on Gnosis Chain.
 4. After enough signatures are collected, `CollectedSignatures` event is emitted/
-5. Anyone can execute the withdrawal on Ethereum by calling `executeSignatures(bytes message, bytes signatures)` on [Foreign xDAI bridge](https://etherscan.io/address/0x4aa42145Aa6Ebf72e164C9bBC74fbD3788045016) on Ethereum. To fetch the calldata value, please check the [guideline below](#how-to-claim-dai-on-ethereum). **USDS** is unlocked to the receiver or swap to **DAI** to the receive.
+5. Anyone can execute the withdrawal on Ethereum by calling `executeSignatures(bytes message, bytes signatures)` on [Foreign xDAI bridge](https://etherscan.io/address/0x4aa42145Aa6Ebf72e164C9bBC74fbD3788045016) on Ethereum. To fetch the calldata value, please check the [guideline below](#how-to-claim-usds-on-ethereum). **USDS** is unlocked to the receiver or swap to **DAI** to the receive.
 6. `RelayedMessage(address recipient, uint256 value, bytes32 transactionHash)` emitted on Foreign xDAI Bridge. Please be aware that after Hashi upgrade, `transactionHash` has been replaced with the value of `nonce`. Please check [here](../hashi/hashi-integration.md) for more information on how it works.
 
 ### Savings xDAI

@@ -14,7 +14,7 @@ title: Offline and Sync Issue
 
 1. **Anyone seeing errors with checkpoint sync today?**
 
-    If the usual checkpoint sync https://checkpoint.gnosischain.com/ doesn't work, you can try using https://checkpoint.gnosis.gateway.fm/ if they are both down, don't hesitate to report it as the team might not be aware yet
+    If the usual checkpoint sync https://checkpoint.gnosischain.com doesn't work, report it so the team can investigate.
 
 2. **My (dapp)node have been offline for a couple of hours. After restart attestation and block proposing resumed, but duties in sync committee still shows missing even after a few hours since it's up again. Does anyone has an explanation for this?**
 
@@ -30,7 +30,7 @@ title: Offline and Sync Issue
 
 5. **Using checkpoint sync, but all my nodes are down. Why?**
 
-    If the usual checkpoint sync https://checkpoint.gnosischain.com/ doesn't work, you can try using https://checkpoint.gnosis.gateway.fm/ if they are both down, don't hesitate to report it as the team might not be aware yet
+    If the usual checkpoint sync https://checkpoint.gnosischain.com doesn't work, report it so the team can investigate.
 
 6. **Just realized my validators are off line since the beginning of the month, can someone take a peek and help?**
 
@@ -42,7 +42,7 @@ title: Offline and Sync Issue
 
 8. **Is there a new checkpoint for Gnosis?**
 
-    The two common checkpoint sync are : https://checkpoint.gnosischain.com/ and https://checkpoint.gnosis.gateway.fm/
+    The common checkpoint sync endpoint is: https://checkpoint.gnosischain.com
 
 9. **My Gnosis node is crashed a month ago, was there a breaking chain upgrade a month ago?**
 

@@ -90,7 +90,7 @@ title: Running Nodes
 
 20. **Is it worth to be a validator?**
 
-    Regardless of your number of validators by becoming one you're helping to secure and decentralize the network and you can earn a decent APY (who was ~14% as of October 2023 but who depends of the number of validators)
+    Regardless of your number of validators, by becoming one you're helping to secure and decentralize the network. Validator APY changes over time based on validator count and network conditions, so use the live dashboards in the docs for current estimates.
 
 21. **How many deposits per epoch are allowed on GBC? How long would it take to deposit and start validating?**
 

@@ -18,7 +18,7 @@ title: Staking and Liquid Staking
 
 3. **What’s the best place to stake my GNO bag?**
 
-    You can stake your GNO on liquid staking platforms like Stakewise or you could get/buy your own node and stake those GNO to validate the chain (~14% APY as October 2023) more information in the docs
+    You can stake your GNO on liquid staking platforms like StakeWise, or run your own node and stake directly as a validator. APY is variable, so check the live metrics linked in the docs for current values.
 
 4. **Is there any official staking platform for GNO?**
 
@@ -30,7 +30,7 @@ title: Staking and Liquid Staking
 
 6. **Can you currently unstake sGNO or is that not ready yet?**
 
-    To withdraw directly you need to wait for Stakewise v3 that isn't out yet or if you really want to withdraw immediately, you can find some liquidity on Curve for sGNO and rGNO
+    StakeWise V3 is live on Gnosis Chain and StakeWise V2 is deprecated. If you still hold V2 assets (sGNO/rGNO), use the migration flow to move to V3.
 
 7. **How can I convert rGNO?**
 

@@ -56,7 +56,7 @@
 
 9. Which clients are supported by GBC?
 
-   Lighthouse, Prysm, Nimbus, and Teku clients. [Read more here](../node/architecture.md#consensus-layer).
+   Lighthouse, Lodestar, Nimbus, and Teku clients. [Read more here](../node/architecture.md#consensus-layer).
 
 10. How long does it take to sync the node?
 
@@ -117,59 +117,65 @@ It depends on the mode and hardware specifications. Typically 24 hours should be
 3. What are two types of withdrawals?
 
    There are 2 types of withdrawals: Partial Withdrawal and Full Withdrawal.
-   Partial Withdrawal: Any balance in excess of 1 GNO from the account balance gets withdrawn back to withdrawal address.
-   Full Withdrawal: All the balance from validator’s account gets withdrawn back to withdrawal address. This has to be initiated by validator, signing `voluntary_exit` message and broadcasting it to the network. It is irreversible.
+   Partial Withdrawal: Any eligible balance in excess of 1 GNO is processed for withdrawal.
+   Full Withdrawal: The validator exits and its full balance becomes withdrawable to the configured execution withdrawal address. This has to be initiated by the validator by signing a `voluntary_exit` message and broadcasting it to the network. It is irreversible.
 
-4. What are 0x00 and 0x01 withdrawal credentials prefixes?
+4. What are 0x00, 0x01, and 0x02 withdrawal credentials prefixes?
 
-   The beacon chain validators have a field called withdrawal credentials, where the first byte is referred to as the withdrawal prefix. Currently, this value can be either 0x00 or 0x01, depending on how it is set during the deposit process using a deposit tool. Validators with 0x00 withdrawal credentials won’t have immediate withdrawal capabilities. To enable partial and full withdrawals and unlock their funds, these validators must undergo a one-time migration to 0x01. As this is a one time process, it is essential to be careful performing it.
+   The beacon chain validators have a field called withdrawal credentials, where the first byte is referred to as the withdrawal prefix.
+
+   `0x02` is the recommended execution-address prefix on Gnosis Chain. It supports the current withdrawal flow and is what new validators should use.
+
+   `0x01` is a legacy execution-address prefix. It still works, but follows the older auto-sweep behavior and is no longer the recommended option for new validators.
+
+   `0x00` is the old BLS-only prefix and does not support withdrawals until you perform a one-time BLS-to-execution credential change.
 
 5. How do I change my withdrawal credential?
 
-   You can find a full tutorial on how to change your withdrawal credential [here](https://docs.gnosischain.com/node/management/withdrawals#how-to-change-the-withdrawal-credential).
+   You can find the current step-by-step guide here: [Validator Withdrawals](../node/management/withdrawals.md).
 
 6. I have been running multiple validators. Can I set up the same withdrawal credential for all of them?
 
    Yes, you can set up the same withdrawal credential for all of your validators and can also set up different withdrawal credentials for individual validators.
 
 7. Where can I check my withdrawal credential?
 
-   https://docs.gnosischain.com/node/management/withdrawals#check-withdrawal-credential
+   Check the Withdrawal tab for your validator on the [Beacon chain explorer](https://beaconchain.gnosischain.com/), or inspect the `withdrawal_credentials` field in your saved `deposit-data*.json` file. See [Validator Withdrawals](../node/management/withdrawals.md) for the current walkthrough.
 
 8. Do partial withdrawals happen automatically?
 
-As we have modified some specs regarding the withdrawals to enable withdrawing GNO instead of the native gas token xDai, unlike Ethereum, partial withdrawals currently do not happen automatically. So, for now, you will need to call [`claimWithdrawal`](https://gnosisscan.io/address/0x0b98057ea310f4d31f2a452b414647007d1645d9#writeProxyContract#F3) function on the [contract](https://gnosisscan.io/address/0x0b98057ea310f4d31f2a452b414647007d1645d9#writeProxyContract). However, it is in our plans to automate and subsidize partial withdrawals in the future.
+   The withdrawal processing itself is automatic once your validator is eligible. What is not automatic today is claiming the resulting GNO to the recipient address. After the withdrawal has been processed, you must claim it either on the [Deposit website](https://deposit.gnosischain.com/) or by calling [`claimWithdrawal`](https://gnosisscan.io/address/0x0B98057eA310F4d31F2a452B414647007d1645d9#writeProxyContract) or `claimWithdrawals(...)` on the deposit contract.
 
 9. Do full withdrawals happen automatically?
 
-   No. If your validator is currently active and participating in the beacon chain, then the full withdrawal will not happen automatically. You will have to manually initiate an exit to cause this.
+   No. If your validator is currently active and participating in the beacon chain, the full withdrawal will not happen unless you first manually initiate a voluntary exit.
 
-   Additionally, if you initiate an exit but still have a 0x00 withdrawal credential, your funds will not be withdrawn until a `BLSToExecutionChange` message is included on chain.
+   Additionally, if you initiate an exit while still using `0x00` withdrawal credentials, your funds will remain locked until a `BLSToExecutionChange` is included on chain.
 
 10. Is there a UI that I can use for withdrawals?
 
-    No, as you will have to interact with the beacon chain, it is not feasible to provide a UI that encompasses all the clients.
+    Yes. You can claim withdrawals on the [Deposit website](https://deposit.gnosischain.com/). Advanced users can also claim directly through the deposit contract on Gnosis Chain.
 
 11. Where does the automatic balance withdraw to?
 
-    In case you are using a legacy withdrawal credential 0x00, it will not be withdrawn and you will have to perform a migration to 0x01 credentials to complete the withdrawal. If you have already configured your withdrawal address and have a withdrawal credential of 0x01, then rewards in excess of 1 GNO will be transferred to your withdrawal address.
+    Withdrawals are associated with the validator's configured execution withdrawal address, also referred to as the recipient address in the current docs. If you are still on `0x00`, withdrawals cannot complete until you convert to an execution-address credential.
 
-12. Once I have changed my credential to 0x01, can I change it to an alternative withdrawal address?
+12. Once I have changed my credential to an execution address, can I change it to an alternative withdrawal address?
 
-    No, the migration from 0x00 to 0x01 is a one time process and once you set the address, it cannot be changed. Please make this migration with the utmost care. Note, the withdrawal credential can either be an externally-owned account (EOA) or a smart contract such as a SAFE.
+    No. The BLS-to-execution change is a one-time operation. Once you set the execution withdrawal address, it cannot be changed later. Please perform this step carefully. The withdrawal address can be either an externally owned account (EOA) or a smart contract wallet such as a Safe.
 
 13. I have lost the private key to my withdrawal address, what can I do?
 
     Unfortunately, there is nothing that can be done if the withdrawal address is lost. Please ensure this address is properly backed up and securely stored.
 
-14. What happens to my GNO if I make a full withdrawal but I forget to set the withdrawal credential to 0x01?
+14. What happens to my GNO if I make a full withdrawal but I forget to set the withdrawal credential to an execution address?
 
-    Nothing. Your validator will exit, and will no longer be assigned duties, neither able to earn nor lose any more additional GNO. You may still migrate your withdrawal credentials from 0x00 to 0x01. Once this is done, the validator’s balance will be withdrawn to the address you specify.
+    Your validator will exit and stop performing duties, but the funds will not be withdrawable until you complete the BLS-to-execution credential change. Once you do that, the validator balance can be withdrawn and claimed to the configured recipient address.
 
 15. Can I cancel a withdrawal request that is in the queue?
 
-    No you cannot, this is a one time, irreversible process. Once you submit your withdrawal request (BLSToExecutionChange and/or exit) you can’t go back. Please only exit or change credentials when you are fully aware of what the specific operation will do and with utmost caution.
+    No. These are one-way operations. Once you submit a `BLSToExecutionChange` and/or a voluntary exit, you cannot reverse it. Make sure you understand the effect of each action before proceeding.
 
 16. Where can I find the client updates for Shapella?
 
-    You can find all client updates in this [blog post](https://www.gnosis.io/blog/shapella-client-updates) or [validator withdrawal section](https://docs.gnosischain.com/node/management/withdrawals). Make sure you update your clients before the upgrade.
+    Refer to the current [Validator Withdrawals](../node/management/withdrawals.md) guide and each client's official release notes. The original Shapella client-update post is useful historical context, but the withdrawals guide should be treated as the current operator-facing source of truth.