Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
58 commits
Select commit Hold shift + click to select a range
8690419
Create 05-21-core-devs-call.md
0xarmagan Jul 23, 2025
d99634a
Create 05-28-core-devs-call.md
0xarmagan Jul 23, 2025
658b08c
Create 06-04-core-devs-call.md
0xarmagan Jul 23, 2025
4690260
Create 06-25-core-devs-call.md
0xarmagan Jul 23, 2025
6d858cd
Create 07-02-core-devs-call.md
0xarmagan Jul 23, 2025
0534e58
Create 07-09-core-devs-call.md
0xarmagan Jul 23, 2025
c9e6a1e
Create 07-23-core-devs-call.md
0xarmagan Jul 23, 2025
c863094
Update and rename 07-23-core-devs-call.md to 07-16-core-devs-call.md
0xarmagan Jul 23, 2025
06680af
Create 07-23-core-devs-call.md
0xarmagan Jul 23, 2025
24f0d20
Add hashi update for deprecation
vanshika-srivastava Aug 22, 2025
9ed392d
shift hashi integration
vanshika-srivastava Aug 22, 2025
ea58789
Main (#799)
vanshika-srivastava Aug 22, 2025
63e06bd
docs(bridges): update docs
zengzengzenghuy Sep 2, 2025
13cc717
update older content
skundu42 Sep 3, 2025
d7d8184
Merge branch 'main' into dev
skundu42 Sep 3, 2025
45abd6e
Fix broken links (#802)
tmgrask Sep 4, 2025
31cfee7
feat: add cookie policy banner and script (#805)
Wagalidoom Sep 16, 2025
8314fcf
feat(bridges): update USDS migration details (#806)
zengzengzenghuy Sep 23, 2025
80d0ddd
added announcement bar
skundu42 Sep 23, 2025
a904fe2
Add dRPC to RPC Providers list (#808)
dRPCMarketing Oct 15, 2025
b3bd7dc
docs: :memo: update Prysm domain to prysm.offchainlabs.com (#804)
victorelec14 Oct 15, 2025
89f4b32
docs: Replace broken link (#811)
rodrigoherera Oct 22, 2025
f013155
Update node > management > monitoring-validators section. (#809)
nicosampler Oct 22, 2025
e628136
remove llms.txt from git
skundu42 Oct 22, 2025
7fa8959
Merge branch 'main' into dev
skundu42 Oct 22, 2025
f5c8498
Revise image and hint in Node README
0xarmagan Oct 22, 2025
581fd4a
Update Covalent details (#814)
zeeshan8281 Nov 1, 2025
c03ae1e
feat(bridges): update usds migration status, add governance decisions…
zengzengzenghuy Nov 10, 2025
a57e3c0
fix(docusaurus.config.js): typo
zengzengzenghuy Nov 10, 2025
7b4d8ff
feat(bridges): update bridges content
zengzengzenghuy Nov 10, 2025
37dd774
feat: update color palette and icons (#817)
Wagalidoom Nov 17, 2025
1fa1cd2
Merge branch 'main' into dev
vanshika-srivastava Nov 17, 2025
be4d9ff
Adding Openfort (#819)
joalavedra Nov 26, 2025
2f5586b
feat(bridges): update bride validator and decision, replace Gateway w…
zengzengzenghuy Nov 26, 2025
ad56e0c
bumped up docusaurus version
skundu42 Nov 26, 2025
c4fad98
minor link updates
skundu42 Nov 26, 2025
9ce2b8d
Merge branch 'main' into dev
skundu42 Nov 26, 2025
6fc4cae
bridges(management): add governance decisions: remove kpk from bridge…
zengzengzenghuy Dec 12, 2025
ceaa07d
Merge branch 'main' into dev
zengzengzenghuy Dec 12, 2025
096036e
Adding Codeowners file, also updating security of workflows
atifather Jan 7, 2026
18e5609
minor fix in erigon command
skundu42 Jan 7, 2026
2708989
Merge branch 'main' into dev
vanshika-srivastava Jan 7, 2026
15eee99
feat: add minimum release, trust policy and lock package version
Wagalidoom Jan 9, 2026
5cdde21
feat: add security audit workflow
Wagalidoom Jan 9, 2026
aa12282
fix: update packages
Wagalidoom Jan 12, 2026
f517846
Merge pull request #828 from gnosischain/feat/security-update
Wagalidoom Jan 12, 2026
4e80420
chore: update nvmrc
Wagalidoom Jan 14, 2026
fed03fd
chore: update vulnerable package
Wagalidoom Jan 14, 2026
519ede8
temp: override ws
Wagalidoom Jan 14, 2026
3a64f26
fix: remove cookbookdev
Wagalidoom Jan 15, 2026
134a35a
remove old link and fix cookbook breaking change
skundu42 Jan 23, 2026
3133d46
chore(about): update bug bounty payout info
zengzengzenghuy Feb 9, 2026
bb6160d
chore(bridge,about): remove bsc-xdai bridge relevant content
zengzengzenghuy Feb 9, 2026
67763f6
re-added search bar
skundu42 Feb 9, 2026
373f136
Merge branch 'main' into dev
skundu42 Feb 9, 2026
a32228f
remove gateway
skundu42 Feb 23, 2026
e6d6a3d
updated beaconchain explorer links and thumbnail
skundu42 Feb 27, 2026
ae0e171
Merge remote-tracking branch 'origin/main' into dev
skundu42 Feb 27, 2026
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/about/networks/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ keywords:
| Chain ID | 100 | 10200 |
| EL RPC | https://rpc.gnosischain.com | https://rpc.chiadochain.net |
| EL Explorer | https://gnosisscan.io | https://blockscout.com/gnosis/chiado |
| CL Explorer | https://gnosischa.in/ | https://beacon.chiadochain.net |
| CL Explorer | https://beaconchain.gnosischain.com/ | https://beacon.chiadochain.net |
| Fork monitor | https://forkmon.gnosischain.com | https://forkmon.chiadochain.net |
| EthStats | https://ethstats.gnosischain.com | https://ethstats.chiadochain.net |
| Faucet | https://faucet.gnosischain.com/ | https://faucet.chiadochain.net/ |
2 changes: 1 addition & 1 deletion docs/about/networks/mainnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@ keywords:
| Consensus Layer | |
| ------------------------ | ------------------------------------------- |
| Consensus Layer RPC | https://rpc-gbc.gnosischain.com |
| Beacon Explorer | https://gnosischa.in/ |
| 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 |
Expand Down
22 changes: 11 additions & 11 deletions docs/faq/Node FAQs/depositWithdrawalReward.md
Original file line number Diff line number Diff line change
Expand Up @@ -35,7 +35,7 @@ title: Deposit, Withdrawals, and Rewards
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.

6. **How long does it take for node status information to appear after a deposit?**
It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on gnosischa.in.
It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on [beaconchain.gnosischain.com](https://beaconchain.gnosischain.com/).

7. **Where can I check my withdrawal credential?**

Expand Down Expand Up @@ -84,7 +84,7 @@ It takes about 4 hours for a deposit to be processed, you can check how your val

17. **How do I voluntarily exit all my validators (using lighthouse) with DappNode?**

First of all be sure to already have a 0x01 withdrawal address or follow the step by step guide. Then go to the web3signer UI, select all keys, select the exit button, type the message ("I want to exit"), then verify on Gnosischa.in how it is going, it can take some time between the moment where you exit and the moment where it's visible on Gnosischa.in
First of all be sure to already have a 0x01 withdrawal address or follow the step by step guide. Then go to the web3signer UI, select all keys, select the exit button, type the message ("I want to exit"), then verify on beaconchain.gnosischain.com how it is going, it can take some time between the moment where you exit and the moment where it's visible on beaconchain.gnosischain.com

18. **When you receive rewards from validation, where does the reward go? Does it stay in the node or go to the address you choose to receive rewards? Because on this address I don't notice any increase of GNO.**

Expand All @@ -110,7 +110,7 @@ It takes about 4 hours for a deposit to be processed, you can check how your val

For consensus layer rewards who are paid in GNO once updated to 0x01 it's not possible to change it. For execution layer rewards who are paid in xDAI you can change them as much as you want in the client or web3signer UI. More information in the [docs](https://docs.gnosischain.com/node/rewards-penalties).

24. **In the explorer gnosischa.in, what is the meaning of total withdrawal?**
24. **In the explorer beaconchain.gnosischain.com, what is the meaning of total withdrawal?**

Total withdrawal means the total accrued GNO

Expand Down Expand Up @@ -174,7 +174,7 @@ It takes about 4 hours for a deposit to be processed, you can check how your val
40. **Are there any news regarding an easy solution to change the recipient address in my DappNode to withdraw my mGNO?**

Currently not, even if Dappnode mentioned working on it in the past. You have to follow the regular [step by step guide](https://docs.gnosischain.com/node/management/withdrawals).
41. **I see automatic withdrawals to my wallet on gnosischa.in, but I don't seem to be receiving them. Is there anything else that I need to do?**
41. **I see automatic withdrawals to my wallet on beaconchain.gnosischain.com, but I don't seem to be receiving them. Is there anything else that I need to do?**

You have to claim withdrawals manually, you can do so on the [Deposit page](https://deposit.gnosischain.com/) or on the Deposit contract. Once claimed it should be instantaneous in the same transaction.

Expand Down Expand Up @@ -224,29 +224,29 @@ It takes about 4 hours for a deposit to be processed, you can check how your val

For full withdrawals you have to wait until your validator leaves the exit queue and be ready to claim. Then both for partial and full withdrawals, once claimed on the contract or on the [Deposit page](https://deposit.gnosischain.com/) it should be instantaneous.

55. **On gnosischa.in while some rewards are denominated in GNO, others are in xDai. What's the difference?**
55. **On beaconchain.gnosischain.com while some rewards are denominated in GNO, others are in xDai. What's the difference?**

You can earn two kinds of rewards : consensus layer rewards who are paid in GNO and execution layer rewards who are paid in xDAI. More information in the [docs](https://docs.gnosischain.com/node/rewards-penalties).

56. **Any timeline from Stakewise for withdrawals?**

It will happen after the Stakewise v3 update which might take longer for Gnosis Chain because of the two tokens rewards system

57. **I see a withdrawal on gnosischa.in, but I haven't initiated anything. Why?**
57. **I see a withdrawal on beaconchain.gnosischain.com, but I haven't initiated anything. Why?**

The withdrawals you see on Gnosischa.in are basically just withdrawals ready to be claimed on the contract, the GNO in question have waiting on the deposit contract, you can claim a withdrawal on the [Deposit page](https://deposit.gnosischain.com/) or manually from the [contract](https://docs.gnosischain.com/node/management/withdrawals#how-to-receive-my-withdrawal-full-or-partial).
The withdrawals you see on beaconchain.gnosischain.com are basically just withdrawals ready to be claimed on the contract, the GNO in question have waiting on the deposit contract, you can claim a withdrawal on the [Deposit page](https://deposit.gnosischain.com/) or manually from the [contract](https://docs.gnosischain.com/node/management/withdrawals#how-to-receive-my-withdrawal-full-or-partial).

58. **I do not want partial withdrawals to be automatic due to tax reasons. Can I opt-out of this feature?**

The bot who was automatically claiming withdrawals has been stopped now, withdrawals are manuals now

59. **I've been running my node for a week now. When/Where can I expect to start seeing my accrued rewards?**

If you have set a withdrawal address, your rewards will accrue in the deposit contract. At the moment you will have to claim them manually from that contract. You can either go and call claimWithdrawals function on the GBC deposit contract or use the Withdrawal Claim tab on https://deposit.gnosischain.com/. You can check your accrued rewards on https://gnosischa.in. as well.
If you have set a withdrawal address, your rewards will accrue in the deposit contract. At the moment you will have to claim them manually from that contract. You can either go and call claimWithdrawals function on the GBC deposit contract or use the Withdrawal Claim tab on https://deposit.gnosischain.com/. You can check your accrued rewards on https://beaconchain.gnosischain.com/ as well.

60. **Can I withdraw without being online?**

It is usually pretty tricky to exit without an actively running node. If getting online is an option, we suggest you to do so. If not, you can try to create an exit message using [ethdo](https://github.com/wealdtech/ethdo/blob/master/docs/exitingvalidators.md) and by [broadcasting](https://gnosischa.in/tools/broadcast) the message using the Broadcast tool on [gnosischa.in](http://gnosischa.in/).
It is usually pretty tricky to exit without an actively running node. If getting online is an option, we suggest you to do so. If not, you can try to create an exit message using [ethdo](https://github.com/wealdtech/ethdo/blob/master/docs/exitingvalidators.md) and by [broadcasting](https://beaconchain.gnosischain.com/tools/broadcast) the message using the Broadcast tool on the [Beacon chain explorer](https://beaconchain.gnosischain.com/).
61. **My wallet got hacked. Is there any way to change my withdrawal address?**

If the withdrawal address you have set is already 0x01, unfortunately, there is no way to change it as it is a one time process.
Expand All @@ -263,9 +263,9 @@ It takes about 4 hours for a deposit to be processed, you can check how your val

You cannot use Ethereum Staking/Deposit CLI tool for BLS-to-Execution on Gnosis Chain as it is not supported. However, you can change your withdrawal credential by using ethdo following the [step by step tutorial](https://docs.gnosischain.com/node/management/withdrawals#how-to-change-the-withdrawal-credential) on our docs.

65. **How long does it take for a withdrawal to be processed? The epoch for my exit (according to https://gnosischa.in/) was 5 hours ago, but if I hit the claimwithdrawal function from the withdrawal address, I don't get any GNO.**
65. **How long does it take for a withdrawal to be processed? The epoch for my exit (according to https://beaconchain.gnosischain.com/) was 5 hours ago, but if I hit the claimwithdrawal function from the withdrawal address, I don't get any GNO.**

You can check the withdrawals tab on https://gnosischa.in to see an estimate of how long you need to actually be able to claim your exited GNO.
You can check the withdrawals tab on https://beaconchain.gnosischain.com/ to see an estimate of how long you need to actually be able to claim your exited GNO.

66. **Anyone know how to withdraw GNO from stakewise validator?**

Expand Down
6 changes: 3 additions & 3 deletions docs/faq/Node FAQs/monitoring.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,11 +22,11 @@ title: Monitoring and Alerts

3. **Anyone has an automated alert for their validators?**

Open an account on gnosischa.in it will send you an email when the node goes down
Open an account on the Beacon chain explorer (https://beaconchain.gnosischain.com/), it will send you an email when the node goes down

4. **Is there a queue monitor similar to validatorqueue.com for beaconchain?**

There is an exit queue on Gnosis Chain as well but no dedicated website. Once the your voluntary exit message broadcasted, you can monitor the progress of your validator withdrawal on Gnosischa.in
There is an exit queue on Gnosis Chain as well but no dedicated website. Once your voluntary exit message is broadcasted, you can monitor the progress of your validator withdrawal on the Beacon chain explorer (https://beaconchain.gnosischain.com/)

5. **Would anyone in this group be interested in a Gnosis Chain validators monitoring bot?**

Expand All @@ -36,7 +36,7 @@ title: Monitoring and Alerts

Go on the [deposit contract](https://gnosisscan.io/address/0x0B98057eA310F4d31F2a452B414647007d1645d9#readProxyContract) and enter your withdrawal address in the field "`7.withdrawableAmount`"

7. **Has anyone set up multiple validators to monitor under your account on gnosischa.in? I'm wondering if there is a way to batch add validators instead of just one-by-one. (edited)**
7. **Has anyone set up multiple validators to monitor under your account on the Beacon chain explorer? I'm wondering if there is a way to batch add validators instead of just one-by-one. (edited)**

You should be able to add them in bulk by searching for the deposit/withdrawal address in the dashboard and then clicking the button that looks like a bookmark (save all to watch list).You can then select all and manage notifications for your selection in the notification center. The dashboard only shows up to 100 in the free fier, but I think you can add up to 300 to the watch list.

Expand Down
6 changes: 3 additions & 3 deletions docs/faq/Node FAQs/runningNode.md
Original file line number Diff line number Diff line change
Expand Up @@ -22,7 +22,7 @@ title: Running Nodes

3. **I have deposited for two hours, why haven’t I seen my node information?**

It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on gnosischa.in
It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on the Beacon chain explorer: https://beaconchain.gnosischain.com/

4. **I'm getting an alert in Lighthouse that I've got an invalid signature and/or that an endpoint has failed, how to troubleshoot?**

Expand Down Expand Up @@ -70,7 +70,7 @@ title: Running Nodes

15. **Could you tell me what code I have to put in the Dappnode terminal to recover all my GNO that I have staked?**

First of all be sure to already have a 0x01 withdrawal address or follow the [step by step guide](https://docs.gnosischain.com/node/management/withdrawals). Then go in the web3signer UI, select all keys, select the exit button, type the message ("I want to exit"), then verify on Gnosischa.in how it is going, it can take some time between the moment where you exit and the moment where it's visible on Gnosischa.in
First of all be sure to already have a 0x01 withdrawal address or follow the [step by step guide](https://docs.gnosischain.com/node/management/withdrawals). Then go in the web3signer UI, select all keys, select the exit button, type the message ("I want to exit"), then verify on the Beacon chain explorer (https://beaconchain.gnosischain.com/) how it is going, it can take some time between the moment where you exit and the moment where it's visible there

16. **How much does it cost per month to run a full node on Azure?**

Expand All @@ -86,7 +86,7 @@ title: Running Nodes

19. **After making the 1 GNO deposit, how long it takes to the validator to be active?**

It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on gnosischa.in
It takes about 4 hours for a deposit to be processed, you can check how your validator is doing on the Beacon chain explorer: https://beaconchain.gnosischain.com/

20. **Is it worth to be a validator?**

Expand Down
4 changes: 2 additions & 2 deletions docs/node/management/migrating-validator.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ title: Migrating a Validator
Migrating validators from one node to another (or from one vm instance to another) requires careful attention to avoid slashing. If you accidentally run the same validator key on 2 instances at the same time, even for a very short time period, you risk being slashed for an Attestation Violation. If this occurs, you will be removed as a validator and your GNO will be frozen and unavailable for withdrawal until after a hard-fork post GC/GBC merge.

:::note
Curious about validators who have been slashed? You can find them here: [https://gnosischa.in/validators/slashings](https://gnosischa.in//validators/slashings)
Curious about validators who have been slashed? You can find them on the [Beacon chain explorer](https://beaconchain.gnosischain.com/validators/slashings).
:::

## Order of Operations
Expand All @@ -24,7 +24,7 @@ Specific instructions will differ depending on the client you are running. In ge
7. Start new validator.

:::danger
Best practice to minimize slashing risks is to wait > 1 epoch [(you can check here to see epoch)](https://gnosischa.in//epochs) following any actions taken by the original validator before starting the new (migrated) validator. This will happen naturally if you stop the original validator at the beginning of the process.
Best practice to minimize slashing risks is to wait > 1 epoch [(you can check here to see epoch)](https://beaconchain.gnosischain.com/epochs) following any actions taken by the original validator before starting the new (migrated) validator. This will happen naturally if you stop the original validator at the beginning of the process.
:::

## Lighthouse
Expand Down
4 changes: 2 additions & 2 deletions docs/node/management/monitoring-node.md
Original file line number Diff line number Diff line change
Expand Up @@ -163,8 +163,8 @@ The site is deprecated

#### Consensus Layer

- **beacon.gnosischain**
[beacon.gnosischain](https://gnosischa.in//) provides insight on consensus layer such as most recent epochs, most recent blocks, and validator's reward on Consensus layer. You can view your validator's info by using its public key or index.
- **Beacon chain explorer**
[Beacon chain explorer](https://beaconchain.gnosischain.com/) provides insight on consensus layer such as most recent epochs, most recent blocks, and validator's reward on Consensus layer. You can view your validator's info by using its public key or index.

To check your Consensus Layer Reward (in mGNO):

Expand Down
6 changes: 3 additions & 3 deletions docs/node/management/withdrawals.md
Original file line number Diff line number Diff line change
Expand Up @@ -49,7 +49,7 @@ Gnosis Chain supports **two** execution‑address credential prefixes:

**How to check**

1. Look up your validator on [gnosischa.in](https://gnosischa.in) → *Withdrawal* tab, **or**
1. Look up your validator on the [Beacon chain explorer](https://beaconchain.gnosischain.com/) → *Withdrawal* tab, **or**
2. Open the `deposit‑m*.json` file you saved when staking and examine `withdrawal_credentials`.

![CheckWC](../../../static/img/node/withdrawal/withdrawcreds.png)
Expand Down Expand Up @@ -79,7 +79,7 @@ ethdo validator credentials set \
--eip4844-prefix=0x02 # ensures 0x02
```

3. **Broadcast** the resulting `change-operations.json` either via the [broadcast tool](https://gnosischa.in/tools/broadcast) or with `curl`:
3. **Broadcast** the resulting `change-operations.json` either via the [broadcast tool](https://beaconchain.gnosischain.com/tools/broadcast) or with `curl`:

```bash
curl -d @change-operations.json \
Expand Down Expand Up @@ -138,7 +138,7 @@ Because Gnosis Chain pays out **GNO** rather than the gas token (xDai), withdraw

* `claimWithdrawal(address validatorRecipient)` – single validator, or
* `claimWithdrawals(address[] validatorRecipients)` – batch.
3. Enter the **withdrawal (recipient) address** exactly as displayed on *gnosischa.in*.
3. Enter the **withdrawal (recipient) address** exactly as displayed on the *Beacon chain explorer*.
4. Sign & send – on confirmation the GNO appears at the recipient address.

> The `withdrawal address` and the `recipient address` are identical. Do *not* paste the long internal address you may see elsewhere.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -25,6 +25,6 @@ You can verify the status of your validators following these steps:
<img src="/img/node/verify/verify-4.jpg" width="600" />
<br />

5. The Gnosis [Beacon Chain Explorer](https://gnosischa.in/) is a fork of the [Ethereum Beaconcha.in](https://beaconcha.in/) explorer.
5. The Gnosis [Beacon chain explorer](https://beaconchain.gnosischain.com/) is a fork of the [Ethereum Beaconcha.in](https://beaconcha.in/) explorer.

See more about the validator statuses and [Deposit Process](https://kb.beaconcha.in/ethereum-2.0-depositing) in the Beaconcha.in Knowledge Base.
Loading
Loading