docs: remove V1/Blazar versioning references from EigenDA docs

mmurrs · claude · mmurrs · commit 6d8e0442dbd3 · 2026-02-16T17:27:02.000-05:00
EigenDA V1 has been fully deprecated and removed from the codebase.
This PR updates the documentation to reflect that V2 is now simply
"EigenDA" - there's no need for version qualifiers.

Changes:
- networks/mainnet.md: "Blazar (V2) Specs" → "Network Specs"
- networks/sepolia.md: "Blob Explorer Blazar (V2)" → "Blob Explorer"
- operator-guides/requirements/system-requirements.md: Remove "Blazar (V2) upgrade" reference
- integrations-guides/rollup-guides/op-stack/README.md:
  - Remove V1 Settings dropdown
  - Remove "Migrating from V1" section (no longer needed)
  - "EigenDA V2 dispersals" → "EigenDA dispersals"
  - Fix capitalization: "eigenda-powered" → "EigenDA-powered"
  - Fix env var names to match actual config file
- integrations-guides/quick-start/v2/index.md: "V2 Guide" → "Guide" in sidebar
- api/overview.md: Fix broken relative links (pre-existing bug)

Co-Authored-By: Claude Opus 4.5 &lt;noreply@anthropic.com&gt;
diff --git a/docs/eigenda/api/overview.md b/docs/eigenda/api/overview.md
@@ -18,7 +18,7 @@ The low level specification for the Disperser API is [disperser.proto](https://g
 The goal of this document is to explain this spec at a higher level.
 
 Eigen Labs hosts a disperser endpoint for each EigenDA network. These endpoints are documented in respective network pages 
-for [Mainnet](../../networks/mainnet.md) and [Sepolia](../../networks/sepolia.md).
+for [Mainnet](../networks/mainnet.md) and [Sepolia](../networks/sepolia.md).
 
 ### Disperser Endpoints
 
diff --git a/docs/eigenda/integrations-guides/quick-start/v2/index.md b/docs/eigenda/integrations-guides/quick-start/v2/index.md
@@ -1,6 +1,6 @@
 ---
 sidebar_position: 1
-title: V2 Guide
+title: Guide
 ---
 
 # EigenDA Payment and Data Dispersal Guide
diff --git a/docs/eigenda/integrations-guides/rollup-guides/op-stack/README.md b/docs/eigenda/integrations-guides/rollup-guides/op-stack/README.md
@@ -21,7 +21,7 @@ We currently maintain a [fork](https://github.com/Layr-Labs/optimism) of the OP
 
 ## Kurtosis Devnet
 
-For a quick start to explore an eigenda-powered op rollup, we [extended](https://github.com/Layr-Labs/optimism/tree/eigenda-develop/kurtosis-devnet) op's kurtosis-devnet. Start by cloning the repo and cd'ing to the correct directory:
+For a quick start to explore an EigenDA-powered OP rollup, we [extended](https://github.com/Layr-Labs/optimism/tree/eigenda-develop/kurtosis-devnet) op's kurtosis-devnet. Start by cloning the repo and cd'ing to the correct directory:
 ```bash
 git clone git@github.com:Layr-Labs/optimism.git
 cd optimism/kurtosis-devnet
@@ -44,7 +44,7 @@ $ just --list
   eigenda-devnet-test-memstore *ARGS=""              # meaning with a config file in eigenda-template-values/memstore-* .
 ```
 
-You can run `just eigenda-devnet-start` to start a devnet which will spin-up an [eigenda-proxy](../../eigenda-proxy/eigenda-proxy.md) in memstore mode, simulating EigenDA. To interact with the actual EigenDA [sepolia](../../../networks/sepolia.md) testnet, you can run `just eigenda-devnet-start "eigenda-template-values/sepolia-concurrent-small-blobs.json"`. You will need to fill in the missing secret values in that [config file](https://github.com/Layr-Labs/optimism/blob/eigenda-develop/kurtosis-devnet/eigenda-template-values/sepolia-v2-concurrent-small-blobs.json): `eigenda-proxy.secrets.eigenda.signer-private-key-hex`, `eigenda-proxy.secrets.eigenda.v2.signer-private-key-hex` and `eigenda-proxy.secrets.eigenda.eth-rpc`. Feel free to modify any other values, or even modify the kurtosis eigenda [template file](https://github.com/Layr-Labs/optimism/blob/e1d636081550caacae42d88b79404899f0e45888/kurtosis-devnet/eigenda.yaml) directly if needed.
+You can run `just eigenda-devnet-start` to start a devnet which will spin-up an [eigenda-proxy](../../eigenda-proxy/eigenda-proxy.md) in memstore mode, simulating EigenDA. To interact with the actual EigenDA [Sepolia](../../../networks/sepolia.md) testnet, you can run `just eigenda-devnet-start "eigenda-template-values/sepolia-concurrent-small-blobs.json"`. You will need to fill in the missing secret values in that [config file](https://github.com/Layr-Labs/optimism/blob/eigenda-develop/kurtosis-devnet/eigenda-template-values/sepolia-v2-concurrent-small-blobs.json): `eigenda-proxy.secrets.eigenda.signer-private-key-hex`, `eigenda-proxy.secrets.eigenda.v2.signer-payment-key-hex` and `eigenda-proxy.secrets.eigenda.eth_rpc`. Feel free to modify any other values, or even modify the kurtosis eigenda [template file](https://github.com/Layr-Labs/optimism/blob/e1d636081550caacae42d88b79404899f0e45888/kurtosis-devnet/eigenda.yaml) directly if needed.
 
 ## Deploying
 
@@ -89,9 +89,7 @@ When configuring your batch parameters, consult this [batch sizing reference](ht
 
 Please use the [eigenda-proxy](https://github.com/Layr-Labs/eigenda/tree/master/api/proxy#eigenda-proxy-) user guide for the latest information.
 
-Make sure to read the different [features](https://github.com/Layr-Labs/eigenda/tree/master/api/proxy#features-and-configuration-options-flagsenv-vars) provided by the proxy, to understand the different flag options. We provide an example [config](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example) which contains the env vars required to configure Proxy for retrieval from both EigenDA V1 and V2.
-
-If deploying proxy for an op-batcher, which means blobs will be dispersed to EigenDA, make sure to set [EIGENDA_PROXY_STORAGE_DISPERSAL_BACKEND=V2](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example#L21) to submit blobs to EigenDA V2.
+Make sure to read the different [features](https://github.com/Layr-Labs/eigenda/tree/master/api/proxy#features-and-configuration-options-flagsenv-vars) provided by the proxy, to understand the different flag options. We provide an example [config](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example) which contains the env vars required to configure the Proxy.
 
 ### Deploying OP Node
 
@@ -117,26 +115,12 @@ The following env config values should be set accordingly to ensure proper commu
 
 Each blob submitted to EigenDA consists of `OP_BATCHER_TARGET_NUM_FRAMES` number of frames, each of size `OP_BATCHER_MAX_L1_TX_SIZE_BYTES`. The above values submit blobs of ~1MiB. We advise not setting `OP_BATCHER_MAX_L1_TX_SIZE_BYTES` larger than the default in case [failover](#failover) is required, which will submit the frames directly to ethereum as calldata, so must fit in a single transaction (max 128KiB).
 
-EigenDA V2 dispersals p99 latency is ~10seconds, so in order to achieve a throughput of 1MiB/s, we set `OP_BATCHER_ALTDA_MAX_CONCURRENT_DA_REQUESTS=10` to allow 10 pipelined requests to fill those 10 seconds. 
-
-<!-- details creates a dropdown menu -->
-<details>
-<summary>EigenDA V1 Setting</summary>
-EigenDA V1, because of its blocking calls, required setting `OP_BATCHER_ALTDA_MAX_CONCURRENT_DA_REQUESTS=1320` to achieve 1MiB/s throughput. This is because blob dispersals on EigenDA V1 mainnet take ~10 mins for batching and 12 mins for Ethereum finality, which means a blob submitted to the eigenda-proxy could take up to 22 mins before returning. Thus, assuming blobs of 1MiB/s by setting `OP_BATCHER_TARGET_NUM_FRAMES=8`, in order to reach a throughput of 1MiB/s, which means 8 requests per second each blocking for possibly up to 22mins, we would need to send up to `60*22=1320` parallel requests.
-</details>
+EigenDA dispersals p99 latency is ~10seconds, so in order to achieve a throughput of 1MiB/s, we set `OP_BATCHER_ALTDA_MAX_CONCURRENT_DA_REQUESTS=10` to allow 10 pipelined requests to fill those 10 seconds.
 
 #### **Failover**
 
 Failover was added in this [PR](https://github.com/Layr-Labs/optimism/pull/34), and is automatically supported by the batcher. Each channel will first attempt to disperse to EigenDA via the proxy. If a `503` HTTP error is received, that channel will failover and be submitted as calldata to ethereum instead. To configure when the proxy returns `503` errors, see the [failover signals](https://github.com/Layr-Labs/eigenda/tree/master/api/proxy#failover-signals-) section of the Proxy README.
 
-## Migrating To EigenDA V2
-
-For [trusted](../integrations-overview.md#trusted-integration) integrations, migrating to EigenDA V2 is as simple as:
-- op-node: restarting the eigenda-proxy to support [both V1 and V2 backends](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example#L17)
-- op-batcher: restarting the eigenda-proxy to [disperse to V2](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example#L21). This will require setting a [V2_SIGNER_PRIVATE_KEY](https://github.com/Layr-Labs/eigenda/blob/master/api/proxy/.env.example#L31) with [V2 payments](../../../core-concepts/payments.md) enabled (either pay-per-blob or reserved bandwidth).
-
-Please refer to the [EigenDA Proxy README](https://github.com/Layr-Labs/eigenda/tree/master/api/proxy#eigenda-proxy-) for more details. We also have a V2 migration test on our kurtosis devnet which shows how to [swap the dispersal-backend](https://github.com/Layr-Labs/optimism/blob/89ac40d0fddba2e06854b253b9f0266f36350af2/kurtosis-devnet/tests/eigenda/v2_migration_test.go#L83) from V1 to V2 without needing to restart the proxy.
-
 ## Security Guarantees
 
 The above setup provides a [trusted integration](../integrations-overview.md#trusted-integration) level of security guarantees without adding an unnecessary trust assumption on the EigenDA disperser.
@@ -145,4 +129,4 @@ The above setup provides a [trusted integration](../integrations-overview.md#tru
 
 OP's Alt-DA spec includes a [DA challenge contract](https://specs.optimism.io/experimental/alt-da.html#data-availability-challenge-contract), which allows L2 asset-holders to prevent a data withholding attack executed by the sequencer or DA network. EigenDA does not make use of the challenge contract because not only is uploading high-throughput bandwidth onto Ethereum not physically possible, but even for low throughput rollups, the challenge contract is not economically viable. See [l2beat's analysis of the redstone rollup](https://l2beat.com/scaling/projects/redstone#da-layer-risk-analysis) or donnoh's [Universal Plasma and DA challenges](https://ethresear.ch/t/universal-plasma-and-da-challenges/18629) article for an economic analysis of the challenge contract.
 
-This means that even if our op stack fork were to implement failover to keccak commitments (currently it is only possible to failover to ethereum calldata), using the challenge contract would not provide any additional security guarantees, which is why we recommend that every eigenda-op rollup uses GenericCommitments in their [rollup.json](#deploying-op-node) config.
+This means that even if our op stack fork were to implement failover to keccak commitments (currently it is only possible to failover to ethereum calldata), using the challenge contract would not provide any additional security guarantees, which is why we recommend that every EigenDA OP rollup uses GenericCommitments in their [rollup.json](#deploying-op-node) config.
diff --git a/docs/eigenda/networks/mainnet.md b/docs/eigenda/networks/mainnet.md
@@ -9,7 +9,7 @@ sidebar_position: 1
 * [AVS Page][2]
 * [Blob Explorer][1]
 
-## Blazar (V2) Specs
+## Network Specs
 
 | Property | Value |
 | --- | --- |
diff --git a/docs/eigenda/networks/sepolia.md b/docs/eigenda/networks/sepolia.md
@@ -9,7 +9,7 @@ The EigenDA Sepolia testnet is the current EigenDA testnet for integrations.
 ## Quick Links
 
 * [AVS Page][2]
-* [Blob Explorer Blazar (V2)][1]
+* [Blob Explorer][1]
 
 ## Specs
 
diff --git a/docs/eigenda/operator-guides/requirements/system-requirements.md b/docs/eigenda/operator-guides/requirements/system-requirements.md
@@ -4,7 +4,7 @@ sidebar_position: 1
 
 # System Requirements
 
-The following system requirements apply to the **Blazar (V2) upgrade** and are critical for maintaining optimal node performance and protocol compliance.
+The following system requirements are critical for maintaining optimal node performance and protocol compliance.
 
 ## General System Requirements
 
