ethereum-optimism / ethereum-optimism/optimism

op-batcher [altda]: allow configurable multiple frames

Open
#18,508 0 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

**Is your feature request related to a problem? Please describe.**

altda rollups have higher throughput than ethereum but are constrained by channel limits originally set based on ethereum.

One such limit is number of frames in a channel. Multiple frames are enabled in blob data mode, but this feature is not available to altda mode.

**Describe the solution you'd like**

It would be ideal to have a `MultiFrame` mode similar to `UseBlobs` configuration option, but which is also available in altda mode.

`op-batcher` channel options CLI flags can be updated to add `MultiFrame` configuration option which instructs `Channel.HasTxData` and `ChannelConfig.MaxFramesPerTx` to return multiple frames. Additional sanity checks for frame size should be updated to reference `l.ChannelConfig.TargetNumFrames` instead.

**Describe alternatives you've considered**

**Additional context**

Potential fix: https://github.com/celestiaorg/optimism/pull/439

Contributor guide

Open the contributing guide

Research direction

Start at the op-batcher channel-options CLI flags and trace the existing UseBlobs configuration through Channel.HasTxData and ChannelConfig.MaxFramesPerTx. Compare the altda and blob-data paths, then update the frame-size sanity checks to use l.ChannelConfig.TargetNumFrames; done means MultiFrame is configurable for altda without breaking existing channel modes.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend, cli
Issue type
Feature
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.