gnosischain · skundu42 · Apr 15, 2025 · Jul 29, 2024 · Jul 29, 2024 · Jul 29, 2024
diff --git a/.github/workflows/dev_deploy.yml b/.github/workflows/dev_deploy.yml
@@ -28,13 +28,13 @@ jobs:
 
     steps:
       - name: Remove broken apt repos [Ubuntu]
-        if: ${{ matrix.os }} == 'ubuntu-latest'
+        if: runner.os == 'Linux'
         run: |
           for apt_file in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $apt_file; done
 
       - uses: actions/checkout@v4
 
-      - uses: actions/cache@v2
+      - uses: actions/cache@v3
         with:
           path: '**/node_modules'
           key: ${{ runner.os }}-modules-${{ hashFiles('**/yarn.lock') }}
@@ -83,4 +83,4 @@ jobs:
       - name: 'Cloudfront: cache invalidation'
         if: ( github.ref == 'refs/heads/dev' || github.ref == 'refs/heads/main' )
         run: |
-          aws cloudfront create-invalidation --distribution-id ${{ secrets.DEV_AWS_CLOUDFRONT_ID }} --paths "/*"
+          aws cloudfront create-invalidation --distribution-id ${{ secrets.DEV_AWS_CLOUDFRONT_ID }} --paths "/*"
diff --git a/.github/workflows/prod_deploy.yml b/.github/workflows/prod_deploy.yml
@@ -1,87 +1,85 @@
 name: Manual Deployment to Production
 
 on:
-    workflow_dispatch:
-      inputs:
-        tag:
-          description: Tagged version to deploy
-          required: true
-          type: string
+  workflow_dispatch:
+    inputs:
+      tag:
+        description: Tagged version to deploy
+        required: true
+        type: string
 
 concurrency:
   group: ${{ github.workflow }}-${{ github.ref }}
   cancel-in-progress: true
 
 jobs:
-    deploy:
-        name: Deployment
-        runs-on: ubuntu-latest
+  deploy:
+    name: Deployment
+    runs-on: ubuntu-latest
 
-        steps:
-            - name: Remove broken apt repos [Ubuntu]
-              if: ${{ matrix.os }} == 'ubuntu-latest'
-              run: |
-                for apt_file in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $apt_file; done
+    steps:
+      - name: Remove broken apt repos [Ubuntu]
+        if: runner.os == 'Linux'
+        run: |
+          for apt_file in `grep -lr microsoft /etc/apt/sources.list.d/`; do sudo rm $apt_file; done
 
-            # Ref: https://github.com/actions/checkout/issues/1471#issuecomment-1771231294
-            - uses: actions/checkout@v4
-
-            - name: Tag checkout
-              run: |
-                git fetch --prune --unshallow --tags
-                git checkout ${{ github.event.inputs.tag }}
+      # Ref: https://github.com/actions/checkout/issues/1471#issuecomment-1771231294
+      - uses: actions/checkout@v4
 
-            - uses: actions/cache@v2
-              with:
-                path: '**/node_modules'
-                key: ${{ runner.os }}-modules-${{ hashFiles('**/yarn.lock') }}
+      - name: Tag checkout
+        run: |
+          git fetch --prune --unshallow --tags
+          git checkout ${{ github.event.inputs.tag }}
 
-            - name: Setup Node.js
-              uses: actions/setup-node@v2
+      - uses: actions/cache@v3
+        with:
+          path: '**/node_modules'
+          key: ${{ runner.os }}-modules-${{ hashFiles('**/yarn.lock') }}
 
-            - name: Install
-              run: |
-                rm -rf .cache
-                rm -rf build
-                yarn config set cache-folder .yarn
-                yarn install
-                pip install awscli --upgrade --user
+      - name: Setup Node.js
+        uses: actions/setup-node@v2
 
-            - name: Build App for release
-              env:
-                ALGOLIA_ID: ${{ secrets.ALGOLIA_ID }}
-                ALGOLIA_INDEX: ${{ secrets.ALGOLIA_INDEX }}
-                ALGOLIA_KEY: ${{ secrets.ALGOLIA_KEY }}
-                GOOGLE_ANALYTICS_ID: ${{ secrets.PROD_GOOGLE_ANALYTICS_ID }}
-              run: yarn build
+      - name: Install
+        run: |
+          rm -rf .cache
+          rm -rf build
+          yarn config set cache-folder .yarn
+          yarn install
+          pip install awscli --upgrade --user
 
