Add New Article: Olympia Development Series — Implementing ECIP-1111 & ECIP-1112 (Part 1) #1652
Conversation
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
…P-1112 This commit adds Part 1 of the Olympia Development Series to the community website. The article provides a neutral, ECIP-1000-compliant overview of ECIP-1111 and ECIP-1112, describing the proposed design, implementation work underway in reference clients, and the consensus boundary of the Olympia framework. No language implies acceptance or activation; content reflects Draft-stage development and is consistent with Part 0.
✅ Deploy Preview for ethereumclassic ready!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
IstoraMandiri
previously requested changes
Nov 30, 2025
content/blog/2025-12-01-olympia-development-series-part1-ecip-1111/index.md
Show resolved
Hide resolved
chris-mercer
dismissed
IstoraMandiri’s stale review
Topic already addressed in draft. Now change needed.
L174: "The Olympia ECIPs (1111–1115) are currently in Draft status..."
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 “Olympia Development Series — Implementing ECIP-1111 & ECIP-1112 (Part 1)” to the Ethereum Classic community website. The article continues the Olympia Development Series and follows the ECIP-1000 standards used in Part 0.
Part 1 provides a technical, Draft-stage overview of the two consensus-related ECIPs within the Olympia framework (ECIP-1111 and ECIP-1112). The article:
• Describes the proposed design of ECIP-1111 (BASEFEE mechanics, Type-2 support, opcode)
• Explains ECIP-1112 and the deterministic Treasury contract destination
• Clarifies the consensus boundary between ECIP-1111/1112 and the contract-layer ECIPs
• Summarizes current reference-client implementation work
• Includes a procedural clarity section reflecting ECIP-1000 neutrality
The article is descriptive only and does not imply acceptance, activation, or consensus. It mirrors the structure and tone of Part 0 while presenting the engineering context for reference-client development as Olympia progresses through the Draft phase.