ECIP-1130: Bastion EVM and Protocol Upgrades #575
Replies: 1 comment 1 reply
-
|
Worth noting for anyone reviewing: all eight EIPs in 1130 are already specified in Olympia ECIP-1121 (published December 2025), alongside ~7 additional execution-layer EIPs and the eth/69–70 networking layer that 1130 omits or defers. The distinction is the fee market and treasury, which 1130 leaves out by design. That's the part that addresses what the network faces: the collapse of its discretionary funding source and the absence of a long-term security budget as block rewards decline. Olympia carries the full EVM set, the funding mechanism, and fee-market alignment between core development and the security user base (PoW miners); 1130 is a partial EVM subset without the funding and security-budget mechanism. Everyone's welcome to submit ECIPs — it's an open process. Noting the overlap here so reviewers have the full picture: this EIP set is already specified and in implementation under the Olympia suite, targeting mainnet before 2027 and in final testing on Mordor across the reference clients — including Fukuii, the only ETC-native client, which carried much of the development burden. You can follow the Olympia implementation in: https://github.com/orgs/ethereumclassic/discussions/530 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
ECIP-1130 is a draft meta ECIP defining the Bastion hard fork, which brings a subset of Ethereum's Cancun, Prague and Osaka execution-layer EIPs to Ethereum Classic.
#576
https://ecips.ethereumclassic.org/ECIPs/ecip-1130
Beta Was this translation helpful? Give feedback.
All reactions