-            - name: Configure AWS Production credentials
-              uses: aws-actions/configure-aws-credentials@v1
-              with:
-                aws-access-key-id: ${{ secrets.PROD_AWS_ACCESS_KEY_ID }}
-                aws-secret-access-key: ${{ secrets.PROD_AWS_SECRET_ACCESS_KEY }}
-                aws-region: ${{ secrets.PROD_AWS_DEFAULT_REGION }}
+      - name: Build App for release
+        env:
+          ALGOLIA_ID: ${{ secrets.ALGOLIA_ID }}
+          ALGOLIA_INDEX: ${{ secrets.ALGOLIA_INDEX }}
+          ALGOLIA_KEY: ${{ secrets.ALGOLIA_KEY }}
+          GOOGLE_ANALYTICS_ID: ${{ secrets.PROD_GOOGLE_ANALYTICS_ID }}
+        run: yarn build
 
-            # Script to deploy to release environment
-            - name: 'Deploy to S3: Release'
-              run: |
-                aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*.html" --exclude "sitemap.xml" --cache-control max-age=86400,public
-                aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*" --include "*.html" --cache-control max-age=0,no-cache,no-store,must-revalidate --content-type text/html
-                aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*" --include "sitemap.xml" --cache-control max-age=0,no-cache,no-store,must-revalidate --content-type text/xml
+      - name: Configure AWS Production credentials
+        uses: aws-actions/configure-aws-credentials@v1
+        with:
+          aws-access-key-id: ${{ secrets.PROD_AWS_ACCESS_KEY_ID }}
+          aws-secret-access-key: ${{ secrets.PROD_AWS_SECRET_ACCESS_KEY }}
+          aws-region: ${{ secrets.PROD_AWS_DEFAULT_REGION }}
 
-            - name: 'Cloudfront: cache invalidation'
-              run: |
-                aws cloudfront create-invalidation --distribution-id ${{ secrets.PROD_AWS_CLOUDFRONT_ID }} --paths "/*"
+      - name: 'Deploy to S3: Release'
+        run: |
+          aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*.html" --exclude "sitemap.xml" --cache-control max-age=86400,public
+          aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*" --include "*.html" --cache-control max-age=0,no-cache,no-store,must-revalidate --content-type text/html
+          aws s3 sync build/ s3://${{ secrets.RELEASE_BUCKET_NAME }} --delete --exclude "*" --include "sitemap.xml" --cache-control max-age=0,no-cache,no-store,must-revalidate --content-type text/xml
 
-    notify:
-      uses: ./.github/workflows/slack_release_notification.yml
-      if: ${{ always() }}
-      needs: [ deploy ]
-      secrets: 
-        RELEASES_SLACK_WEBHOOK_URL: ${{ secrets.RELEASES_SLACK_WEBHOOK_URL }}
-      with:
-        environment: Production
-        service: GC Documentation
-        success: ${{ contains(join(needs.*.result, ','), 'success') }}
-        message: "deploy service `GC Documentation` version `${{ inputs.tag }}`. Triggered by `${{ github.actor }}`."
-
+      - name: 'Cloudfront: cache invalidation'
+        run: |
+          aws cloudfront create-invalidation --distribution-id ${{ secrets.PROD_AWS_CLOUDFRONT_ID }} --paths "/*"
+
+  notify:
+    uses: ./.github/workflows/slack_release_notification.yml
+    if: ${{ always() }}
+    needs: [ deploy ]
+    secrets: 
+      RELEASES_SLACK_WEBHOOK_URL: ${{ secrets.RELEASES_SLACK_WEBHOOK_URL }}
+    with:
+      environment: Production
+      service: GC Documentation
+      success: ${{ contains(join(needs.*.result, ','), 'success') }}
+      message: "deploy service `GC Documentation` version `${{ inputs.tag }}`. Triggered by `${{ github.actor }}`."
diff --git a/docs/bridges/About Token Bridges/hashi-integration.md b/docs/bridges/About Token Bridges/hashi-integration.md
@@ -54,7 +54,7 @@ For Omnibridge / AMB:
 
 ## xDAI briddge
 
-![](../../../static/img/bridges/hashi/Hashi-Gnosis-AMB.png)
+![](../../../static/img/bridges/hashi/Hashi-Gnosis-xDAI.png)
 
 **Ethereum → Gnosis Chain**
 

diff --git a/docs/bridges/About Token Bridges/xdai-bridge.md b/docs/bridges/About Token Bridges/xdai-bridge.md
@@ -7,11 +7,25 @@ keywords: [xdai bridge, bridge, dai, ethereum, gnosis bridge]
 
 # xDai Bridge
 
