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.

Sign up for GitHub

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

Jump to bottom

[Feature] Interop - Message Graph #27

Open
clabby opened this issue Jan 9, 2025 · 5 comments · May be fixed by #86
Open

[Feature] Interop - Message Graph #27

clabby opened this issue Jan 9, 2025 · 5 comments · May be fixed by #86
Assignees
@refcell
Labels
A-protocol Area: protocol crate C-blocked Category: cannot move forward until something else changes C-feat Category: new feature or request H-interop Hardfork: interop

Comments

@clabby
Copy link
Contributor

clabby commented Jan 9, 2025 •
edited
Loading

Component

protocol

Describe the feature you would like

Note

During initial iteration, this type will live in kona. Once the interop proof design begins to stablize, it will be moved to maili.

The Message Graph is a representation of all Interop Messages for a set of L2 blocks within the Superchain's active dependency set.

This structure should be generic over a provider that can serve receipts / headers by BlockId, for the sake of portability between fault-proof (oracle-backed) and native (RPC-backed) environments.

The purpose of the message graph is to consume block headers, traverse their receipts for ExecutingMessages, and search for corresponding InitiatingMessages. If any ExecutingMessages are found to be invalid per message validity rules, the API should return all chain IDs with bad blocks for the consumer to process.

Additional context

No response
@clabby clabby added A-protocol Area: protocol crate C-feat Category: new feature or request labels Jan 9, 2025
@emhane emhane added the H-interop Hardfork: interop label Jan 15, 2025
@clabby
Copy link
Contributor Author

clabby commented Jan 15, 2025

https://github.com/op-rs/kona/tree/main/crates/interop

@emhane
Copy link
Member

emhane commented Jan 16, 2025

did you start this @refcell ? otherwise imma do it now

@refcell refcell self-assigned this Jan 17, 2025
@refcell refcell linked a pull request Jan 17, 2025 that will close this issue
Draft
@refcell
Copy link
Contributor

refcell commented Jan 17, 2025

Picked this up in #86

@clabby
Copy link
Contributor Author

clabby commented Jan 17, 2025

#86 (comment)

on:

During initial iteration, this type will live in kona. Once the interop proof design begins to stablize, it will be moved to maili.

Still think we should wait a bit.

@emhane emhane added the C-blocked Category: cannot move forward until something else changes label Jan 17, 2025
@emhane
Copy link
Member

emhane commented Jan 17, 2025

ok @clabby , marking as blocked

@clabby clabby mentioned this issue Jan 22, 2025
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@refcell refcell

Labels
A-protocol Area: protocol crate C-blocked Category: cannot move forward until something else changes C-feat Category: new feature or request H-interop Hardfork: interop
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(protocol): Interop Types op-rs/maili
3 participants
@clabby @refcell @emhane