Skip to content

Batcher update #80

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
MadelineAu wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Batcher update #80

Show file tree
Hide file tree
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
e27a61d
WIP
MadelineAu Jul 14, 2025
29ef686
Updated for proxy v2
MadelineAu Jul 14, 2025
7e947fc
Updated for v2
MadelineAu Jul 15, 2025
3f4bc51
review rework
MadelineAu Jul 21, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/products/eigenda/integrations-guides/eigenda-proxy/eigenda-proxy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -34,14 +34,14 @@ Reference this [Quick Start](../quick-start/v2/index.md) to setup payments for y
Different security measures and runtime optimizations can be applied through various proxy configurations. The different configuration flags can be found [here](https://github.com/Layr-Labs/eigenda-proxy/blob/main/docs/help_out.txt). The following recommendations are advised for different rollup node actor types:

### Batchers
Privileged roles that are responsible for submitting rollup batches to EigenDA should have the following presets:
- Certificate verification enabled. If the rollup (stage = 0) doesn't verify DA certs against the `EigenDAServiceManager` for writing then a `ETH_CONFIRMATION_DEPTH` should be reasonably set (i.e, >= 6). Otherwise, a certificate could be submitted to the sequencer's inbox using an EigenDA blob batch header which is reorged from Ethereum.
Privileged roles that are responsible for submitting rollup batches to EigenDA.

Use the `eigenda.v2.cert-verifier-router-or-immutable-verifier-addr` option to specify the address of either the `EigenDACertVerifierRouter`
or immutable `EigenDACertVerifier` contract. Required for performing `eth_call` to verify EigenDA certificates.
Copy link
Contributor

@samlaf samlaf Jul 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
or immutable `EigenDACertVerifier` contract. Required for performing `eth_call` to verify EigenDA certificates.
or immutable `EigenDACertVerifier` contract. Required for building the correct versioned cert, as well as performing `eth_call` to verify the constructed EigenDA certificates before returning them.


### Bridge Validators
Validators that are responsible for defending or progressing a child --> parent chain withdraw bridge should be configured with the following:
- Certificate verification enabled
- Read fallback configured with a secondary backed to ensure blobs can be read in the event of EigenDA retrieval failure

### Permissionless Verifiers
- Certificate verification enabled
- Use of a cached backend provider which ensures data read from EigenDA is only done once
Binary file modified static/img/integrations/proxy/proxy-v2.png
View file
Open in desktop
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.