chore: fix documentation guides

docs/guides/create-genesis.md

@@ -113,7 +113,7 @@ Finally, start the chain with your start command.
 For example, start the simple ignite chain with the following command:
 
 ```sh
-gmd start --evolve.node.aggregator
+gmd start --evnode.node.aggregator
 ```
 
 ## Summary

docs/guides/da/celestia-da.md

@@ -52,12 +52,12 @@ After successfully starting a light node, it's time to start posting the batches
 
 Now that we are posting to the Celestia DA instead of the local DA, the `evolve start` command requires three DA configuration flags:
 
-- `--evolve.da.start_height`
-- `--evolve.da.auth_token`
-- `--evolve.da.namespace`
+- `--evnode.da.start_height`
+- `--evnode.da.auth_token`
+- `--evnode.da.namespace`
 
 :::tip
-Optionally, you could also set the `--evolve.da.block_time` flag. This should be set to the finality time of the DA layer, not its actual block time, as Evolve does not handle reorganization logic. The default value is 15 seconds.
+Optionally, you could also set the `--evnode.da.block_time` flag. This should be set to the finality time of the DA layer, not its actual block time, as Evolve does not handle reorganization logic. The default value is 15 seconds.
 :::
 
 Let's determine which values to provide for each of them.
@@ -110,8 +110,8 @@ DA_NAMESPACE="fancy_namespace"
 
 **Advanced Configuration:** For production deployments, you can use separate namespaces for headers and data to optimize syncing:
 
-- `--evolve.da.header_namespace` for block headers
-- `--evolve.da.data_namespace` for transaction data
+- `--evnode.da.header_namespace` for block headers
+- `--evnode.da.data_namespace` for transaction data
 
 The namespace values are automatically encoded by the node to ensure compatibility with Celestia.
 
@@ -131,12 +131,12 @@ Finally, let's initiate the chain node with all the flags:
 
 ```bash
 gmd start \
-    --evolve.node.aggregator \
-    --evolve.da.auth_token $AUTH_TOKEN \
-    --evolve.da.header_namespace $DA_NAMESPACE \
-    --evolve.da.data_namespace $DA_NAMESPACE \
-    --evolve.da.start_height $DA_BLOCK_HEIGHT \
-    --evolve.da.address $DA_ADDRESS
+    --evnode.node.aggregator \
+    --evnode.da.auth_token $AUTH_TOKEN \
+    --evnode.da.header_namespace $DA_NAMESPACE \
+    --evnode.da.data_namespace $DA_NAMESPACE \
+    --evnode.da.start_height $DA_BLOCK_HEIGHT \
+    --evnode.da.address $DA_ADDRESS
 ```
 
 Now, the chain is running and posting blocks (aggregated in batches) to Celestia. You can view your chain by using your namespace or account on one of Celestia's block explorers.

docs/guides/da/local-da.md

