About HIPs

    GitHub Logo HIP-1341: Support for Ethereum Pectra Release

    Author Luke Lee, Lukasz Gasior
    Working Group Fernando Paris, Luis Mastrangelo
    Discussions-To https://github.com/hiero-ledger/hiero-improvement-proposals/pull/1341
    Status Last Call ⓘ
    Needs Hedera Review Yes ⓘ
    Needs Hiero Approval Yes ⓘ
    Last Call Period Ends ⓘ Mon, 09 Feb 2026 07:00:00 +0000
    Type Standards Track ⓘ
    Category Service ⓘ
    Created 2025-11-14
    Updated 2026-01-26
    Requires 1340

    Table of Contents

    Abstract

    Ethereum’s Pectra upgrade (activated May 7, 2025) introduced 11 EIPs, but not all of them are applicable to the Hiero network. This HIP defines the adoption of Pectra for the Smart Contract Service by distinguishing which EIPs are applicable to Hiero versus non-applicable.

    Motivation

    To maintain EVM compatibility, applicable EIPs introduced in Ethereum’s Pectra upgrade must be supported by the Hiero network.

    Rationale

    Maintaining EVM compatibility is a core goal of the Hiero network, so updates from Ethereum releases must be adopted. However, not every EIP needs to be implemented. Each EIP needs to be evaluated individually for applicability.
    Some EIPs address functionality that is (i) not supported by Hiero (e.g., blobs), (ii) aimed at improving validators—which have no Hiero equivalent—or (iii) focuses on layers outside of L1 execution engine. All other EIPs should be considered for support.

    User stories

    • As a smart contract developer, I want to access BLS12-381 precompiles as described in EIP-2537.
    • As a smart contract developer, I expect the gas cost for call data to increase as described in EIP-7623 so that gas costs are consistent with Ethereum after the Pectra release.
    • As a smart contract developer, I want to set code for EOAs and execute it when the EOA address is called, as described in EIP-7702 so that new use cases such as batching, sponsorship and privilege de-escalation become possible.
    • As an end user, I want to be able to be able to call an EOA that has executable code so that I can make use of new use cases made available by EIP-7702.
    • As an EOA, I want to be able to set execution code for myself via signing an authorization and including the authorization in a transaction so that I can add smart contract functionalities and improved user experience without the need to migrate assets to a new wallet address. .

    Specification

    The eleven EIPs in the Pectra release are listed below and categorized as either applicable or non-applicable to Hiero.

    Applicable EIPs

    EIP-2537

    EIP-2537 introduces new precompiles for BLS12-381 operations. Besu has already implemented these precompiles. The necessary work for Hiero is to make them available within HSCS. The new precompile functions and addresses are summarized in this table.
    These precompile functions can be called utilizing functions such as call and staticcall. BLS encryption offers features such as efficient aggregation, constant size and faster verification. While possible to implement in Solidity, the gas costs are prohibitive. The precompiles introduced in EIP-2537 provides a native implementation in order to provide efficient execution and lower gas cost.

    Function Name Precompile address How to use it Input size (bytes)
    BLS12_G1ADD 0x0b address(0x0b).call(abi.encodePacked(input)); 256
    BLS12_G1MSM 0x0c address(0x0c).call(abi.encodePacked(input)); 160 * k slices
    BLS12_G2ADD 0x0d address(0x0d).call(abi.encodePacked(input)); 512
    BLS12_G2MSM 0x0e address(0x0e).call(abi.encodePacked(input)); 288 * k slices
    BLS12_PAIRING_CHECK 0x0f address(0x0f).call(abi.encodePacked(input)); 384 * k slices
    BLS12_MAP_FP_TO_G1 0x10 address(0x10).call(abi.encodePacked(input)); 64
    BLS12_MAP_FP2_TO_G2 0x11 address(0x11).call(abi.encodePacked(input)); 128

    The EIP specifies the input format for each precompile function. For more details, please refer to the EIP document.

    EIP-7623

    EIP-7623 increases the gas cost of calldata to reduce the maximum block size. Although the limit to maximum block size and block gas limit do not directly apply to Hiero, for EVM equivalence, Hiero will also adopt these gas costs. The necessary changes have been implemented in the PragueGasCalculator in Besu, but these changes must be made available to the gas calculator used by Hiero SCS.

    More specifically, the gas calculation remains the same but a minimum floor value defined as TOTAL_COST_FLOOR_PER_TOKEN ***** tokens_in_calldata is introduced

    where TOTAL_COST_FLOOR_PER_TOKEN = 10

    and tokens_in_calldata = zero_bytes_in_calldata + nonzero_bytes_in_calldata * 4

    EIP-7702

    EIP-7702 is the most complex EIP to implement from the Pectra release. It allows for setting and executing contract code for EOAs. HIP-related details can be found in HIP-1340.

    Non-Applicable EIPs

    The non-applicable EIPs are described and categorized below.

    • EIPs that enhance blob support. These are not applicable since Hiero does not support blobs.
    • EIPs related to Ethereum validators. Hiero does not have validators, so these EIPs are not applicable.
    • EIPs related to Ethereum 2.0. These are not applicable since Hiero does not implement Ethereum 2.0 features.

    Impact on Mirror Node

    EIP-2537 and EIP-7623 do not meaningfully impact the mirror node beyond normal acceptance of the new code once it is available for simulation.
    EIP-7702 impact can be found in the related HIP-1340.

    Impact on JSON-RPC relay

    EIP-7623 changes the calculation for determining intrinsic gas. As this value is also calculated by the JSON-RPC relay, the relay must be updated to reflect the new calculation. EIP-7702 also changes the definition of intrinsic gas and the impact can be found in the related HIP-1340.

    Impact on SDK

    EIP-2537 and EIP-7623 do not meaningfully impact the SDK. EIP-7702 impact can be found in the related HIP-1340.

    Backwards Compatibility

    EIP-2537 does not impact backwards compatibility.
    EIP-7623 alters the gas consumption for transaction and this may impact new and subsequent interactions with existing contracts by end users seeing an increase in gas costs.

    Security Implications

    There are no known security implications from EIP-2537 and EIP-7623. EIP-7702 impact can be found in the related HIP-1340.

    How to Teach This

    Hiero will support EIP-2537, EIP-7623, and EIP-7702 to maintain EVM compatibility. Other Pectra EIPs are not applicable to Hiero.
    Documentation for these and other Pectra related EIPs are available via the official Ethereum EIP website

    Rejected Ideas

    With the implementation of HIP-1086 which allows for jumbo transactions, the ability to support blobs was considered but ultimately rejected in this HIP as out of scope for the Pectra upgrade. A future HIP could be proposed to add blob support to Hiero and allow for the adoption of blob related EIPs from Pectra.

    Open Issues

    None.

    References

    HIP-1340 Hedera Support for EIP-7702: Set EOA Account Code

    EIP-7600 Pectra Hardfork EIP-2537: Precompile for BLS12-381 curve operations

    EIP-2935: Save historical block hashes in state

    EIP-6110: Supply validator deposits on chain

    EIP-7002: Execution layer triggerable exits

    EIP-7251: Increase the MAX_EFFECTIVE_BALANCE

    EIP-7549: Move committee index outside Attestation

    EIP-7623: Increase calldata cost

    EIP-7685: General purpose execution layer requests

    EIP-7691: Blob throughput increase

    EIP-7702: Set EOA account code

    EIP-7840: Add blob schedule to EL config files (Informational)

    Copyright/license

    This document is licensed under the Apache License, Version 2.0 — see LICENSE or https://www.apache.org/licenses/LICENSE-2.0.

    Citation

    Please cite this document as: