diff --git a/docs/products/eigenda/integrations-guides/rollup-guides/op-stack/README.md b/docs/products/eigenda/integrations-guides/rollup-guides/op-stack/README.md index 21ec9400..9ecdb65e 100644 --- a/docs/products/eigenda/integrations-guides/rollup-guides/op-stack/README.md +++ b/docs/products/eigenda/integrations-guides/rollup-guides/op-stack/README.md @@ -113,7 +113,7 @@ 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. +EigenDA V2 dispersals p50 latency is <10 seconds, 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.
diff --git a/docs/products/eigenda/networks/mainnet-beta.md b/docs/products/eigenda/networks/mainnet-beta.md new file mode 100644 index 00000000..e05ddd76 --- /dev/null +++ b/docs/products/eigenda/networks/mainnet-beta.md @@ -0,0 +1,46 @@ +--- +sidebar_position: 4 +--- + +# Mainnet Beta + +The EigenDA Mainnet Beta is a beta version of EigenDA network for functional and load testing. This environment is set up as a separate AVS on mainnet and targeted for registered mainnet operators only. No rollup integrations can be made on Mainnet Beta, and only V2 (Blazar) mode is supported. + +:::important +To reuse existing stake, operators should use the same ECDSA key from mainnet but **must** generate a new BLS key. +::: + +Please refer to [this guide](https://github.com/Layr-Labs/eigenda-operator-setup/tree/master/mainnet-beta#mainnet-beta-specific-instructions--requirements) for additional steps for setting up a validator on Mainnet Beta. + +## Quick Links + +* [AVS Page][1] +* Blob Explorer Blazar (V2): coming soon + +## Specs + +| Property | Value | +| --- | --- | +| DataAPI Address | `dataapi-mainnet-beta.eigenda.xyz` | +| Churner Address | `churner-mainnet-beta.eigenda.xyz:443` | +| Batch Dispersal Interval | Every 1 second (may vary based on network health) | +| Min Blob Size | 128 KiB | +| Max Blob Size | 16 MiB | + +## Contract Addresses + +| Contract | Address | +| --- | --- | +| EigenDAServiceManager | [0xd314209cE0ae9aDfD7643BB9d8becD62290D826a](https://etherscan.io/address/0xd314209cE0ae9aDfD7643BB9d8becD62290D826a) | +| BLSOperatorStateRetriever | [0x9E874193D8d500371bE151f2Bb8512Fc48a1f5aa](https://etherscan.io/address/0x9E874193D8d500371bE151f2Bb8512Fc48a1f5aa) | +| CertVerifier | [0x9D901Ea8971287294b417277c6176fE8172Fec6F](https://etherscan.io/address/0x9D901Ea8971287294b417277c6176fE8172Fec6F) | + + +## Quorums + +| Quorum Number | Token | +| --- | --- | +| 0 | ETH, LSTs | +| 1 | [EIGEN](https://etherscan.io/address/0xec53bF9167f50cDEB3Ae105f56099aaaB9061F83) | + +[1]: https://app.eigenlayer.xyz/avs/0xd314209ce0ae9adfd7643bb9d8becd62290d826a \ No newline at end of file diff --git a/docs/products/eigenda/operator-guides/overview.md b/docs/products/eigenda/operator-guides/overview.md index 5b1e3416..e7e372cb 100644 --- a/docs/products/eigenda/operator-guides/overview.md +++ b/docs/products/eigenda/operator-guides/overview.md @@ -20,3 +20,9 @@ Start by understanding the [Requirements](requirements/requirements-overview.md) EigenDA is in a state of active development. Operators must make sure to listen for [node software updates](./upgrades/software-upgrades/) in the correct channels and to implement these upgrades promptly. +## Testing Environments +We have two environments for operators for testing: Holesky testnet and Mainnet Beta. Mainnet Beta is intended for active mainnet operators to participate in isolated throughput validation. If you are _not_ a mainnet validator, there is no benefit to joining mainnet beta. + +[Holesky Testnet](../networks/holesky.md): reserved for functional testing. Test traffic will be kept minimal. + +[Mainnet Beta](../networks/mainnet-beta.md): reserved for isolated mainnet throughput validation. Operators are expected to provision high network bandwidth and large performant storage. Due to potential cost associated with provisioning for large traffic, participation _may_ be incentivized. \ No newline at end of file diff --git a/docs/products/eigenda/operator-guides/run-a-node/run-overview.md b/docs/products/eigenda/operator-guides/run-a-node/run-overview.md index 5e106b6f..df20f399 100644 --- a/docs/products/eigenda/operator-guides/run-a-node/run-overview.md +++ b/docs/products/eigenda/operator-guides/run-a-node/run-overview.md @@ -9,6 +9,10 @@ If you are able to satisfy all of the [eligibility requirements](../requirements Before registering as an operator for EigenDA, operators should [register as an operator with EigenLayer](https://docs.eigenlayer.xyz/operator-guides/operator-installation). This process will allow the operator to securely create BLS and ECDSA keys that will be needed during the DA node configuration steps outlined below. ::: +:::warning +When running validator nodes in multiple environments, ensure that each environment uses a different [BLS key](https://docs.eigencloud.xyz/products/eigenlayer/operators/howto/operator-installation#create-keys). +::: + Running an operator node consists of a few main steps: 1. Setting up the system environment and configuring the node (covered in [run with docker](run-with-docker.mdx)) 2. Starting the node software and confirming basic operation (covered in [run with docker](run-with-docker.mdx)