-
Notifications
You must be signed in to change notification settings - Fork 5
Increase MaxFrameLen to 16 MB #228
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
Conversation
EigenDA current limit for Holesky (their documentation is currently outdated but the limit seems to be set to 16 MB based on the updated tests from [this PR](Layr-Labs/eigenda-proxy#100)).
Tested on Holesky with EigenDA as AltDA. |
// Data transactions that carry frames are generally not larger than 128 KB due to L1 network conditions, | ||
// but we leave space to grow larger anyway (gas limit allows for more data). | ||
const MaxFrameLen = 1_000_000 | ||
// For AltDA, frames size can be larger. Setting to 16 MB as current blob limit for EigenDA. | ||
const MaxFrameLen = 16_000_000 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How is the final size decided? Does that happen in the node or in the batcher?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change applies to derivation pipeline, and affects only to the limit enforced to op-node. op-batcher has a cmdflag to set the batch size limit (--max-l1-tx-size-bytes
) and this is not affected by MaxFrameLen
.
16 MB was chosen as it is currently the limit of blob size on EigenDA Holesky.
This does not mean that the frame size used is 16MB, but op-node would accept frames up to that size.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in line 88 there's a comment, which you might want to adapt as well.
// Cap frame length to MaxFrameLen (currently 1MB)
Updates DelayedWETH to use call instead of transfer because transfer only sends along 2300 gas which will cause the transfer to fail if the owner contract uses lots of gas in the fallback function. Adds tests that demonstrate that the function now works appropriately under any reasonable amount of gas usage. In theory this means the recovery function can be reentered but this isn't an issue because the function is authenticated and is recovering all of the ETH in the contract anyway.
On `celo10` branch I've observed in the batcher: ``` {"t":"2024-10-17T15:24:33.473665645Z","lvl":"crit","msg":"Application failed","message":"failed to setup: failed to init channel config: max frame size 999999 exceeds altDA max input size 130672"} ``` With previous `celo` versions this size limit was not enforced, and we increased the max frame size to 16MB in the derivation pipeline ([PR](#228)).
On `celo10` branch I've observed in the batcher: ``` {"t":"2024-10-17T15:24:33.473665645Z","lvl":"crit","msg":"Application failed","message":"failed to setup: failed to init channel config: max frame size 999999 exceeds altDA max input size 130672"} ``` With previous `celo` versions this size limit was not enforced, and we increased the max frame size to 16MB in the derivation pipeline ([PR](#228)).
EigenDA current limit for Holesky (their documentation is currently outdated but the limit seems to be set to 16 MB based on the updated tests from this PR).