@@ -15,15 +15,18 @@ Before proceeding, ensure that you have completed the [build a chain](/docs/guid
 
 To set up a local DA network node on your machine, run the following script to install and start the local DA node:
 
-```bash-vue
-curl -sSL https://ev.xyz/install-local-da.sh | bash -s {{constants.localDALatestTag}}
+```bash
+git clone  --depth=1 --branch v1.0.0-beta.2 https://github.com/evstack/ev-node.git
+cd ev-node 
+make build-da
+./build/local-da
 ```
 
 This script will build and run the node, which will then listen on port `7980`.
 
 ## Configuring your chain to connect to the local DA network
 
-To connect your chain to the local DA network, you need to pass the `--evolve.da.address` flag with the local DA node address.
+To connect your chain to the local DA network, you need to pass the `--evnode.da.address` flag with the local DA node address.
 
 ## Run your chain
 
@@ -32,13 +35,13 @@ Start your chain node with the following command, ensuring to include the DA add
 ::: code-group
 
 ```sh [Quick Start]
-{BINARY} start --evolve.da.address http://localhost:7980
+testapp start --evnode.da.address http://localhost:7980
 ```
 
 ```sh [gm-world Chain]
-{BINARY} start \
-    --evolve.node.aggregator \
-    --evolve.da.address http://localhost:7980 \
+gmd start \
+    --evnode.node.aggregator \
+    --evnode.da.address http://localhost:7980 \
 ```
 
 :::

docs/guides/deploy/local.md

@@ -106,7 +106,7 @@ COPY --from=base /root/.gm /root/.gm
 # CMD tail -f /dev/null
 
 ENTRYPOINT ["gmd"]
-CMD ["start","--evolve.node.aggregator"]
+CMD ["start","--evnode.node.aggregator"]
 ```
 
 This Dockerfile sets up the environment to build the chain and run the gm-world node. It then sets up the runtime environment to run the chain. This allows you as the developer to modify any files, and then simply rebuild the Docker image to run the new chain.
@@ -156,8 +156,8 @@ services:
     command:
       [
         "start",
-        "--evolve.node.aggregator",
-        "--evolve.da.address",
+        "--evnode.node.aggregator",
+        "--evnode.da.address",
         "http://0.0.0.0:7980",
       ]
     # Ensures the local-da service is up and running before starting the chain

docs/guides/deploy/testnet.md

@@ -170,15 +170,15 @@ The two services work together through well-defined interfaces:
 The single sequencer node runs both RETH and EVOLVE services with specific settings:
 
 - **RETH**: Configured to accept blocks from the Evolve sequencer
-- **EVOLVE**: Configured with `--evolve.node.aggregator=true` to enable block production
+- **EVOLVE**: Configured with `--evnode.node.aggregator=true` to enable block production
 - **Role**: Produces blocks, orders transactions, posts to DA layer
 
 ### 📡 Full Node Configuration
 
 Each full node also runs both RETH and EVOLVE services but in sync mode:
 
 - **RETH**: Configured to process blocks received from the network
-- **EVOLVE**: Configured with `--evolve.node.aggregator=false` to sync from the sequencer
+- **EVOLVE**: Configured with `--evnode.node.aggregator=false` to sync from the sequencer
 - **Role**: Syncs blocks, serves queries, provides redundancy
 
 ### 🔑 Key Integration Points
@@ -196,14 +196,14 @@ You can customize timing parameters for your chain. While there are many configu
 
 #### 🎯 Sequencer Block Time
 
-- **Flag**: `--evolve.node.block_time`
+- **Flag**: `--evnode.node.block_time`
 - **Default**: 1s (1 block per second)
 - **Purpose**: Controls how frequently the sequencer produces new blocks
 - **Customization**: Can be adjusted based on throughput requirements and latency preferences
 
 #### 📊 Data Availability Block Time
 
-- **Flag**: `--evolve.da.block_time`
+- **Flag**: `--evnode.da.block_time`
 - **Default**: 6s
 - **Purpose**: Controls how frequently blobs are posted to the Celestia chain
 - **Function**: Each 6 seconds (by default), batched block data is submitted to Celestia for data availability

docs/guides/evm/single.md

@@ -72,7 +72,7 @@ The JWT secret is typically located at `ev-node/execution/evm/docker/jwttoken/jw
 
 ```bash
 cd build
-./evm-single init --evolve.node.aggregator=true --evolve.signer.passphrase secret
+./evm-single init --evnode.node.aggregator=true --evnode.signer.passphrase secret
 ```
 
 ### 2. Start the Sequencer
@@ -81,9 +81,9 @@ cd build
 ./evm-single start \
   --evm.jwt-secret $(cat /path/to/ev-node/execution/evm/docker/jwttoken/jwt.hex) \
   --evm.genesis-hash 0x0a962a0d163416829894c89cb604ae422323bcdf02d7ea08b94d68d3e026a380 \
-  --evolve.node.block_time 1s \
-  --evolve.node.aggregator=true \
-  --evolve.signer.passphrase secret
+  --evnode.node.block_time 1s \
+  --evnode.node.aggregator=true \
+  --evnode.signer.passphrase secret
 ```
 
 Replace `/path/to/` with the actual path to your ev-node repository.
@@ -121,9 +121,9 @@ INF listening on address=/ip4/127.0.0.1/tcp/26659/p2p/12D3KooWXXXXXXXXXXXXXXXXXX
   --home ~/.evolve/evm-single-fullnode \
   --evm.jwt-secret $(cat /path/to/ev-node/execution/evm/docker/jwttoken/jwt.hex) \
   --evm.genesis-hash 0x0a962a0d163416829894c89cb604ae422323bcdf02d7ea08b94d68d3e026a380 \
-  --evolve.node.block_time 1s \
-  --evolve.node.aggregator=false \
-  --evolve.p2p.peers <SEQUENCER_P2P_ID>@127.0.0.1:26659
+  --evnode.node.block_time 1s \
+  --evnode.node.aggregator=false \
+  --evnode.p2p.peers <SEQUENCER_P2P_ID>@127.0.0.1:26659
 ```
 
 Replace `<SEQUENCER_P2P_ID>` with the actual P2P ID from your sequencer's logs.
@@ -142,9 +142,9 @@ INF block marked as DA included blockHash=XXXX blockHeight=XX module=BlockManage
 
 | Flag | Description |
 |------|-------------|
-| `--evolve.node.aggregator` | Set to true for sequencer mode, false for full node |
-| `--evolve.signer.passphrase` | Passphrase for the signer |
-| `--evolve.node.block_time` | Block time for the Evolve node |
+| `--evnode.node.aggregator` | Set to true for sequencer mode, false for full node |
+| `--evnode.signer.passphrase` | Passphrase for the signer |
+| `--evnode.node.block_time` | Block time for the Evolve node |
 
 ### EVM Flags
 

docs/guides/full-node.md

@@ -66,7 +66,7 @@ Run your full node with the following command:
 
 ```bash
 gmd start \
-  --evolve.da.address http://127.0.0.1:7980 \
+  --evnode.da.address http://127.0.0.1:7980 \
   --p2p.seeds $P2P_ID@127.0.0.1:7676 \
   --minimum-gas-prices 0stake \
   --rpc.laddr tcp://127.0.0.1:46657 \

docs/guides/gm-world.md

@@ -39,15 +39,15 @@ ignite version
 ```
 
 ```bash
-Ignite CLI version:             v29.2.0-dev
+Ignite CLI version:             v29.3.1-dev
 Ignite CLI build date:          undefined
 Ignite CLI source hash:         undefined
 Ignite CLI config version:      v1
-Cosmos SDK version:             v0.53.0
+Cosmos SDK version:             v0.53.3
 Buf.build version:              undefined
 Your OS:                        darwin
 Your arch:                      arm64
-Your go version:                go version go1.24.3 darwin/arm64
+Your go version:                go version go1.25.0 darwin/arm64
 ```
 
 ## Generate your App {#generate-your-app}
@@ -104,7 +104,10 @@ Now that we have our gm app generated and installed, we can launch our GM chain
 First lets start the local DA network:
 
 ```bash
-curl -sSL https://ev.xyz/install-local-da.sh | bash -s {{constants.evolveLatestTag}}
+git clone  --depth=1 --branch v1.0.0-beta.2 https://github.com/evstack/ev-node.git
+cd ev-node 
+make build-da
+./build/local-da
 ```
 
 you should see logs like:
@@ -118,7 +121,7 @@ you should see logs like:
 After which we can start the app:
 
 ```bash
-gmd start --evolve.node.aggregator
+gmd start --evnode.node.aggregator
 ```
 
 You should see an output like this:

docs/guides/quick-start.md

@@ -39,16 +39,16 @@ testapp version
 A successful installation will display the version number and its associated git commit hash.
 
 ```bash
-evolve version:  execution/evm/v1.0.0-beta.1
-evolve git sha:  cd1970de
+evolve version:  v1.0.0-beta.2
+evolve git sha:  d096a24e
 ```
 
 ## 🗂️ Initialize a evolve network node
 
 To initialize a evolve network node, execute the following command:
 
 ```bash
-testapp init --evolve.node.aggregator --evolve.signer.passphrase secret
+testapp init --evnode.node.aggregator --evnode.signer.passphrase secret
 ```
 
 ## 🚀 Run your evolve network node
@@ -61,8 +61,10 @@ First lets start the local DA network:
 # If you're not already in the ev-node directory
 cd ev-node
 
+# Build the local DA binary
+make build-da
 # Start the local DA network using the built binary
-./build/testapp da start
+./build/local-da
 ```
 
 You should see logs like:
@@ -76,7 +78,7 @@ You should see logs like:
 To start a basic evolve network node, execute:
 
 ```bash
-testapp start --evolve.signer.passphrase secret
+testapp start --evnode.signer.passphrase secret
 ```
 
 Upon execution, the CLI will output log entries that provide insights into the node's initialization and operation:

docs/guides/restart-chain.md

@@ -39,7 +39,7 @@ I[2024-10-17|14:52:13.845] executed block                               module=B
 I[2024-10-17|14:52:13.845] indexed block events                         module=txindex height=8
 ```
 
-It is important to include any additional flags that you used when you first started your chain. For example, if you used the `--evolve.da.namespace` flag, you will need to include that flag when restarting your chain to ensure your chain continues to publish blobs to the same namespace.
+It is important to include any additional flags that you used when you first started your chain. For example, if you used the `--evnode.da.namespace` flag, you will need to include that flag when restarting your chain to ensure your chain continues to publish blobs to the same namespace.
 
 ## Restart chain after running out of funds
 

docs/guides/use-tia-for-gas.md

@@ -35,7 +35,7 @@ curl -sSL https://ev.xyz/install-local-da.sh | bash -s {{constants.evolveLatestT
 Start the chain, posting to the local DA network:
 
 ```bash
-gmd start --evolve.node.aggregator --evolve.da.address http://localhost:7980 --minimum-gas-prices="0.02ibc/C3E53D20BC7A4CC993B17C7971F8ECD06A433C10B6A96F4C4C3714F0624C56DA,0.025stake"
+gmd start --evnode.node.aggregator --evnode.da.address http://localhost:7980 --minimum-gas-prices="0.02ibc/C3E53D20BC7A4CC993B17C7971F8ECD06A433C10B6A96F4C4C3714F0624C56DA,0.025stake"
 ```
 
 Note that we specified the gas token to be IBC TIA. We still haven't made an IBC connection to Celestia's Mocha testnet, however, if we assume our first channel will be an ICS-20 transfer channel to Celestia, we can already calculate the token denom using this formula: