Repository navigation
Add ECIP-1130: Bastion EVM and Protocol Upgrades (Draft) - #576
Conversation
|
I preempt that the claim might be made that this is a duplicate of 1121. However, this proposal differs in two significant ways:
The EIP bundle choice was discussed on calls https://cc.ethereumclassic.org/calls/46/ and notably https://cc.ethereumclassic.org/calls/53/, where the rationale for why each EIP is included or dropped is listed under "EIP Shortlist Walkthrough with Diego" There are advantages of not including Olympia related proposals in the next ETC Hard Fork.
We hope this PR can be approved in a timely manner, without the drawn out process that 1120 went through. This is a draft PR, not a commitment. Publishing it to the ECIPs website is a means to begin a conversation with the community about the next steps for ETC. |
1120, which is not Olympia, is already approved and in the 112X namespace. Please use 1123 for your later PR, take the 113X space, or simply update the 1121 spec. The 111X namespace was already reserved for Olympia, hence why we used 1120 before, and the next available 1122. |
|
1120 was originally and remins an Olympia option. |
|
1120 is explicitly not an Olympia option.
The quantum PR argument is moot if @chris-mercer wants to use 1122 ...and the Olympia argument is moot if the Quantum PR isn't. 🙄 |
|
This is rather petty, but not worth the energy to fight. FWIW I don't think a draft PR from a non-maintainer can 'claim' an ECIP number. The numbers, per ECIP rules, are allocated by maintainers. Anyway. @diega - how about 1130 ? |
Introduces the Bastion network upgrade proposal: a subset of the Ethereum Cancun, Prague and Osaka execution-layer EIPs (1153, 5656, 6780, 2537, 7823, 7883, 7939, 7951) for Ethereum Classic, with PoS/blob/fee-market EIPs omitted and several EL-applicable EIPs deferred to a follow-up. Numbered 1130 (per reviewer request) to avoid confusion with the Olympia 1111-1121 suite. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Moved to 1130 and updated the date. Force-push dismissed the reviews — re-review appreciated. |
It's real code for a real effort in progress and the number was already claimed. I can change mine if there's a reason to but let's not wave it away by labeling someone contributing in the space as a "non-maintainer" given that these numbers are obtained in-sequence and that was the next one in sequence. The draft work is ongoing. |
| lang: en | ||
| ecip: 1130 | ||
| title: Bastion EVM and Protocol Upgrades | ||
| author: Diego López León (@diega), Istora Mandiri (@IstoraMandiri) |
There was a problem hiding this comment.
Is Istora Mandiri the actual first/last name? Is Istora a software developer by trade as to author implementation or is this contribution solely for the ECIP logistics?
There was a problem hiding this comment.
I'm not sure what the relevance is here?
We have had plenty of pseudonymous ECIP maintainers and authors.
There was a problem hiding this comment.
It's good for accountability to be publicly facing if contributing to open infrastructure. I am personally okay with pseudonymous contributions but there needs to be a means of maintaining accountability. You've also made concerning (to me) comments about what you believe to be the extent to which an LLM can seemingly reduce the barrier to entry for people to contribute as devs...however, the professional landscape will certainly disagree with that and especially for esoteric constructs like core blockchain dev. So I want there to be a means for accountability as to avoid someone without any practical knowledge relying on an LLM without there being any kind of access to their real person.
|
|
||
| ### Omitted (not applicable to ETC) | ||
|
|
||
| The following EIPs from the source upgrades assume Proof-of-Stake, the Beacon Chain, blob data availability, or the EIP-1559 fee market — none of which ETC has adopted — and are therefore omitted from *Bastion*: |
There was a problem hiding this comment.
So these EIPs are being migrated as an ECIP purely to have parity with ETH?
There was a problem hiding this comment.
The EVM standards are applicable to more than just Ethereum Mainnet. This ECIP introduces these features because they are useful, ultimately to improve developer and user experience, not "purely to have parity with ETH".
There was a problem hiding this comment.
I can see down below where some features were deemed irrelevant due to pertaining to Proof of Stake or other Ethereum-specific constructs, so does this mean that the rest are selected if they are not incompatible with Ethereum Classic or someone knows specifically or precisely how they as a developer would use these features? The reason I am asking is because I am interested in understanding more about how much trust we are giving to Ethereum "upstairs" on what the EVM should be like.
There was a problem hiding this comment.
does this mean that the rest are selected if they are not incompatible with Ethereum Classic
Basically, yes. The idea is we generally want to maintain compatibility with EVM, until it's no longer necessary.
someone knows specifically or precisely how they as a developer would use these features?
Each EIP referenced is well defined with it's own rationale.
|
|
||
| ## Simple Summary | ||
|
|
||
| Enable a subset of the Ethereum Foundation **Cancun**, **Prague** and **Osaka** execution-layer protocol upgrades on the Ethereum Classic network in a hard-fork code-named Bastion to enhance compatibility across these networks. |
There was a problem hiding this comment.
Since Bastion already introduces new precompiles, including EIP-2537 and EIP-7951, and since activation blocks are still TBD, I’d like to ask whether ECIP-1122 — ML-DSA-65 verification at 0x101 — should be considered for Bastion scope, explicitly deferred to the next fork, or included only as an address/activation-reservation discussion. I understand Bastion is focused on selected Ethereum EL compatibility, while ECIP-1122 is a more novel ETC-specific post-quantum security primitive. My goal is not to create scope creep, but to avoid unnecessary hard-fork fragmentation if the client teams believe the precompile can meet the required specification, test-vector, gas-benchmark, and cross-client-readiness bar in time.
There was a problem hiding this comment.
One of the goals of this ECIP is to have a minimally contentious "easy win" for the next hard fork, so yes, ML-DSA-65 verification is not in scope for this, and needs a wider conversation that shouldn't block this ECIP. Quantum discussions need their own longer term planning, and will need to also consider what is happening in upstream Ethereum.
There was a problem hiding this comment.
I don't see why we need to be beholden to what is happening in upstream Ethereum if Ethereum Classic can lead the way. If ETC has the first ML-DSA-65 implementation and also the first Falcon implementation, that's good for ETC. This is in keeping also with Ethereum Classic having origination eminence.
Since a precompile is an optional feature for a smart contract developer to use or not use, a successful implementation of ML-DSA-65 is low risk from the point of view of scope creep. My concern in raising this here is that if there is hard forking taking place for this ECIP and if the contents have not been implemented yet, then there might be enough time to complete ML-DSA-65 including with that broader review as to be able to piggyback on this hard fork too.
If we are not going to be blocked on another hard fork relatively soon after this one, then should be fine if quantum things don't go out with this as being blocked on another hard fork is my concern.
I'm not trying to wave away anything or diminish this contribution. I am just referring to ECIP-1000, which states:
So non-maintainers are supposed to wait for number to be assigned by a maintainer. But again, it's not a big deal. |
|
Final call for @realcodywburns @chris-mercer Unless there are objections in the next 24 hours, I'll merge this, a la #573 |
|
Conversation continues in https://github.com/orgs/ethereumclassic/discussions/575#discussioncomment-17539311 |
ECIP Submission
Proposes ECIP-1130: Bastion EVM and Protocol Upgrades — a Meta ECIP defining the Bastion hard fork, which brings a subset of Ethereum's Cancun, Prague and Osaka execution-layer EIPs to Ethereum Classic.
Front-Matter Checklist
ecip:—1130title:— Bastion EVM and Protocol Upgradeslang:—enauthor:— Diego López León (@diega), Istora Mandiri (@IstoraMandiri)discussions-to:— https://github.com/orgs/ethereumclassic/discussions/575status:—Drafttype:—Metacategory:— N/A (only required forStandards Track)created:—2026-05-13Section Checklist
## Abstract## Motivation## Specification## Rationale## Implementation(placeholder; to be completed beforeFinal)## Copyright— CC0-1.0Description
Bastion adds the following EL EIPs to ETC: 1153 (transient storage), 5656 (
MCOPY), 6780 (SELFDESTRUCTsame-tx), 2537 (BLS12-381 precompiles), 7823 + 7883 (MODEXPbounds & repricing), 7939 (CLZ), and 7951 (secp256r1P256VERIFY).EIPs that assume Proof-of-Stake, the Beacon Chain, blob data availability, or the EIP-1559 fee market are omitted, and several EL-applicable EIPs (2935, 7623, 7702, 7825, 7935) are deferred to a follow-up ECIP. No fee-market changes are introduced, consistent with Mystique and ECIP-1017.
Activation blocks for Mordor and mainnet are still
TBDpending the fork schedule.🤖 Generated with Claude Code