Skip to content
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.

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

Update op-stack README.md with latest info for high-throughput #20

Draft
wants to merge 6 commits into
base: master
Choose a base branch
from

Conversation

samlaf
Copy link
Contributor

@samlaf samlaf commented Sep 29, 2024

No description provided.

New high-throughput configuration
Copy link

vercel bot commented Sep 29, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
eigenda-docs ✅ Ready (Inspect) Visit Preview Oct 7, 2024 5:26pm

@@ -22,7 +22,10 @@ First check out the version of the EigenDA proxy corresponding to the version of
|------------------|-----------------------|
| [v1.7.6](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.6) | [v1.0.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.0.0) |
| [v1.7.7](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.7) | [v1.2.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.2.0) |
| [v1.9.0](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.0) | [v1.4.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.4.0)
| [v1.9.0](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.0) | [v1.4.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.4.0) |
| [v1.9.3](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.3) | TODO(@bxue): make new release |
Copy link
Contributor Author

Choose a reason for hiding this comment

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

TODO for release captain @bxue-l2

Copy link

Choose a reason for hiding this comment

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

released 1.5.0

@@ -22,7 +22,10 @@ First check out the version of the EigenDA proxy corresponding to the version of
|------------------|-----------------------|
| [v1.7.6](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.6) | [v1.0.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.0.0) |
| [v1.7.7](https://github.com/ethereum-optimism/optimism/releases/tag/v1.7.7) | [v1.2.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.2.0) |
| [v1.9.0](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.0) | [v1.4.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.4.0)
| [v1.9.0](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.0) | [v1.4.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.4.0) |
| [v1.9.3](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.3) | TODO(@bxue): make new release |
Copy link

Choose a reason for hiding this comment

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

released 1.5.0

| [v1.9.0](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.0) | [v1.4.0](https://github.com/Layr-Labs/eigenda-proxy/releases/tag/v1.4.0) |
| [v1.9.3](https://github.com/ethereum-optimism/optimism/releases/tag/v1.9.3) | TODO(@bxue): make new release |

The latest v1.9.2 op-stack release does not contain our most recent concurrent batch submission [PR](https://github.com/ethereum-optimism/optimism/pull/11698), hence high-throughput chains will need to use the latest op-challenger v1.1.0 release until the op-stack v1.9.3 release.
Copy link

Choose a reason for hiding this comment

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

it is no longer latest. Are we comfortable with 1.9.3 now?

- `OP_BATCHER_ALTDA_DA_SERVICE=true`
- `OP_BATCHER_ALTDA_VERIFY_ON_READ=false`
- `OP_BATCHER_ALTDA_DA_SERVER={EIGENDA_PROXY_URL}`
- `OP_BATCHER_ALTDA_MAX_CONCURRENT_DA_REQUESTS=1500`
Copy link

Choose a reason for hiding this comment

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

Should we use the multi-frames branch, so this number isn't that crazy

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants