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.
Rationale
Ethereum fragmentation via L2 sequencing silos has arguably been a primary cause of ETH’s divergence from BTC since the significant rise of L2s in the last two years. This is because the value of transactions at the L2 layer has devalued the value of the L1; in other words, we currently risk the market taking the L1 layer for granted, which would create an existential threat to the proof of stake consensus system. Thus, this proposal suggests that new ERCs should be required to state whether and how they align with the goal of Shared Sequencing/Universal Synchronous Composability. Such mandatory statements during the ERC proposal process can assist both editors and Core Devs with the review of new ERCs in relation to the Ethereum roadmap.
Summary of changes:
Notes:
type: Meta
is currently EIP-1. EIPs have made more heavy use of Meta documents than ERCs, with 36 Meta EIPs so far. Therefore, this change is proposed to EIP-1 instead of introducing a new Meta ERC.other
as a possible value for thesequencing
header is considered suboptimal, but was included to future-proof the proposal in the case that other sequencing solutions beyondbased
andshared
become available. Alternatives to this approach would be very welcome.Dependencies: