update docs

Author: tac0turtle

docs/guides/da/celestia-da.md

@@ -102,20 +102,18 @@ The output of the command above will look similar to this:
  Your DA AUTH_TOKEN is eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJBbGxvdyI6WyJwdWJsaWMiLCJyZWFkIiwid3JpdGUiXX0.cSrJjpfUdTNFtzGho69V0D_8kyECn9Mzv8ghJSpKRDE
 ```
 
-Next, let's set up the namespace to be used for posting data on Celestia:
+Next, let's set up the namespace to be used for posting data on Celestia. Evolve supports separate namespaces for headers and data, but for simplicity, we'll use a single namespace for both:
 
 ```bash
-DA_NAMESPACE=00000000000000000000000000000000000000000008e5f679bf7116cb
+DA_NAMESPACE="fancy_namespace"
 ```
 
-:::tip
-`00000000000000000000000000000000000000000008e5f679bf7116cb` is a default namespace for Mocha testnet. You can set your own by using a command similar to this (or, you could get creative 😎):
 
-```bash
-openssl rand -hex 10
-```
+**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
 
-Replace the last 20 characters (10 bytes) in `00000000000000000000000000000000000000000008e5f679bf7116cb` with the newly generated 10 bytes.
+The namespace values are automatically encoded by the node to ensure compatibility with Celestia.
 
 [Learn more about namespaces](https://docs.celestia.org/tutorials/node-tutorial#namespaces).
 :::
@@ -135,7 +133,8 @@ Finally, let's initiate the chain node with all the flags:
 gmd start \
     --evolve.node.aggregator \
     --evolve.da.auth_token $AUTH_TOKEN \
-    --evolve.da.namespace $DA_NAMESPACE \
+    --evolve.da.header_namespace $DA_NAMESPACE \
+    --evolve.da.data_namespace $DA_NAMESPACE \
     --evolve.da.start_height $DA_BLOCK_HEIGHT \
     --evolve.da.address $DA_ADDRESS
 ```

docs/guides/deploy/testnet.md

@@ -248,7 +248,7 @@ Both sequencer and full node Evolve services need to communicate with the celest
 #### 🔑 Common Integration Points
 
 1. **Authentication**: Evolve requires an auth token generated by the celestia-node so that Evolve can send transactions on its behalf. Both sequencer and full node types use these JWT tokens for secure communication with celestia-node
-2. **Namespace Isolation**: Data is organized using Celestia namespaces
+2. **Namespace Isolation**: Data is organized using Celestia namespaces (automatically encoded by the node for proper formatting)
 3. **API Endpoints**: Both sequencer and full nodes use the same celestia-node API interface
 4. **Network Configuration**: All nodes must be configured to connect to the same Celestia network
 

docs/learn/config.md

@@ -25,6 +25,8 @@ This document provides a comprehensive reference for all configuration options a
   - [DA Gas Multiplier](#da-gas-multiplier)
   - [DA Submit Options](#da-submit-options)
   - [DA Namespace](#da-namespace)
+  - [DA Header Namespace](#da-header-namespace)
+  - [DA Data Namespace](#da-data-namespace)
   - [DA Block Time](#da-block-time)
   - [DA Start Height](#da-start-height)
   - [DA Mempool TTL](#da-mempool-ttl)
@@ -395,19 +397,57 @@ da:
 **Description:**
 The namespace ID used when submitting blobs (block data) to the DA layer. This helps segregate data from different chains or applications on a shared DA layer.
 
+**Note:** This configuration is deprecated in favor of separate header and data namespaces (see below). If only `namespace` is provided, it will be used for both headers and data for backward compatibility.
+
 **YAML:**
 
 ```yaml
 da:
-  namespace: "MY_UNIQUE_NAMESPACE_ID"
+  namespace: "MY_UNIQUE_NAMESPACE_ID"  # Deprecated - use header_namespace and data_namespace instead
 ```
 
 **Command-line Flag:**
 `--rollkit.da.namespace <string>`
 *Example:* `--rollkit.da.namespace 0x1234567890abcdef`
-*Default:* `""` (empty, must be configured)
+*Default:* `""` (empty)
 *Constant:* `FlagDANamespace`
 
+### DA Header Namespace
+
+**Description:**
+The namespace ID specifically for submitting block headers to the DA layer. Headers are submitted separately from transaction data. The namespace value is encoded by the node to ensure proper formatting and compatibility with the DA layer.
+
+**YAML:**
+
+```yaml
+da:
+  header_namespace: "HEADER_NAMESPACE_ID"
+```
+
+**Command-line Flag:**
+`--rollkit.da.header_namespace <string>`
+*Example:* `--rollkit.da.header_namespace my_header_namespace`
+*Default:* Falls back to `namespace` if not set
+*Constant:* `FlagDAHeaderNamespace`
+
+### DA Data Namespace
+
+**Description:**
+The namespace ID specifically for submitting transaction data to the DA layer. Transaction data is submitted separately from headers, enabling nodes to sync only the data they need. The namespace value is encoded by the node to ensure proper formatting and compatibility with the DA layer.
+
+**YAML:**
+
+```yaml
+da:
+  data_namespace: "DATA_NAMESPACE_ID"
+```
+
+**Command-line Flag:**
+`--rollkit.da.data_namespace <string>`
+*Example:* `--rollkit.da.data_namespace my_data_namespace`
+*Default:* Falls back to `namespace` if not set
+*Constant:* `FlagDADataNamespace`
+
 ### DA Block Time
 
 **Description:**

docs/learn/specs/block-manager.md

@@ -121,8 +121,8 @@ Block manager configuration options:
 |GasPrice|float64|gas price for DA submissions (-1 for automatic/default)|
 |GasMultiplier|float64|multiplier for gas price on DA submission retries (default: 1.3)|
 |Namespace|da.Namespace|DA namespace ID for block submissions (deprecated, use HeaderNamespace and DataNamespace instead)|
-|HeaderNamespace|string|namespace ID for submitting headers to DA layer|
-|DataNamespace|string|namespace ID for submitting data to DA layer|
+|HeaderNamespace|string|namespace ID for submitting headers to DA layer (automatically encoded by the node)|
+|DataNamespace|string|namespace ID for submitting data to DA layer (automatically encoded by the node)|
 
 ### Block Production
 

docs/src/openapi-rpc.json

@@ -680,20 +680,20 @@
       },
       "GetNamespaceResponse": {
         "type": "object",
-        "description": "Response containing namespace configuration",
+        "description": "Response containing namespace configuration. Namespaces are encoded by the node to ensure proper formatting and compatibility with the DA layer.",
         "required": [
           "header_namespace",
           "data_namespace"
         ],
         "properties": {
           "header_namespace": {
             "type": "string",
-            "description": "The namespace identifier for block headers",
+            "description": "The namespace identifier for block headers. This namespace is used exclusively for storing and retrieving block header data on the DA layer. The value is pre-encoded by the node.",
             "example": "0x01234567890abcdef"
           },
           "data_namespace": {
             "type": "string",
-            "description": "The namespace identifier for block data",
+            "description": "The namespace identifier for block data (transactions). This namespace is used exclusively for storing and retrieving transaction data on the DA layer, separate from headers. The value is pre-encoded by the node.",
             "example": "0xfedcba9876543210"
           }
         }