The focus of the next fork of Ethereum, is it enough to read this article?
Author | Qin Xiaofeng
Editor | Lu Xiaoming
Produced | Odaily
Author | Qin Xiaofeng
Editor | Lu XiaomingJustin DrakeOver the past two weeks, the weekly conference call has been canceled as numerous core ethereum developers traveled to Toronto for the scaling conference. This Friday night, Ethereum core developers will continue to hold a conference call, focusing on the hard fork of Istanbul (Istanbul) and deciding on the final proposal (EIP).
From a design perspective, the Istanbul (Istanbul) hard fork is the final fork of Ethereum towards the Serenity phase (no new tokens will be generated). At the same time, the proposal for this fork involves many issues (Progpow, state leasing, chainID, etc.). If some problems are not resolved in this fork, it will have a major impact on the subsequent ecological development of Ethereum. According to Ethereum 2.0 researcher
That being said, Ethereum 2.0 Phase 0 will be released on January 3, 2020.
EIP-615secondary title
EIP-663Postpone ProgPoW, focus on "state leasing"
EIP-1057On the 17th of last month, the Istanbul hard fork proposal (EIP) collection ended, and a total of 29 proposals were collected. These proposals are:
EIP-1108: EVM subroutines and static jumps
EIP-1109: Unlimited SWAP and DUP instructions
EIP-1283: ProgPoW, a Programmatic Proof of Work
EIP-1344: Reduce alt_bn128 precompiled gas cost
EIP-1352: PRECOMPILEDCALL opcode (remove CALL charges for precompiled contracts)
EIP-1380: Without dirty maps, measure the net gas cost of SSTORE
EIP-1559: Add ChainID opcode
EIP-1965: specifies a restricted address range for precompiled/system contracts
EIP-1702: reduce the gas cost of self calls
EIP-1706: Change ETH 1.0 chain gas fee
EIP-1803: method to check if a chainID is valid at a specific block number
EIP-1829: generalized account versioning scheme
EIP-1884: disable SSTORE when gas cost is low
EIP-1930: rename opcode
EIP-1985: Precompilation of Elliptic Curve Linear Combinations
EIP-1959: redefine opcodes that depend on trie-size
EIP-1962: The gas call standard is strict, and it can be restored if there is not enough gas call.
EIP-2014: reasonable limits for some EVM parameters
EIP-2026: new opcode that checks if the chainID is part of the chainID history
EIP-2027: EC arithmetic and pairing with runtime definitions (replaces EIP-1829)
EIP-2028: Extended State Oracle
EIP-2029: State Lease H - Fixed Account Advance
EIP-2031: State Lease C - Accounting Net Contract Size
EIP-2035: Reduce Calldata Gas cost
EIP-2045: State Lease A - State Counter Contract
EIP-2046: Status Lease B--Net Trading Counter
: stateless client - repricing SLOAD and SSTORE to pay for block proofsEIP 1108: gas cost of EVM opcode particles
: Reduce the gas cost of making static calls to precompiled programsEIP-1057In the previous core developer conference call, the tentatively approved proposal was
- Proposed minor changes to the gas fees for the Ethereum network. However, the developers stressed that while the proposal was approved, benchmark data would need to be presented at a later core developer meeting.
In addition, the much-anticipated proposalEIP-1559may be delayed. EIP 1057 proposes an improved PoW algorithm called "Progressive PoW" or ProgPoW, which aims to better utilize GPU-specific computing capabilities.
Previously, developers raised 50,000 DAI (approximately $50,000) through crowdfunding on the open source bounty platform Gitcoin as ProgPoW code audit funds. However, since the code has not been audited by a third-party organization so far, it was announced to be postponed at the developer meeting on May 24.
also delayed
Among these proposals, "state leasing" is particularly dazzling.
The original intention of "state leasing" is that the state size of Ethereum is already very large. If it continues to grow at the current rate, the Ethereum network will become extremely bloated. And we are underestimating the long-term cost of storage, which can be modeled approximately as: bytes * time, so it is necessary for us to make changes to the current state design of Ethereum.
According to the roadmap of Ethereum 2.0, state leasing will also be deployed in ETH 2.0 (the current plan is in phase 2). Whether or not to re-develop on ETH1.0 is believed to be a hot topic in this Friday's conference call.
secondary title
deletion proposal
The above proposals have also caused extensive discussions in the community. Many developers have questioned that some proposals are redundant and should be deleted.
Developer Alex Beregszaszi said: "I'm confused. I think the suggestion of conflicting, adjacent, duplicate EIPs (with 3 or 4 EIPs all about chainid, repricing, SWAP and DUP) should be raised again There was some consensus before. If they are not clearly defined, then there is little point in arguing about the EIP."Up to now, the proposal audit process has only been carried out for a short period, and whether the core developers can give the final answer this Friday is still pending.For the EIP above,
Developer Community (click to enter)
It is also currently being discussed to reduce the workload to reduce the workload of core developers and improve efficiency.
secondary title Afri SchoedonHard Fork Timeline
In addition to paying attention to the proposal, the timing of the Istanbul hard fork is also worthy of attention.
According to the former hard fork coordinator
(departed) timetable, the hard fork process breaks down into "a fixed 9-month cycle". The Istanbul hard fork schedule is as follows:
2019-05-17 (Friday): Deadline for Acceptance of "Istanbul" Proposals
2019-07-19 (Friday): Main client implementation deadline
2019-08-14 (Wednesday): Testnet ((Ropsten, Gorli or ad hoc testnet)) upgrade time
2019-10-16 (Wednesday): Mainnet upgrade time (“Istanbul”)
The first stage of proposal collection has been completed, and the next step is the "main client implementation". The so-called "main client implementation", merging the accepted EPI into the existing ethereum client, is a step akin to putting code together so it can be fully tested.
