Please add severel core devs call notes!

.github/workflows/tag_release.yml

@@ -3,7 +3,11 @@ name: Create Github Release
 on:
   push:
     tags:
-      - '[0-9]+.[0-9]+.[0-9]+'
+      - 'v[0-9]+.[0-9]+.[0-9]+'
+
+# Permission can be added at job level or workflow level    
+permissions:
+  contents: write # This is required for actions/checkout and create release
 
 jobs:
   release:
@@ -25,15 +29,15 @@ jobs:
         with:
           github-token: ${{ secrets.GITHUB_TOKEN }}
           script: |
-            if (!${{ github.ref_name }}) {
+            if (!${{ toJson(github.ref_name) }}) {
               core.setFailed("RELEASE_TAG is not defined.")
 
               return;
             }
             try {
               const response = await github.rest.repos.createRelease({
-                name: ${{ github.ref_name }},
-                tag_name: ${{ github.ref_name }},
+                name: ${{ toJson(github.ref_name) }},
+                tag_name: ${{ toJson(github.ref_name) }},
                 draft: false,
                 generate_release_notes: true,
                 owner: context.repo.owner,

README.md

@@ -8,6 +8,21 @@ The website is built using [Docusaurus 2](https://docusaurus.io/).
 
 The Documentation is an ecosystem tool, we welcome everybody to collaborate and improve it! See the [contributing page](CONTRIBUTING.md) for details.
 
+## Release process
+
+Releases to production are managed through the creation of a tagged version.
+
+This step-by-step guide will walk you through getting ready for the deployment.
+
+1. Create a Pull Request to merge `dev` branch onto the `main` branch, ask code maintainers to review and approve the PR
+2. Once merged, create a tagged version in the form of `vMayor.Minor.Patch`, wait for the [CIs](https://github.com/gnosischain/documentation/blob/dev/.github/workflows/tag_release.yml) to run, the CI will craft a Github release automatically containing the release notes, check the release out in [releases](https://github.com/gnosischain/documentation/releases)
+3. Go to Actions page, search for `Manual deployment to production`, [here the link](https://github.com/gnosischain/documentation/actions/workflows/prod_deploy.yml).
+    - click on `Run workflow`, this will open a drop-down menu
+    - Set `use workflow from main` (it doesn't perform any actions on our CIs, but Github is still asking for a proper value)
+    - Provide the version to deploy in the form of `vMayor.Minor.Patch`
+    - refresh the page, a new job will be marked as running, enter the job to check the logs out
+4. A notification is sent on Slack to the DevOps team containing the project being deployed, the version and the name of the user who triggered the action
+
 ## Credits
 
 Some content in this site was adapted or inherited from the work done by [Andrew](https://github.com/andogro), [Igor](https://github.com/igorbarinov) and team on the development of xDai. We thank them for the great job done!

docs/about/specs/hard-forks/dencun.md

@@ -56,23 +56,23 @@ Gnosis chain has both a lower `CHURN_LIMIT_QUOTIENT` and faster epoch times. A `
 
 | Network | Timestamp  | Date & Time (UTC)                 | Fork Hash | Beacon Chain Epoch |
 | ------- | ---------- | --------------------------------- | --------- | ------------------ |
-| Chiado  | 1706724940 | Wed Jan 31 2024 18:15:40 GMT+0000 | -         | 516608             |
-| Mainnet | 1710181820 | Monday March 11 202418:30:20 +UTC | -         | 889856             |
+| Chiado  | 1706724940 | Wed Jan 31 2024 18:15:40 GMT+0000 |  0x5fbc16bc  | 516608             |
+| Mainnet | 1710181820 | Monday March 11 202418:30:20 +UTC |  0x1384dfc1  | 889856             |
 
 ## How to Prepare
 
 ### For Validators
 
-1. Update your clients:
+Update your clients:
 
    Execution Layer
 
-   - ✅ NethermindEth [v1.25.3](https://github.com/NethermindEth/nethermind/releases/tag/1.25.3)
-   - ✅ ErigonEth [v2.57.1](https://github.com/ledgerwatch/erigon/releases/tag/v2.57.1)
+   - ✅ NethermindEth [v1.25.4+](https://github.com/NethermindEth/nethermind/releases/)
+   - ✅ ErigonEth [v2.58.0+](https://github.com/ledgerwatch/erigon/releases/)
 
    Consensus Layer
 
-   - ✅ Lighthouse [v4.6.0](https://github.com/sigp/lighthouse/releases/tag/v4.6.0)
-   - ✅ Teku [v24.1.1](https://github.com/Consensys/teku/releases/tag/24.1.1)
-   - ✅ Nimbus [v24.1.2](https://github.com/status-im/nimbus-eth2/releases/tag/v24.1.2)
-   - ✅ Lodestar [v1.15.0](https://github.com/ChainSafe/lodestar/releases/tag/v1.15.0)
+   - ✅ Lighthouse [v5.0.0+](https://github.com/sigp/lighthouse/releases/)
+   - ✅ Teku [v24.2.0+](https://github.com/Consensys/teku/releases/)
+   - ✅ Nimbus [v24.2.1+](https://github.com/status-im/nimbus-eth2/releases/)
+   - ✅ Lodestar [v1.16.0+](https://github.com/ChainSafe/lodestar/releases/)

docs/about/specs/hard-forks/shanghai-capella.md

@@ -12,11 +12,12 @@ Validator withdrawal allows a validator's account balance get withdrawn from Bea
 
 Check out [validator withdrawal](/node/management/withdrawals) for more details.
 
-## When did Shanghai/Capella hardfork happen?
+## Upgrade Schedule
 
-Epoch: 648704  
-Slot: 10379264  
-Time: August 1, 2023 at 11:34.20 UTC
+| Network | Timestamp    | Date & Time (UTC)             | Fork Hash | Beacon Chain Epoch |
+| ------- | ------------ | ----------------------------- | --------- | ------------------ |
+| Chiado  | 1684934220 | May-24-2023 13:17:00 +UTC | 0xa15a4252 | 244224             |
+| Mainnet | 1690889660 | Aug-01-2023 11:34:20 +UTC | 0x2efe91ba | 648704             |
 
 ## How to Prepare
 
@@ -32,22 +33,22 @@ Time: August 1, 2023 at 11:34.20 UTC
 
    Execution Layer:
 
-   ✅ NethermindEth [v1.19.3](https://github.com/NethermindEth/nethermind/releases/tag/1.19.3)  
+   ✅ NethermindEth [v1.19.3](https://github.com/NethermindEth/nethermind/releases/tag/1.19.3)
    ✅ ErigonEth [v2.48.0](https://github.com/ledgerwatch/erigon/releases/tag/v2.48.0)
 
    Consensus Layer:
 
-   ✅ Lighthouse [v4.3.0](https://github.com/sigp/lighthouse/releases/tag/v4.3.0)  
-   ✅ Teku [v23.6.1](https://github.com/Consensys/teku/releases/tag/23.6.1)  
-   ✅ Nimbus v23.6.0 (only with the following Docker image: http://ghcr.io/gnosischain/gnosis-nimbus-eth2:v23.6.0)  
+   ✅ Lighthouse [v4.3.0](https://github.com/sigp/lighthouse/releases/tag/v4.3.0)
+   ✅ Teku [v23.6.1](https://github.com/Consensys/teku/releases/tag/23.6.1)
+   ✅ Nimbus v23.6.0 (only with the following Docker image: http://ghcr.io/gnosischain/gnosis-nimbus-eth2:v23.6.0)
    ✅ Lodestar [v1.9.1](https://github.com/ChainSafe/lodestar/releases/tag/v1.9.1)
 
    DAppNode Packages
 
-   ✅ Teku Gnosis v0.1.9  
-   ✅ Lighthouse Gnosis v0.1.10  
-   ✅ Lodestar Gnosis v0.1.2  
-   ✅ Nethermind xDAI v1.0.34  
+   ✅ Teku Gnosis v0.1.9
+   ✅ Lighthouse Gnosis v0.1.10
+   ✅ Lodestar Gnosis v0.1.2
+   ✅ Nethermind xDAI v1.0.34
    ⌛️ Erigon and Nimbus - Forthcoming
 
 ## How to claim your withdrawal?

docs/bridges/Build with Bridges/using-omnibridge/README.md

@@ -21,7 +21,7 @@ It is possible to use the [Gnosis Bridge](https://bridge.gnosischain.com) to tra
 
 In this example, we transfer the Basic Attention Token (BAT) from Ethereum to xDai. When this process was started, this token does not yet exist on Gnosis. It takes less than 5 minutes and some ETH for gas fees.
 
-1. Go the the [Legacy OmniBridge UI](https://omni.legacy.gnosischain.com/bridge)
+1. Go to the [Legacy OmniBridge UI](https://omni.legacy.gnosischain.com/bridge)
 
 - Connect your wallet to the Ethereum Mainnet
 - Select the token you want to transfer (here we select BAT) and enter the amount

docs/bridges/Build with Bridges/using-omnibridge/specific-tokens.md

@@ -31,7 +31,7 @@ In the second part of the tutorial, you will learn how to bridge GNO between Goe
 
 5. When the transaction is included in the block, click on the transaction link to get the transaction details
    ![](/img/bridges/omni-bridge-to-native-eth3.png)
-6. Use the "View in ALM App" link on the page with transaction details, or use the transaction hash and go the the [ALM site](https://alm-bridge-monitor.gnosischain.com/) and enter it manually to track status of the transfer and finalize bridge operations if required.  
+6. Use the "View in ALM App" link on the page with transaction details, or use the transaction hash and go to the [ALM site](https://alm-bridge-monitor.gnosischain.com/) and enter it manually to track status of the transfer and finalize bridge operations if required.  
    ![](/img/bridges/omni-bridge-to-native-eth4.png)
 7. Eventually, when an executing transaction on the Mainnet is processed, the WETH will be unlocked and unwrapped to ETH native tokens:
    ![](/img/bridges/omni-bridge-to-native-eth5.png)

updates/2022/12-05-bridges-pause.md

@@ -14,7 +14,7 @@ tags: [bridges, merge]
 
 ### Pausing of Bridges
 
-24 hours prior to the Merge TTD (currently tracking for ~8th Dec 2022 18:43 UTC), the [Gnosis Bridge Governance Multisig](/bridges/governance) will execute a transaction to set the the following bridge parameters. 
+24 hours prior to the Merge TTD (currently tracking for ~8th Dec 2022 18:43 UTC), the [Gnosis Bridge Governance Multisig](/bridges/governance) will execute a transaction to set the following bridge parameters. 
 
 | Bridge                                                                                                                             | Details                                                                                                                        |
 | ---------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------ |

updates/2024/04-24-core-devs-call.md

@@ -0,0 +1,109 @@
+---
+title: Core Devs Call - 2024/04/24
+authors: [dapplion, armaganercan, filoozom]
+tags: [CoreDevsCall, Gnosis Chain]
+---
+
+# Gnosis Core Devs Call Notes
+
+Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.
+
+Participants represent teams:
+
+Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.
+
+With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.
+
+Missed the meeting? Catch the [full recording on Gnosis Chain YouTube channel.](https://youtu.be/wtQ8oVIRVlU)
+
+April 24, 2024
+
+# Client Team Updates
+## EL
+
+* **Nethermind**: 
+    * Working on Pectra, close to be ready for devnet0 (expected next week but will be announced at ACD)
+    * Testing snap sync
+    * Release planned for tomorrow
+        * One potential bug remaining
+        * Includes half-path and snap sync server for newly synced nodes by default
+        * Snap sync in ~45 minutes with one peer
+            * Nethermind ↔ Nethermind snap sync tested and working
+            * Nethermind from Geth also worked
+
+
+* **Erigon**: 
+  * Working on Pectra
+
+* **Geth**:
+  * Fully syncs on GC!
+  * Serving snap sync, was able to snap sync a few nodes from it
+  * 3 official Geth nodes were deployed an synced, can be used for snap syncing
+    * Enodes to be sent in the Telegram group
+  * Working on a rebase from a more recent Geth version
+  * Block building seems to be broken
+  * There’s a bug for full sync that needs to be addressed
+  * Very positive in general, just some housekeeping left
+
+
+# Chain Infra
+
+* **Gateway**
+  * Fixed the checkpointz endpoint
+  * Observed OOM issues with 1.25.4
+    * The node was killed and couldn’t resync after restarting
+    * Will keep Nethermind posted with logs and information
+
+
+# Innovation
+
+* Shutter
+    * Pushed a new update with the new curves in keypers
+        * Working on integrating with that
+    * Working on the libp2p stability issue (probably linked to GossipSub implementation)
+
+
+# Research
+
+* EIP-3074 + EIP-5003
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

updates/2024/05-08-core-devs-call.md

@@ -0,0 +1,104 @@
+---
+title: Core Devs Call - 2024/05/08
+authors: [dapplion, armaganercan, filoozom]
+tags: [CoreDevsCall, Gnosis Chain]
+---
+
+# Gnosis Core Devs Call Notes
+
+Welcome to the Gnosis Core Devs weekly gathering. Every Wednesday, key members from the Gnosis team, contributors, and various team representatives convene to discuss, collaborate, and update one another on the Gnosis ecosystem's progression.
+
+Participants represent teams:
+
+Erigon, Gateway, Nethermind, Geth, Gnosis DevOps, Gnosis Core Devs, Gnosis Comms team.
+
+With a diverse set of voices present, our discussions are rich, multifaceted, and aim to foster innovation within the community.
+
+Missed the meeting? Catch the [full recording on Gnosis Chain YouTube channel.](https://youtu.be/07-TtrWiBCk)
+
+May 08, 2024
+
+# Client Team Updates
+## EL
+
+* **Nethermind**: 
+    * Snap sync and half-path published last week
+    * Preparing for Pectra
+
+
+* **Erigon**: 
+  * Switched internal development to Erigon 3
+  * Release candidate of Erigon v2.60.0
+    * Should be the last significant v2 release
+    * There might still be patch releases
+    * Includes the `eth_getLogs` regression introduced in v2.59
+      * Log pruning issue fix described in the release notes: 
+          * https://github.com/ledgerwatch/erigon/releases/tag/v2.60.0-rc1
+                * Required for people who ran v2.59 with pruning
+  * Erigon v3
+    * Syncs way faster (doesn’t have to execute all blocks since genesis)
+    * Granularity of state history is much finer
+    * Should be cheaper to run because less data has to be on fast drives and colder history can be on cheaper disks
+
+
+* **Geth**:
+  * No update
+
+
+# Chain Infra
+
+* **Gateway**
+  * No update
+
+
+# Innovation
+
+* Shutter
+    * Nethermind now integrates with the keypers, nothing is hardcoded anymore
+    * Working on a few stability improvements
+        * Syncing / missed slots: fixed
+        * Gossipsub disconnection issue still ongoing
+        * Not receiving keys on time
+        * Discovered an issue on the keyper side for key signing
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+

updates/archive/2020/xdai-weekly-recap-18-12-2020.md

@@ -25,7 +25,7 @@ https://twitter.com/blockscoutcom/status/1339631851644719104
 
 ## :christmas\_tree: Swether NFTs
 
-Just in time for the holidays you can create your own custom NFT in a holiday sweater pattern, and the xDai logo is one a handful available to add! This fun project is made possible by the The Treum team, part of ConsenSys Mesh.\
+Just in time for the holidays you can create your own custom NFT in a holiday sweater pattern, and the xDai logo is one a handful available to add! This fun project is made possible by The Treum team, part of ConsenSys Mesh.\
 \
 Bonus for US residents - mint a token and get a FREE SWEATSHIRT with your design on it! Swether minting season ends Dec 31, 2020.\
 \

updates/archive/2021/xdai-weekly-recap-14-05-2021.md

@@ -86,7 +86,7 @@ UI Customizations include additional items added to the Apps Menu and trading ic
 
 ### Project Page Updates
 
-Explore xDai diversity and the the more than 100+ projects and growing currently deployed on the xDai chain. We updated our projects page to include additional NFT and DeFi projects and more. If you have a project utilizing xDai, please get in touch so we can add it to our list.
+Explore xDai diversity and more than 100+ projects and growing currently deployed on the xDai chain. We updated our projects page to include additional NFT and DeFi projects and more. If you have a project utilizing xDai, please get in touch so we can add it to our list.
 
 ### Cryptokek Integration