ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the main points of the 144th Ethereum Core Developers Consensus Meeting (ACDC #144):Developers agreed to include a new code change EIP 7742 in Pectra, which allows the beacon chain to dynamically set the network's target and maximum blob gas limits. The inclusion of EIP 7742 indicates that developers may also increase the target and maximum blob gas limits in Pectra. However, some developers raised concerns during the call that incorporating additional EIPs (especially EIP 7742) would delay the activation of other Pectra code changes on the mainnet. Developers also discussed the testing progress of Pectra and PeerDAS development.L2 rollup Base developer Francis Li introduced the urgency and fundamental principles of increasing blob capacity in Pectra. Li suggested increasing the blob gas target to 5 and the maximum to 8, along with additional work at the network layer, such as implementing engine_getBlobsV1. Busa pointed out that the increase in blob capacity should be combined with the deployment of EIP 7742, which introduces a mechanism to dynamically set blob gas targets and maximum limits through CL. Busa stated that the current mechanism for setting these parameters is difficult to change, and introducing EIP 7742 would ensure that developers can easily adjust these settings in the future, such as upgrades like PeerDAS. However, Busa also noted that EIP 7742 requires additional work from the EL and CL client teams for deployment and could delay Pectra's timeline by 1 to 2 months. He urged developers to consider starting the work on deploying EIP 7742 as soon as possible to avoid unnecessary delays in the Pectra upgrade.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 144th Ethereum Core Developers Consensus (ACDC) conference call.This week, developers discussed and coordinated modifications to the Ethereum Consensus Layer (CL). Developers agreed to incorporate EIP 7742 changes into Pectra, allowing the beacon chain to dynamically set the network's target and maximum Blob Gas fee limits; EF developer operations engineer Barnabas Busa stated that he plans to shut down Pectra Devnet 3 immediately; currently, Geth and Ethereum JS clients are ready, and the Lighthouse, Teku, and Nimbus clients on the CL side are also ready.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the 198th Ethereum Core Developers Execution (ACDE) conference call. This week, developers discussed EIP 7782 and 7783 that may be included in Pectra. The former proposes to shorten the slot time from 12 seconds to 8 seconds, while the latter suggests a new mechanism to increase the block gas fee limit.Developers have not yet decided whether to incorporate these two mechanisms into Pectra or future upgrades; the deadline for submitting Pectra system contract audit proposals is October 11, and accepted proposals will be confirmed by October 22 at the latest; developers decided to include the EIP 6110 update in Devnet 4; developers agreed to try to launch Pectra Devnet 4 before the Core Developers Consensus (ACDC) conference call on October 17.Additionally, developers are considering names for the public Pectra testnet. Several naming suggestions proposed by community members include MooDeng and Khlong.

ChainCatcher message, the Galaxy official website released the summary of the 143rd Ethereum Consensus Layer Core Developers Conference (ACDC). This meeting mainly discussed:Pectra Devnet 3 update (debugging work is still ongoing)Pectra Devnet 4 preparation status (discussion on simplifying requests triggered by EL and delegating them to CL for parsing, etc.)PeerDAS Devnet update (the latest PeerDAS devnet is facing issues with achieving finality, a restart may be necessary)Update on the implementation of "engine_getBlobsV1" (aimed at helping low-bandwidth validators propose blocks in a timely manner, client teams are working on implementing this method, Stokes emphasized that this is the current top priority)Discussion on increasing blob throughput (some developers suggested first increasing the target number of blobs, and then adjusting based on analysis results)In addition, most developers support the proposal of EIP 7742, which decouples the blob counting between CL and EL.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the 197th Ethereum Core Developers Execution (ACDE) conference, discussing and coordinating changes to the Ethereum Execution Layer (EL). Developers agreed to advance the Pectra upgrade within a limited scope, currently only including 8 Ethereum Improvement Proposals (EIPs) on Devnet 3. They also agreed that a set of 4 EIPs related to the Ethereum blob fee market might be included in Pectra during the upgrade planning process, with Vitalik expressing support for increasing blob capacity in Pectra, while other developers voiced opposition, and no conclusion has been reached yet.Other blob-related EIPs include EIP 7762 (increase MIN_BASE_FEE_PER_BLOB_GAS), EIP 7623 (increase calldata costs), and EIP 7742 (separate blob counting between CL and EL).Beiko confirmed that the next upgrade after Pectra will indeed be named Fusaka, which will include PeerDAS and EOF. Fusaka may also incorporate additional EIPs, provided that further progress can be made on the implementation of these two EIPs. Finally, Beiko stated that a new EIP for EL upgrades will be opened after Osaka, named "Amsterdam," and the EIP originally considered for inclusion in Osaka, namely Verkle, will be carried over to the new Amsterdam EIP.

ChainCatcher news, according to Decrypt, this week, Ethereum's core developers decided to split the network's next major upgrade, Pectra, into at least two parts, with the first update expected to be released around February 2025.Currently, regardless of which tokens are transferred, Gas fees on Ethereum, Base, Arbitrum, Optimism, and other Layer 2 networks must be paid in ETH. A proposal included in the first part of Pectra, EIP-7702, will effectively end this requirement, allowing users to pay Gas fees with other more versatile cryptocurrencies.Another improvement is EIP-7251, which will allow Ethereum stakers to earn rewards on staked amounts exceeding 32 ETH. For example, users currently staking 40 ETH cannot earn from the additional 8 ETH or gain voting rights. This will significantly reduce the bandwidth requirements for the entire Ethereum network.Additionally, two other proposals included in the initial version of Pectra, EIP-6110 and EIP-7002, will also implement fully automated and permissionless ETH staking pools for the first time. The remainder of Pectra may not arrive until 2026.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 142nd Ethereum Core Developers Consensus (ACDC) conference call. This week, developers discussed the decision to split the Pectra upgrade into two hard forks, developers have begun fuzz testing on Pectra Devnet 3, communicated pending issues related to Ethereum Improvement Proposals (EIPs) on Pectra Devnet 3, and a developer of the Base Rollup protocol, known by the pseudonym Francis, submitted an analysis report to support increasing the Blob Gas target for the first part of the Pectra upgrade.

ChainCatcher news, according to CoinDesk, Ethereum developers agreed on Thursday to split the upcoming hard fork Pectra into two batches, aiming to make the large-scale upgrade less cumbersome and reduce the risk of mistakes or errors. The first package may be released in 2025 (as early as February).The first part of Pectra will include Ethereum Improvement Proposals (EIPs), including EIP-7702, which aims to improve wallets. The second part will see an EIP aimed at upgrading the Ethereum Virtual Machine (referred to as EOF).

ChainCatcher news, according to Cointelegraph, Galaxy cryptocurrency researcher Christine Kim believes that due to the current complexity of the Pectra fork and the increased demand for upgrades, the possibility of splitting into two independent upgrades (Prague upgrade and Electra upgrade) is "very high." Christine Kim previously summarized the 196th Ethereum Core Developers Meeting (ACDE), stating that Ethereum developers are seriously considering executing the Pectra upgrade in two phases.In addition, Christine Kim also added that if developers decide to split the Pectra upgrade into two hard forks, the scope could change significantly. It is reported that Ethereum developers will make a decision on this during the next Ethereum All Core Developers teleconference on September 19.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the 141st Ethereum Core Developers Execution (ACDE) conference call, with the main points including:The debugging work for Pectra devnet 2 is nearing completion;The release date for Pectra devnet 3 is yet to be determined;The client teams are testing their latest implementations locally;The release date for Peerdas devnet 2 is yet to be determined;There are still some unresolved issues regarding how to design Peerdas proof computation to be more friendly to home stakers and those running validators on low-spec hardware.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the 141st Ethereum Core Developers Consensus (ACDC) call.This week, developers discussed modifications to the Ethereum Consensus Layer (CL), various updates to the consensus layer specifications and engine API in the Pectra upgrade (including EIP7251 and Beacon block body, etc.), and how to address the proof computation issues for resource-constrained node operators (primarily Home Stakers) in PeerDAS. PeerDAS Devnet2 is expected to be rebuilt on the basis of the Pectra upgrade, rather than Deneb.

ChainCatcher news, summarized by Galaxy's Vice President of Research Christine Kim, reports that Ethereum developers held the 140th All Core Developers Consensus Call (ACDC).The meeting was chaired by Ethereum Foundation researcher Alex Stokes, discussing topics such as the development progress of the Pectra upgrade, PeerDAS, and the naming of the next Ethereum consensus layer upgrade. The developers decided to name this upgrade "Fulu" and plan to use "Fusaka" to refer to the "Fulu-Osaka" upgrade in the future.Additionally, the meeting also addressed technical issues in the Pectra development network and the progress of proposals such as EIP 7742.

ChainCatcher news, according to CoinDesk, the Ethereum EVM Object Format (EOF) improvement proposal has been included in the Pectra hard fork, which is expected to be executed later this year or early next year. The EOF proposal is a series of smaller changes aimed at making significant upgrades to Ethereum's core programming environment, the Ethereum Virtual Machine (EVM). EOF will make smart contracts more developer-friendly, especially for those building decentralized applications using the Solidity or Vyper programming languages. This series of changes is quite subtle and may disrupt existing smart contracts, so developers have added a new version that allows DApp builders to choose which version of the EVM to use when deploying code.Ethereum Foundation core developer Parithosh Jayanthi stated that EOF will be the first major change related to the EVM in years, laying the groundwork for future upgrades to the EVM and demonstrating the intention to continue improving the EVM.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim published a summary of the main points from the 139th Ethereum Core Developers Consensus Meeting (ACDC #139). Debugging for Devnet 2 of the Pectra upgrade is ongoing, and the release date for Devnet 3 is yet to be determined; developers will hold weekly testing update meetings starting Monday to better coordinate the release of Pectra's Devnet; the decision to include EIP-7688 in the Pectra upgrade has been postponed again.

ChainCatcher news, EGalaxy Research Vice President Christine Kim summarized the 193rd Ethereum Core Developer Execution (ACDE) conference call, which discussed the testing progress of the Pectra upgrade, the threat of quantum computers, EIP-7212, and EIP-6110, among other topics.Developers postponed the decision on whether to include EIP-7212 in Pectra, focusing instead on resolving existing code issues. The discussion also covered preparations for Ethereum's resistance to quantum attacks and the proposal for distributing historical data through EIP-4444.

ChainCatcher news, Galaxy's Vice President of Research Christine Kim summarized the 192nd Ethereum Core Developers Execution (ACDE) conference call, where developers shared their latest progress on implementing various code changes, including Ethereum Improvement Proposal (EIP) 7702 and the addition of the Ethereum Object Format (EOF) in Pectra. The EF Developer Operations team's "pk910" also shared updates on Pectra Devnet 1.Developers have differing views on EOF and decided to temporarily incorporate EOF into Pectra. Additionally, before making decisions on EIP 7742 or RIP 7212, developers should focus on the release of Pectra Devnet 1 and the development of EOF and EIP 7702.

ChainCatcher news, according to Christine Kim's summary of the 137th Ethereum Consensus Layer Core Developers Meeting (ACDC), this ACDC discussed the progress of Pectra Devnet 1 and PeerDAS Devnet 1, as well as the fork choice testing generation research led by the Consensys research team TxRx.Regarding Pectra Devnet 1, both CL and EL clients are ready, with a testnet launch expected next week. The EF development operations team is testing various client combinations, and the EthereumJS client is ready for testing.As for PeerDAS Devnet 1, EF DevOps engineer Barnabas Busa stated that the CL client team is fixing bugs and plans to restart this weekend. Stokes updated on the pull request to modify the hardcoded blob gas limit on EL and CL, and plans to formalize it as an Ethereum Improvement Proposal (EIP).The TxRx research team has implemented the initial version of the fork choice testing generator, aimed at identifying client software bugs that could lead to chain splits, and is requesting feedback to refine the test suite.