ethereum-optimism / ethereum-optimism/optimism

op-batcher [altda]: should not limit max frame size to max input size in generic mode

Open
#17,796 3 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
6.5k
Forks
4k
Avg merge
2d 15h
Merged PRs (30d)
145

Description

**Bug Description**
Exempt `op-batcher` max frame size from altDA max input size limit in generic commitment mode as per specs:

https://specs.optimism.io/experimental/alt-da.html#:~:text=exempt%20from%20this%20limit

**Steps to Reproduce**
* run op-batcher in altDA generic commitment mode

**Expected behavior**
does not throw `max frame size %d exceeds altDA max input size`

**Environment Information:**
macOS 14.1
op-batcher v1.15.0

**Configurations:**
`--altda.enabled`
`--altda.da-service`

**Additional context**

related: https://github.com/ethereum-optimism/optimism/issues/11185#issuecomment-2262601394

---

⚠️ **Notice:** Issues that do not include the following sections will be subject to closure:
- Bug Description
- Steps to Reproduce
- Environment Information

Please ensure all required sections are filled out accurately to expedite the debugging process and improve issue resolution efficiency.

Contributor guide

Open the contributing guide

Research direction

Start at the op-batcher entry point and reproduce the error with --altda.enabled and --altda.da-service in generic commitment mode. Read the linked altDA specification and trace the max frame size validation. Done means generic mode no longer rejects a frame size solely because it exceeds the altDA max input size.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
blockchain
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.