Skip to content
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

eibc client should be able to validate each rollapp against an rpc #1

Open
omritoptix opened this issue Apr 25, 2024 · 0 comments
Open
Assignees

Comments

@omritoptix
Copy link
Contributor

omritoptix commented Apr 25, 2024

The order client should have 2 modes: trust and verify.

by default the mode should be verify where the order client should be able to get trusted states from a full node.

The verify should have multiple levels based on the risk apetite (requires more research but in essence):

  1. p2p - fulfill after p2p block has arrived (prone to double signing attack)
  2. da - fulfill after da block has arrived (prone to fraud proof as the sequencer may still write a wrong state commitment which will require a rollback )
  3. settlement - fulfill after settlement commitment has been written. in this case we know the state the sequencer committed + the da block, hence if its correct it's not subject to rollback.

names for UI etc should be adjusted.

This requires obviously further research but this is the gist as I see it.

@omritoptix omritoptix changed the title Order client should be able to validate state against a full node eibc client should be able to validate state against a full node May 22, 2024
@omritoptix omritoptix changed the title eibc client should be able to validate state against a full node eibc client should be able to validate state against a full node - Impl Jun 12, 2024
@omritoptix omritoptix changed the title eibc client should be able to validate state against a full node - Impl eibc client should be able to validate each rollapp against an rpc Sep 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants