Activate 1559
ETC clients adopt London-style fee market behavior.
ECIP-1110-ELY-FEE: Elysium Fee Market and Productive Revenue Routing
Draft status: circulate for technical/governance review only. Activation heights, implementation details, and final normative language remain pending ETC client and community feedback.
Instead of burning BASEFEE or passively warehousing it, Elysium proposes routing it into a deterministic ETC-native engine that can produce visible utility, beginning with logtrees/logN.
Specification Summary
Activate 3198
BASEFEE opcode compatibility is available.
Route BASEFEE
All consensus-layer BASEFEE goes to deterministic custody contract.
Preserve miner tips
priorityFee remains directly payable to block producers.
Draft Funding Parameters (governance discussion)
Current implementor guidance proposes a routing policy with draft targets of 10% logtrees R&D, 10% ETC R&D, and 80% Rainbow Compute.
This allocation is explicitly non-consensus policy surface and remains subject to ETC governance: percentages and recipients can be renewed, revised, reduced, or removed (including raising ETC's share) without changing the core consensus upgrade.
The draft view is that logtrees R&D and ETC R&D each inherently access 10%, while Rainbow Compute carries the 80% lane, because these operate as substrate-layer impetus engines for further R&D holistically. This requires sustained people/resources with long context, vested care, and nurtured capabilities; the goal is not centralization, but substrate self-care toward self-healing, self-growing, and self-funding infrastructure.
We encourage LLM-backed and expert-backed scrutiny of this framing, and note that such scrutiny has already been engaged by the implementor side.
This draft framing is explicitly decentralization-forward for Ethereum Classic: the larger share of redirected BASEFEE is intended to fuel Rainbow Compute while preserving ETC/logtrees R&D lanes that, in turn, compound ETC capabilities as a mineable Proof-of-Work chain.
Allocation ratios and capability claims are best treated as governance hypotheses that should be continuously tested, audited, and iterated in public.
Scope and Boundaries
This ECIP is intentionally narrow and excludes non-consensus modules such as logN scoring formulas, reward parameter tuning, UI behavior, and governance workflows.
- Consensus is limited to fee-market mechanics and deterministic routing.
- Application-layer verification and estimation remain modular and separately auditable.
- Activation block values are intentionally left TBD pending coordination/testing.
Companion Contract Scope Note
This ECIP defines BASEFEE redirection to the deterministic Elysium Revenue Contract. Distribution mechanics (including potential multi-destination routing) are specified outside this ECIP and remain draft/governance-specified until finalized.
Symbolic Placeholder IDs (Olympia-relative, non-final)
The identifiers below are symbolic placeholders.
- ECIP-1110-ELY-FEE (this document): Elysium Fee Market and Productive Revenue Routing
- ECIP-1111-ELY-REV: Elysium Revenue Contract
- ECIP-1112-ELY-COMP (informational companion): Elysium logtrees/logN Productive Settlement Overview