+:::danger
+Bridging DAI/xDAI using https://bridge.gnosischain.com is currently unavailable.
+We are currently working on resolving the UI issues. We appreciate your patience.
+
+In the meantime, you can still interact directly with the smart contract to relay DAI and xDAI via the xDAI Bridge. To claim the DAI on Ethereum, please check the [tutorial](#claim-dai-on-ethereum-using-smart-contract).
+:::
+
 :::info
 The xDAI bridge can be used in https://bridge.gnosischain.com by selecting DAI/xDAI.  
 Please avoid using the legacy xDai bridge: https://bridge.legacy.gnosischain.com/.
 :::
 
+:::warning
+
+With the Hashi migration for the xDAI bridge, `transfer` will no longer mint xDAI, and users must use `relayTokens` instead.
+For more detail, please check [here](https://forum.gnosis.io/t/decommissioning-of-the-transfer-function-on-xdai-bridge/8575).
+
+:::
+
 The [xDai bridge](https://bridge.gnosischain.com) is a native DAI bridge from Ethereum that is used to mint and burn [xDai](/about/tokens/xdai), the native asset used for gas and transaction fees on Gnosis.
 
 Once Dai is bridged into the xDai bridge, the xDai bridge contract on Gnosis notifies the [block rewards contract](https://gnosis.blockscout.com/address/0x481c034c6d9441db23Ea48De68BCAe812C5d39bA). The consensus algorithm then mints xDai to the user's corresponding address on Gnosis in the next block.
@@ -263,6 +277,19 @@ The second contract is the Interest Receiver. This will be the address provided
 
 </Tabs>
 
+## Tutorials
+
+### Claim DAI on Ethereum using smart contract
+
+1. Fetch the value of `recipient`, `value` and `nonce` from `UserRequestForSignature(address recipient, uint256 value, bytes32 nonce)` from the Gnosis Chain.
+   ![](../../../static/img/bridges/xdaibridge/gc-xdai-tx.png)
+2. Go to the [xDAI bridge helper contract on Gnosis Chain](https://gnosis.blockscout.com/address/0x2d51eaa266eafcb59bb36dd3c7e99c515e58113a#readContract).  
+   3. Call [`getMessageHash(address _recipient,  uint256 _value, _origTxHash)`](https://gnosis.blockscout.com/address/0x2d51eaa266eafcb59bb36dd3c7e99c515e58113a?tab=read_write_contract#0x30322ce7) : with `recipient` and `value` from the `UserRequestForSignature` and `_origTxHash` as `nonce` from `UserRequestForSignature` (not the transaction hash!). Fetch the returned message hash.  
+   4. Call [`getMessage(bytes32 _msgHash)`](https://gnosis.blockscout.com/address/0x2d51eaa266eafcb59bb36dd3c7e99c515e58113a?tab=read_write_contract#0x0139a221) & [`getSignatures(bytes32 _msgHash)`](https://gnosis.blockscout.com/address/0x2d51eaa266eafcb59bb36dd3c7e99c515e58113a?tab=read_write_contract#0x9bc51068) with the message hash from the previous step.
+   ![](../../../static/img/bridges/xdaibridge/xdai-helper.png)
+3. Use the value returned from the previous step to call `executeSignatures(bytes message, bytes signatures)`[Ethereum xDAI Bridge](https://etherscan.io/address/0x4aa42145Aa6Ebf72e164C9bBC74fbD3788045016#writeProxyContract#F7).
+   ![](../../../static/img/bridges/xdaibridge/xdai-execute-signatures.png)
+
 ## Resources
 
 - [Tokenbridge Docs on xDai Bridge](https://github.com/tokenbridge/docs/blob/master/xdai-bridge/about.md)
diff --git a/docs/bridges/management/decisions.md b/docs/bridges/management/decisions.md
@@ -8,6 +8,22 @@ keywords: [governance board, bridge governance]
 
 The [Bridge Governance Board](./#current-bridge-governors) is responsible for enacting updates related to bridge functionality, contract upgrades, and other parameters impacting bridge operations. The following items have been implemented by the board.
 
+## Upgrade xDAI implementation contract for Hashi integraion, replacing Metacartel with Monerium
+
+🗳 Justification:
+
+1. Upgrade xDAI proxy contract to the new Hashi integrated bridge contract according to https://forum.gnosis.io/t/gip-93-should-gnosisdao-support-the-integration-of-hashi-within-gnosis-chains-canonical-bridges/8245:
+   1. Foreign xDAI implementation contract: [0xb54042F5bA4B048fEa54aaE70abbbe41AC716299](https://etherscan.io/address/0xb54042F5bA4B048fEa54aaE70abbbe41AC716299#readContract), version: 9
+   2. Home xDAI Implementation contract: [0xb740472c650fe949931b9df0cb253b48c80c82de](https://gnosisscan.io/address/0xb740472c650fe949931b9df0cb253b48c80c82de#readContract), version: 6
+2. set Hashi Manager for xDAI Bridge
+   1. Hashi Manager on ETH: [0x9acCFAD714A1e670CD1f6dc666FE892d1d5547BD](https://etherscan.io/address/0x9acCFAD714A1e670CD1f6dc666FE892d1d5547BD)
+   2. Hashi Manager on Gnosis Chain: [0x60Aa15198a3AdfC86FF15B941549A6447B2dDB49](https://gnosisscan.io/address/0x60Aa15198a3AdfC86FF15B941549A6447B2dDB49)
+3. Replace MetaCartel in Bridge governors with Monerium
+   1. MetaCartel: 0xd945325557f1FB4374fBf10Ae86D385632Df870A
+   2. Monerium: 0xB646B8b5Fe6cBc7770578B7679208337ef747ae4
+
+✅ Implemented: Apr 15, 2025
+
 ## Replacing bridge governors
 
 🗳 Justification:

diff --git a/docs/bridges/usebridges.md b/docs/bridges/usebridges.md
@@ -16,14 +16,14 @@ You will need xDAI to perform any transactions on Gnosis Chain as it’s the cha
 ### Follow the below steps to get xDAI into your Ethereum address: 
 1. Go to the Gnosis Chain Bridge UI and connect your wallet to the Ethereum Mainnet.
 2. Once connected, you will see your address populated in the header, and your DAI balance will be displayed on the page.
-3. Enter the amount of Dai you would like to transfer to Gnosis, and click the Transfer button.
+3. Enter the amount of DAI you would like to transfer to Gnosis, and click the Transfer button.
 4. The web3 wallet window will open with transaction details. The default gas price is fine, if you would like a faster transaction you can increase. Click Submit or Confirm (depending on wallet) to initiate the transaction.
 5. Wait for the transaction confirmation (this can take some time if the network is super congested). The transaction is considered finalized after 8 blocks. To check on a pending transaction, click on the tx in the UI.
 
 
 ### Follow the below steps to get ERC20 token from Ethereum address to Gnosis Chain:
 
-1. Go the Gnosis Bridge UI
+1. Go to the Gnosis Bridge UI
 2. Connect your wallet to the Ethereum Mainnet
 3. Select the token you want to transfer and enter the amount of token you want.
 4. Click Bridge and sign the transaction
@@ -60,4 +60,4 @@ If you are not coming from other chains, you can choose from a list of third-par
 
 ### Need more help?
 
-Join the Gnosis Chain Discord and if you need to troubleshoot a specific bridge issue, feel free to open a support ticket and tell us more about it.
+Join the Gnosis Chain Discord and if you need to troubleshoot a specific bridge issue, feel free to open a support ticket and tell us more about it.
diff --git a/docs/faq/bridges.md b/docs/faq/bridges.md
@@ -2,7 +2,7 @@
 
 1. Can I bridge tokens between Gnosis Chain and BSC using Omni Bridge
 
-   The BSC - Gnosis Chain bridge has been depreciated you can instead use a third party bridge like Jumper for example.
+   The BSC - Gnosis Chain bridge has been deprecated you can instead use a third party bridge like Jumper for example.
 
 2. What is the best way to bridge it to another chain?
 
@@ -137,4 +137,4 @@ main();
 ```mdx-code-block
 </div>
 </details>
-```
+```
diff --git a/docs/node/Node Tools/dappnode.md b/docs/node/Node Tools/dappnode.md
@@ -7,7 +7,7 @@ title: DAppNode
 [DAppNode](https://dappnode.com/) is a simple platform for deploying and hosting DApps, P2P clients, and blockchain nodes. It provides a user-friendly way to set up and configure nodes with a couple of clicks.  It is a Free Open Source Software, and can be used in the following ways
 
 1. Purchase one of their pre-installed [DAppNode Servers](https://dappnode.com/en-us/collections/frontpage). These are designed to be able to be run by those with very little technical know-how, and requires no command line at any point.
-2. Install DAppNode software on any compatible hardware or even a VPS. The installation is done by following the their official installation documentation [Here](https://docs.dappnode.io/user/quick-start/Core/installation)
+2. Install DAppNode software on any compatible hardware or even a VPS. The installation is done by following their official installation documentation [Here](https://docs.dap
10000
pnode.io/user/quick-start/Core/installation)
 
 ## Using DAppNode {#install-on-dappnode}
 
@@ -25,16 +25,16 @@ Make sure to select the Gnosis chain tab,
 
 The next step is to select the combination of client you want to use in your dappnode. For this process you need to select:
 
-- 1. Select the execution client: Nethermind-xdai. Click in the package
+- 1. Select the execution client: Nethermind-xdai. Click on the package
 - 2. Select the consensus client, here you can install one of the following options: Teku-gnosis, Lighthouse-gnosis and Prysm-gnosis
-- 3. Install the web3signer. This is required becausethis is the package that will contain the keystores.
+- 3. Install the web3signer. This is required because this is the package that will contain the keystores.
 
 ![Select the execution and consensus clients](/img/node/dappnode-stakers-ui-2.png)
 
 1. Select the Execution client. For now, or in the moment this guide was created, nethermind is the only execution client that supports gnosis chain.
    ![Execution client ](/img/node/dappnode-execution-client.png)
 
-2. Select the consensus client. You will see the next fields when you click in the package chard.
+2. Select the consensus client. You will see the next fields when you click in the package chart.
 
 ![Select a consensus client](/img/node/dappnode-consensus-client.png)
 

diff --git a/docs/node/README.md b/docs/node/README.md
@@ -5,9 +5,9 @@ sidebar_position : 1
 
 # Run a Node
 
-![Screenshot 2024-05-15 at 13 11 23](https://github.com/gnosischain/documentation/assets/75987728/72e33372-bb7e-4f03-8559-8c6e9c232672)
+![Screenshot 2025-04-09 at 09 55 38](https://github.com/user-attachments/assets/98a33f0a-37b3-4c14-8536-7ee91e67b100)
 
-**Image:** Gnosis nodes around the world, circa May 15 2024
+**Image:** Gnosis nodes around the world, circa April 9 2025
 
 ## Open Infrastructure Powered by Solo Stakers
 
@@ -24,7 +24,7 @@ Gnosis is persistently committed to building the open infrastructure for a decen
 
 - Gnosis runs the same composite client software and tooling stack as Ethereum
 - In some cases, Gnosis clients are just Ethereum clients run with a `--network` flag! (e.g. [Nethermind](https://downloads.nethermind.io/), [Lighthouse](https://lighthouse.sigmaprime.io/), etc)
-- Gnosis aims to be a learning ground for a new generation of node runners, requiring only 1 GNO (around $350 at March 2024) instead of the 32 ETH (around $100.000 at March 2024) minimum required for Ethereum
+- Gnosis aims to be a learning ground for a new generation of node runners, requiring only 1 GNO (around $100 at April 2025) instead of the 32 ETH (around $47.000 at April 2025) minimum required for Ethereum
 - Gnosis Chain runs the same client software as Ethereum, with minor parameter tweaks. As such, Gnosis is a Proof-of-Stake network that uses Ethereum's Beacon Chain consensus.
 
 ## Choosing an Approach

diff --git a/docs/node/architecture.md b/docs/node/architecture.md
@@ -12,7 +12,7 @@ Gnosis is an open peer-to-peer network of nodes operated by anyone in the world
 
 Gnosis utilizes the same architecture as Ethereum, and has committed to building together with Ethereum and contributing to the research, engineering and tooling for Ethereum's stack.
 
-Gnosis started out as a [proof-of-authority ](../about/specs/consensus/aura.md) sidechain to Ethereum with its own consensus algorithm in 2017. Gnosis [Merged](/updates/2022/12/10/merge) successful at block 6,306,357 deprecating legacy differences and aligning with Ethereum's new architecture, beginning with the Merge, with a goal of achieving 1:1 parity with Ethereum.
+Gnosis started out as a [proof-of-authority ](../about/specs/consensus/aura.md) sidechain to Ethereum with its own consensus algorithm in 2017. Gnosis [Merged](/updates/2022/12/10/merge) successfully at block 6,306,357 deprecating legacy differences and aligning with Ethereum's new architecture, beginning with the Merge, with a goal of achieving 1:1 parity with Ethereum.
 
 ## Composite Network Architecture