Add ERC: Verifiable Cross Rollup Links #863
Open
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
SamWilsn
reviewed
Jan 27, 2025
ERCS/erc-XXXX.md
Outdated
| @@ -0,0 +1,117 @@ | |||
| --- | |||
| eip: XXXX | |||
There was a problem hiding this comment.
Suggested change
| eip: XXXX | |
| eip: 7868 |
Also rename the file and assets directories please!
notbdu
changed the title
eip-review-bot
changed the title
|
The commit c90b69f (as a parent of 7398416) contains errors. |
bomanaps
reviewed
Jan 29, 2025
|
|
||
| We propose a log and storage key identifier. Both are verifiable by cryptographically linking them to the execution results (e.g. block header) produced by communicating rollups (and the L1). The creation of either identifier creates a "cross rollup link" between the execution of the origin and the destination rollup. These cross rollup links can either be pessimistically or optimistically validated depending on the type of proof system used. | ||
|
|
||
| The `LogIdentifier` specification below borrows heavily from Optimism's [message identifier](https://github.com/ethereum-optimism/specs/blob/main/specs/interop/messaging.md#message-identifier) format. It uniquely identifies a log emitted on the origin rollup. |
There was a problem hiding this comment.
There is an issue with the link on line 42 in ERCS/erc-7868.md. To resolve this, please ensure the link is a relative link as described in the Markdown Relative Links guidelines. You can also refer to the correct method for linking external resources here: Linking to External Resources.
|
|
||
| ### Settlement | ||
|
|
||
| Rollup frameworks are then expected to use this information at settlement time to validate all cross rollup inputs. This means that we now introduce a dependency of a single rollup STF on the STF of communicating rollups in a cluster. There are two general approaches for implementing this cross rollup dependency - shared or chained settlement. |
There was a problem hiding this comment.
Could you please clarify the meaning of STF in the context of the Rollup frameworks? It would help readers understand the document better.
Feroslav268
approved these changes
Feb 15, 2025
Feroslav268
approved these changes
Feb 15, 2025
Feroslav268
approved these changes
Feb 15, 2025
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 ERC proposes a specification for verifiable cross rollup links to enable settlement time verification of cross rollup transactions across different rollup frameworks.
The goal is to enable rollups of any framework to join a cluster and have cross rollup communication within that cluster secured by the L1.