Merge branch 'main' into julien/signature-payload

julienrbrt · web-flow · commit 011e9cdff395 · 2025-08-26T17:32:54.000+02:00
diff --git a/.github/workflows/claude-code-review.yml b/.github/workflows/claude-code-review.yml
@@ -33,7 +33,7 @@ jobs:
 
       - name: Run Claude Code Review
         id: claude-review
-        uses: anthropics/claude-code-action@beta
+        uses: anthropics/claude-code-action@ada5bc42ebb031c1b30d9e12ec73cb7f978b4846
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
 
diff --git a/.github/workflows/claude.yml b/.github/workflows/claude.yml
@@ -32,7 +32,7 @@ jobs:
 
       - name: Run Claude Code
         id: claude
-        uses: anthropics/claude-code-action@beta
+        uses: anthropics/claude-code-action@ada5bc42ebb031c1b30d9e12ec73cb7f978b4846
         with:
           claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
 
diff --git a/docs/README.md b/docs/README.md
@@ -1,7 +1,5 @@
 # Evolve Documentation Site
 
-[![Deploy](https://github.com/evstack/ev-node/actions/workflows/deploy.yml/badge.svg)](https://github.com/evstack/ev-node/actions/workflows/deploy.yml)
-
 Welcome to the official documentation repository for Evolve.
 
 Here you'll find comprehensive guides, and reference materials to help you make the most out of Evolve.
diff --git a/docs/guides/create-genesis.md b/docs/guides/create-genesis.md
@@ -6,7 +6,7 @@ This guide will walk you through the process of setting up a genesis for your ch
 
 For this guide you need to have a chain directory where you have created and built your chain.
 
-If you don't have a chain directory yet, you can initialize a simple ignite chain by following [this tutorial](/docs/guides/gm-world.md)
+If you don't have a chain directory yet, you can initialize a simple ignite chain by following [this tutorial](./gm-world.md)
 
 :::tip
 This guide will use the simple ignite chain created in linked guide. Make sure to update any relevant variables to match your chain.
@@ -27,7 +27,7 @@ STAKING_AMOUNT="1000000000stake"
 
 ## Rebuild your chain
 
-Ensure that `.gm` folder is present at `/Users/you/.gm` (if not, follow a [Guide](/docs/guides/gm-world.md) to set it up) and run the following command to (re)generate an entrypoint binary out of the code:
+Ensure that `.gm` folder is present at `/Users/you/.gm` (if not, follow a [Guide](./gm-world.md) to set it up) and run the following command to (re)generate an entrypoint binary out of the code:
 
 ```sh
 make install
diff --git a/docs/guides/da/celestia-da.md b/docs/guides/da/celestia-da.md
@@ -9,7 +9,7 @@ import constants from '../../.vitepress/constants/constants.js'
 
 This tutorial serves as a comprehensive guide for deploying your chain on Celestia's data availability (DA) network. From the Evolve perspective, there's no difference in posting blocks to Celestia's testnets or Mainnet Beta.
 
-Before proceeding, ensure that you have completed the [gm-world](/docs/guides/gm-world.md) tutorial, which covers installing the Testapp CLI and running a chain against a local DA network.
+Before proceeding, ensure that you have completed the [gm-world](./gm-world.md) tutorial, which covers installing the Testapp CLI and running a chain against a local DA network.
 
 ## 🪶 Running a Celestia light node
 
@@ -46,7 +46,7 @@ After successfully starting a light node, it's time to start posting the batches
 
 ## 🏗️ Prerequisites {#prerequisites}
 
-- `gmd` CLI installed from the [gm-world](/docs/guides/gm-world.md) tutorial.
+- `gmd` CLI installed from the [gm-world](./gm-world.md) tutorial.
 
 ## 🛠️ Configuring flags for DA
 
diff --git a/docs/guides/da/local-da.md b/docs/guides/da/local-da.md
@@ -9,15 +9,15 @@ import constants from '../../.vitepress/constants/constants.js'
 
 This tutorial serves as a comprehensive guide for using the [local-da](https://github.com/evstack/ev-node/tree/main/da/cmd/local-da) with your chain.
 
-Before proceeding, ensure that you have completed the [build a chain](/docs/guides/gm-world.md) tutorial, which covers setting-up, building and running your chain.
+Before proceeding, ensure that you have completed the [build a chain](./gm-world.md) tutorial, which covers setting-up, building and running your chain.
 
 ## Setting Up a Local DA Network
 
 To set up a local DA network node on your machine, run the following script to install and start the local DA node:
 
 ```bash
 git clone  --depth=1 --branch v1.0.0-beta.2 https://github.com/evstack/ev-node.git
-cd ev-node 
+cd ev-node
 make build-da
 ./build/local-da
 ```
diff --git a/docs/guides/deploy/local.md b/docs/guides/deploy/local.md
@@ -1,6 +1,6 @@
 # 🏠 Local
 
-This tutorial is going to show you how to deploy the [gm-world chain](/docs/guides/gm-world.md) using Docker Compose.
+This tutorial is going to show you how to deploy the [gm-world chain](./gm-world.md) using Docker Compose.
 
 You can learn more about Docker Compose [here](https://docs.docker.com/compose/).
 
@@ -17,7 +17,7 @@ import constants from '../../.vitepress/constants/constants.js'
 
 ## 💻 Pre-requisites {#prerequisites}
 
-Make sure you have your gm-world chain ready by completing [the Build your chain tutorial](/docs/guides/gm-world.md).
+Make sure you have your gm-world chain ready by completing [the Build your chain tutorial](./gm-world.md).
 
 ## 🛠️ Dependencies {#dependencies}
 
diff --git a/docs/guides/deploy/overview.md b/docs/guides/deploy/overview.md
@@ -6,7 +6,7 @@ description: This page provides an overview of some common ways to deploy chains
 
 One of the benefits of building chains with Evolve is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.
 
-You can learn more about Evolve architecture [here](/learn/specs/overview.md).
+You can learn more about Evolve architecture [here](../../learn/specs/overview.md).
 
 The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your chain.
 
diff --git a/docs/guides/deploy/testnet.md b/docs/guides/deploy/testnet.md
@@ -2,7 +2,7 @@
 
 This tutorial is going to show you how to deploy a Evolve testnet, focusing on the architecture choices and components that make up a complete EVM-based chain deployment.
 
-You can learn more about Evolve EVM architecture [here](/learn/execution.md).
+You can learn more about Evolve EVM architecture [here](../../learn/execution.md).
 
 <!-- markdownlint-disable MD033 -->
 <script setup>
@@ -90,7 +90,7 @@ graph TB
 
 ## 💻 Pre-requisites {#prerequisites}
 
-Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](/learn/sequencing/overview.md).
+Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](../..//learn/sequencing/overview.md).
 
 ## 🛠️ Dependencies {#dependencies}
 
@@ -107,7 +107,7 @@ Currently, Evolve supports one sequencing implementation:
 - **Advantages**: Easy setup, fast block production, independence from DA block time
 - **Requirements**: One sequencer node, multiple optional full nodes
 
-For detailed information about sequencing topologies, see the [Sequencing Overview](/learn/sequencing/overview.md) and [Single Sequencer](/learn/sequencing/single.md) documentation.
+For detailed information about sequencing topologies, see the [Sequencing Overview](../../learn/sequencing/overview.md) and [Single Sequencer](../../learn/sequencing/single.md) documentation.
 
 ## 🏗️ Deployment Architecture {#deployment-architecture}
 
@@ -300,8 +300,8 @@ Congratulations again! You now know how to deploy Evolve EVM chains and understa
 
 For detailed setup instructions, see:
 
-- [Single Sequencer Setup Guide](/guides/evm/single.md) - Step-by-step deployment instructions
-- [RETH Backup Guide](/guides/evm/reth-backup.md) - Data protection and backup procedures
-- [Celestia DA Guide](/guides/da/celestia-da.md) - Connecting to Celestia networks
+- [Single Sequencer Setup Guide](../evm/single.md) - Step-by-step deployment instructions
+- [RETH Backup Guide](../evm/reth-backup.md) - Data protection and backup procedures
+- [Celestia DA Guide](../da/celestia-da.md) - Connecting to Celestia networks
 
-You can also learn more about local deployments in our [Docker Compose guide](/docs/guides/deploy/local.md).
+You can also learn more about local deployments in our [Docker Compose guide](../deploy/local.md).
diff --git a/docs/guides/execution/cosmwasm.md b/docs/guides/execution/cosmwasm.md
@@ -24,7 +24,7 @@ this tutorial.
 
 ## 💻 CosmWasm dependency {#dependencies}
 
-As with the [GM Chain](/docs/guides/gm-world.md), we use [kurtosis](https://docs.kurtosis.com/) to help with managing all the services we need to run. You can [install kurtosis here](https://docs.kurtosis.com/install).
+As with the [GM Chain](./gm-world.md), we use [kurtosis](https://docs.kurtosis.com/) to help with managing all the services we need to run. You can [install kurtosis here](https://docs.kurtosis.com/install).
 
 Once installed, you can verify the installation by running:
 
diff --git a/docs/guides/full-node.md b/docs/guides/full-node.md
@@ -6,7 +6,7 @@ This guide covers how to set up a full node to run alongside a sequencer node in
 
 ## Prerequisites
 
-Before proceeding, ensure that you have completed the [build a chain](/docs/guides/gm-world.md) tutorial, which covers setting-up, building and running your chain.
+Before proceeding, ensure that you have completed the [build a chain](./gm-world.md) tutorial, which covers setting-up, building and running your chain.
 
 Ensure that you have:
 
diff --git a/docs/guides/gm-world.md b/docs/guides/gm-world.md
@@ -7,7 +7,7 @@ description: Learn how to build and deploy a CosmWasm-based "gm" (good morning)
 
 ## 🌞 Introduction {#introduction}
 
-This tutorial will guide you through building a evolve `gm-world` chain (`gm` stands for "good morning") using Evolve. Unlike the [quick start guide](/docs/guides/quick-start.md), this tutorial provides a more practical approach to understanding evolve chain development.
+This tutorial will guide you through building a evolve `gm-world` chain (`gm` stands for "good morning") using Evolve. Unlike the [quick start guide](./quick-start.md), this tutorial provides a more practical approach to understanding evolve chain development.
 
 We will cover:
 
@@ -105,7 +105,7 @@ First lets start the local DA network:
 
 ```bash
 git clone  --depth=1 --branch v1.0.0-beta.2 https://github.com/evstack/ev-node.git
-cd ev-node 
+cd ev-node
 make build-da
 ./build/local-da
 ```
diff --git a/docs/guides/metrics.md b/docs/guides/metrics.md
@@ -12,7 +12,7 @@ Metrics will be served under `/metrics` on port 26660 by default. The listening
 
 ## List of available metrics
 
-You can find the full list of available metrics in the [Technical Specifications](../learn/specs/block-manager.html#metrics).
+You can find the full list of available metrics in the [Technical Specifications](../learn/specs/block-manager.md#metrics).
 
 ## Viewing Metrics
 
diff --git a/docs/guides/reset-state.md b/docs/guides/reset-state.md
@@ -14,7 +14,7 @@ Some reason you might need to reset the state of your chain are:
 
 ## Prerequisites
 
-In order to complete this guide, you will need to have completed either the [quick start tutorial](/docs/guides/quick-start.md) or the [build our chain tutorial](/docs/guides/gm-world.md).
+In order to complete this guide, you will need to have completed either the [quick start tutorial](./quick-start.md) or the [build our chain tutorial](./gm-world.md).
 
 ## Quick Start
 
@@ -74,7 +74,7 @@ When you launch your chain again with `testapp start` your `data` directory will
 
 ## gm-world
 
-When you ran your gm-world chain in the [build your chain tutorial](/docs/guides/gm-world.md), it created a `.gm` directory in your `$HOME` directory.
+When you ran your gm-world chain in the [build your chain tutorial](./gm-world.md), it created a `.gm` directory in your `$HOME` directory.
 
 This directory will look like the following:
 
diff --git a/docs/guides/restart-chain.md b/docs/guides/restart-chain.md
@@ -9,7 +9,7 @@ This section covers the case where you need to restart your chain.
 In order to restart your chain, you simply need to run the `<your-binary>d start [...args]`
 command for your chain.
 
-For example, if you ran the [quick start](/docs/guides/quick-start.md) tutorial, you started your chain with:
+For example, if you ran the [quick start](./quick-start.md) tutorial, you started your chain with:
 
 ```bash
 testapp start
@@ -48,7 +48,7 @@ you are using to post blocks to your DA and consensus layer runs out of funds (t
 and you need to restart your chain.
 
 In this example, we're using Celestia's [Mocha testnet](https://docs.celestia.org/how-to-guides/mocha-testnet/)
-and running the [quick start](/docs/guides/quick-start.md). In this example, our Celestia DA light node
+and running the [quick start](./quick-start.md). In this example, our Celestia DA light node
 ran out of Mocha testnet TIA and we are unable to post new blocks to Celestia due to a
 [`Code: 19`](https://github.com/cosmos/cosmos-sdk/blob/main/types/errors/errors.go#L95)
 error. This error is defined by Cosmos SDK as:
@@ -88,7 +88,7 @@ You can stop your chain by using `Control + C` in your terminal where the node i
 
 ### ⛽ Increase the gas fee {#increase-gas-fee}
 
-To reiterate, before restarting the chain, you will need to increase the gas fee in order to avoid a `Code: 19` error. See the [How to configure gas price](/docs/learn/config.md#da-gas-price) guide for more information.
+To reiterate, before restarting the chain, you will need to increase the gas fee in order to avoid a `Code: 19` error. See the [How to configure gas price](../learn/config.md#da-gas-price) guide for more information.
 
 ### 🔁 Restarting your chain {#restarting-your-chain}
 
diff --git a/docs/guides/use-tia-for-gas.md b/docs/guides/use-tia-for-gas.md
@@ -2,13 +2,13 @@
 
 ## 🌞 Introduction {#introduction}
 
-This tutorial will guide you through building a sovereign `gm-world` chain using Evolve, with TIA as the gas token. Unlike the [quick start guide](/docs/guides/quick-start.md), which uses a native chain token for gas, this tutorial demonstrates how to integrate an IBC-enabled token, TIA, as the gas token within the chain, providing a deeper exploration of sovereign chain development.
+This tutorial will guide you through building a sovereign `gm-world` chain using Evolve, with TIA as the gas token. Unlike the [quick start guide](./quick-start.md), which uses a native chain token for gas, this tutorial demonstrates how to integrate an IBC-enabled token, TIA, as the gas token within the chain, providing a deeper exploration of sovereign chain development.
 
 No prior understanding of the build process is required, just that it utilizes the [Cosmos SDK](https://github.com/cosmos/cosmos-sdk) for blockchain applications.
 
 ## Requirements {#requirements}
 
-Before proceeding, ensure that you have completed the [build a chain](/docs/guides/gm-world.md) tutorial, which covers setting-up, building and running your chain.
+Before proceeding, ensure that you have completed the [build a chain](./gm-world.md) tutorial, which covers setting-up, building and running your chain.
 
 <!-- markdownlint-disable MD033 -->
 <script setup>
@@ -24,7 +24,7 @@ import constants from '../.vitepress/constants/constants.js'
 
 ## Setup your local DA network {#setup-local-da}
 
-Your local DA network is already running if you followed the [quick start guide](/docs/guides/quick-start.md) or the [build a chain](/docs/guides/gm-world.md). If not, you can start it with the following command:
+Your local DA network is already running if you followed the [quick start guide](./quick-start.md) or the [build a chain](./gm-world.md). If not, you can start it with the following command:
 
 ```bash
 curl -sSL https://ev.xyz/install-local-da.sh | bash -s {{constants.evolveLatestTag}}
diff --git a/docs/learn/about.md b/docs/learn/about.md
@@ -90,6 +90,6 @@ As of today, Evolve provides a single sequencer, an execution interface (Engine
 
 We're currently working on implementing many new and exciting features such as light nodes and state fraud proofs.
 
-Head down to the next section to learn more about what's coming for Evolve. If you're ready to start building, you can skip to the [Guides](/docs/guides/quick-start.md) section.
+Head down to the next section to learn more about what's coming for Evolve. If you're ready to start building, you can skip to the [Guides](../guides/quick-start.md) section.
 
 Spoiler alert, whichever you choose, it's going to be a great rabbit hole\!
diff --git a/docs/learn/config.md b/docs/learn/config.md
@@ -5,7 +5,7 @@ This document provides a comprehensive reference for all configuration options a
 ## Table of Contents
 
 - [DA-Only Sync Mode](#da-only-sync-mode)
-- [Introduction to Configurations](#introduction-to-configurations)
+- [Introduction to Configurations](#configs)
 - [Base Configuration](#base-configuration)
   - [Root Directory](#root-directory)
   - [Database Path](#database-path)
@@ -641,7 +641,7 @@ rpc:
 *Default:* `false`
 *Constant:* `FlagRPCEnableDAVisualization`
 
-See the [DA Visualizer Guide](/guides/da-visualizer.md) for detailed information on using this feature.
+See the [DA Visualizer Guide](../guides/da/da-visualizer.md) for detailed information on using this feature.
 
 ## Instrumentation Configuration (`instrumentation`)
 
@@ -677,7 +677,7 @@ instrumentation:
 **Description:**
 The network address (host:port) where the Prometheus metrics server will listen for scraping requests.
 
-See [Metrics](/docs/guides/metrics.md) for more details on what metrics are exposed.
+See [Metrics](../guides/metrics.md) for more details on what metrics are exposed.
 
 **YAML:**
 
diff --git a/docs/learn/data-availability.md b/docs/learn/data-availability.md
@@ -28,6 +28,6 @@ Evolve is designed to be DA-agnostic, meaning it can integrate with different da
 
 ## Learn More
 
-- [Set up a local DA](/docs/guides/da/local-da.md)
-- [Set up Celestia DA](/docs/guides/da/celestia-da.md)
+- [Set up a local DA](./guides/da/local-da.md)
+- [Set up Celestia DA](./guides/da/celestia-da.md)
 - [Celestia Docs](https://docs.celestia.org/)
diff --git a/docs/learn/sequencing/overview.md b/docs/learn/sequencing/overview.md
@@ -41,4 +41,4 @@ It mainly consists of:
 An implementation of the sequencing interface mainly acts as a middleware that connects Evolve chain and the sequencing layer. It implements the sequencing interface functions described above.
 There are several implementations of the sequencer but for now only one is available in Evolve.
 
-* [single-sequencer](/docs/learn/sequencing/single.md) - The simplest and most widely used sequencing model, where a single node (the sequencer) is responsible for ordering transactions and producing blocks.
+* [single-sequencer](./single.md) - The simplest and most widely used sequencing model, where a single node (the sequencer) is responsible for ordering transactions and producing blocks.
diff --git a/docs/learn/specs/block-manager.md b/docs/learn/specs/block-manager.md
diff --git a/docs/learn/specs/overview.md b/docs/learn/specs/overview.md
diff --git a/docs/learn/specs/template.md b/docs/learn/specs/template.md
