ECIP (draft) - Elysium Revenue Routing Destinations#569
Open
GravityLabLLC wants to merge 4 commits into
Open
Conversation
15 tasks
This was referenced Mar 13, 2026
GravityLabLLC
changed the title
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Description
Elysium Revenue Routing Destinations specifies the deterministic, protocol-owned revenue contract used by Elysium to receive redirected
BASEFEE. It defines minimal custody semantics, prioritizes auditability, and preserves strict separation between custody and downstream settlement/governance logic so non-consensus policy mechanisms can evolve independently.This is part of the Elysium upgrade which is defined here on the web in the Elysium Files:
https://logtrees.com/elysium/elysium.html
For broader Elysium discussion, see this discussion: https://github.com/orgs/ethereumclassic/discussions/571
You can also ask us questions in Discord and we will be on the Community Calls!
Front-Matter Checklist
Verify that your ECIP file's front-matter block contains all required fields per ECIP-1000:
ecip:—1111title:—Elysium Revenue Contractlang:—enauthor:— Real name(s) and optionally email address or GitHub handlediscussions-to:— URL of the public discussion thread (Discord, GitHub issue, etc.)status:—Drafttype:—Standards Trackcategory:—Corecreated:—2026-03-12Section Checklist
Verify that your ECIP document contains all required sections:
### Abstract— Short (~200 word) description of the technical issue### Motivation— Why the existing protocol is inadequate### Specification— Precise technical specification of the proposed change### Rationale— Design decisions, alternatives considered, and community consensus### Implementation— Reference implementation or notes (may be added beforeFinalstatus)### Copyright/Licensing— Explicit license terms (see ECIP-1000 for accepted licenses)