Skip to content

Add Validium Mode to the L2 #2313

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

Closed
Tracked by #2142
jrchatruc opened this issue Mar 26, 2025 · 0 comments · Fixed by #2365
Closed
Tracked by #2142

Add Validium Mode to the L2 #2313

jrchatruc opened this issue Mar 26, 2025 · 0 comments · Fixed by #2365
Assignees

Comments

@jrchatruc
Copy link
Collaborator

The L2 should be able to deploy in Validium mode, meaning the state diff is not posted to the L1 on commit transactions. This requires changing from an eip 4844 transaction to a standard EIP 1559 one.

@mpaulucci mpaulucci removed this from ethrex_l1 Apr 23, 2025
github-merge-queue bot pushed a commit that referenced this issue Apr 25, 2025
Validium is a [scaling
solution](https://ethereum.org/en/developers/docs/scaling/) that
enforces integrity of transactions using validity proofs like
[ZK-rollups](https://ethereum.org/en/developers/docs/scaling/zk-rollups/),
but doesn’t store transaction data on the Ethereum Mainnet.

**Description**
- Replace EIP 4844 transactions for EIP 1559
- Modify OnChainProposer contract so that it supports validium. It is
not the most efficient way of doing it but the simplest.
- Now the config.toml has a validium field.

Note: I'm not 100% sure about the changes that I made to the
OnChainProposer, there may be a mistake in the additions that I made. I
will review it though but I still consider worth opening this PR.


<!-- Link to issues: Resolves #111, Resolves #222 -->

Closes #2313

---------

Co-authored-by: ilitteri <[email protected]>
Co-authored-by: Ivan Litteri <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants