You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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]>
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.
The text was updated successfully, but these errors were encountered: