docs: message-passing groups current goals and status #13
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Joxess
reviewed
Feb 13, 2025
| Reasoning: | ||
| * Both L2 <> L2 messaging and L1 <> L2 messaging are core use cases. If we want to create a unified developer experience, the interface needs to support both using the same abstractions. | ||
| * L3 <> L2 messaging is a less common use case, but should be supported. | ||
| * Key Question: Should it be an explicit goal of this interface to support L1 <> L1 messaging? |
There was a problem hiding this comment.
Ideally, it makes total sense to support L1 <> L1 since we have already stated the interface should be proof, protocol, and VM agnostic. This would require incorporating feedback from those interested in it; I would leave it as a nice-to-have
0xteddybear
reviewed
Feb 14, 2025
| * Should the interface be pull or push-based? | ||
| * Should the interface use Ethereum specific addresses? | ||
| * Should the interface defined specific message formats for specific use cases? | ||
| * Should the interface use 7786-style attributes |
There was a problem hiding this comment.
nit: missing question mark
|
|
||
| ### Timeline: | ||
| * 2/17/2025: Core contibutors identified. | ||
| * 2/24/2025: Agreement on goals has been reached among core contributors, broader group feedback welcome. |
There was a problem hiding this comment.
nit: consider using ISO-8601 dates
| 3. Identifying core contributors to move this consensus forward quickly. We will ask for feedback from the broader group periodically. | ||
| 4. Establishing commitments and timelines from core projects to implement the interface once it is finalized. | ||
|
|
||
| ### Timeline: |
There was a problem hiding this comment.
just to see if I should be following something else to stay in the loop: are the deliverables on this deadline going to be contained in this document? only linked from here? or tracked somewhere else entirely
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR adds a doc page formalizing the Message Passing Working Group goals and progress. This will be the living doc the group references for all decisions made by the group.