Merge branch 'ethereum:master' into master

Author: ⁸Mehmet

.github/workflows/auto-review-trigger.yml

@@ -52,7 +52,7 @@ jobs:
           files: pr-number.txt
 
       - name: Save PR Number
-        uses: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05
+        uses: actions/upload-artifact@65c4c4a1ddee5b72f698fdd19549f0f0fb45cf08
         if: steps.check_pr_number_exists.outputs.files_exists == 'true'
         with:
           name: pr-number

.github/workflows/ci.yml

@@ -31,7 +31,7 @@ jobs:
           echo $MERGE_SHA > ./pr/merge_sha
 
       - name: Upload PR Number
-        uses: actions/upload-artifact@65d862660abb392b8c4a3d1195a2108db131dd05
+        uses: actions/upload-artifact@65c4c4a1ddee5b72f698fdd19549f0f0fb45cf08
         with:
           name: pr_number
           path: pr/
@@ -42,12 +42,12 @@ jobs:
 
     steps:
       - name: Checkout EIPs
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
         with:
           repository: ethereum/EIPs
           path: ''
       - name: Checkout ERCs
-        uses: actions/checkout@v4
+        uses: actions/checkout@11bd71901bbe5b1630ceea73d27597364c9af683
         with:
           repository: ethereum/ERCs
           path: ERCs

EIPS/eip-1898.md

@@ -4,7 +4,8 @@ title: Add `blockHash` to defaultBlock methods
 description: Add `blockHash` option to JSON-RPC methods that currently support defaultBlock parameter.
 author: Charles Cooper (@charles-cooper)
 discussions-to: https://ethereum-magicians.org/t/eip-1898-add-blockhash-option-to-json-rpc-methods-that-currently-support-defaultblock-parameter/11757
-status: Review
+status: Last Call
+last-call-deadline: 2025-03-04
 type: Standards Track
 category: Interface
 created: 2019-04-01

EIPS/eip-2537.md

@@ -4,7 +4,8 @@ title: Precompile for BLS12-381 curve operations
 description: Adds operation on BLS12-381 curve as a precompile in a set necessary to efficiently perform operations such as BLS signature verification.
 author: Alex Vlasov (@shamatar), Kelly Olson (@ineffectualproperty), Alex Stokes (@ralexstokes), Antonio Sanso (@asanso)
 discussions-to: https://ethereum-magicians.org/t/eip2537-bls12-precompile-discussion-thread/4187
-status: Review
+status: Last Call
+last-call-deadline: 2025-04-01
 type: Standards Track
 category: Core
 created: 2020-02-21
@@ -194,10 +195,6 @@ Error cases:
 - An input is on its respective elliptic curve but not in the correct subgroup
 - Input has invalid length
 
-Note:
-
-If any input is the infinity point, pairing result will be 1. Protocols may want to check and reject infinity points prior to calling the precompile.
-
 #### ABI for mapping Fp element to G1 point
 
 Field-to-curve call expects `64` bytes as an input that is interpreted as an element of Fp. Output of this call is `128` bytes and is an encoded G1 point.

EIPS/eip-2539.md

@@ -4,7 +4,7 @@ title: BLS12-377 curve operations
 description: Precompiles for BLS12-377 curve operations
 author: Alex Vlasov (@shamatar), hujw77 (@hujw77)
 discussions-to: https://ethereum-magicians.org/t/eip-2539-bls12-377-precompile-discussion-thread/4659
-status: Draft
+status: Stagnant
 type: Standards Track
 category: Core
 created: 2020-02-26

EIPS/eip-2935.md

@@ -4,7 +4,8 @@ title: Serve historical block hashes from state
 description: Store and serve last 8192 block hashes as storage slots of a system contract to allow for stateless execution
 author: Vitalik Buterin (@vbuterin), Tomasz Stanczak (@tkstanczak), Guillaume Ballet (@gballet), Gajinder Singh (@g11tech), Tanishq Jasoria (@tanishqjasoria), Ignacio Hagopian (@jsign), Jochem Brouwer (@jochem-brouwer), Sina Mahmoodi (@s1na)
 discussions-to: https://ethereum-magicians.org/t/eip-2935-save-historical-block-hashes-in-state/4565
-status: Review
+status: Last Call
+last-call-deadline: 2025-04-01
 type: Standards Track
 category: Core
 created: 2020-09-03

EIPS/eip-3155.md

@@ -4,7 +4,8 @@ title: EVM trace specification
 description: A JSON format for EVM traces
 author: Martin Holst Swende (@holiman), Marius van der Wijden (@MariusVanDerWijden)
 discussions-to: https://ethereum-magicians.org/t/eip-3155-create-evm-trace-specification/5007
-status: Review
+status: Last Call
+last-call-deadline: 2025-03-01
 type: Standards Track
 category: Interface
 created: 2020-12-07

EIPS/eip-3540.md

@@ -2,7 +2,7 @@
 eip: 3540
 title: EOF - EVM Object Format v1
 description: EOF is an extensible and versioned container format for EVM bytecode with a once-off validation at deploy time.
-author: Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Andrei Maiboroda (@gumb0), Matt Garnett (@lightclient)
+author: Alex Beregszaszi (@axic), Paweł Bylica (@chfast), Andrei Maiboroda (@gumb0), Matt Garnett (@lightclient), Piotr Dobaczewski (@pdobacz)
 discussions-to: https://ethereum-magicians.org/t/evm-object-format-eof/5727
 status: Review
 type: Standards Track
@@ -147,8 +147,6 @@ types_section := (inputs, outputs, max_stack_height)+
 | container_section | variable | n/a           | arbitrary EOF-formatted container                                                          |
 | data_section      | variable | n/a           | arbitrary sequence of bytes                                                                |
 
-See [EIP-4750](./eip-4750.md) for more information on the type section content.
-
 **NOTE**: A special value of `outputs` being `0x80` is designated to denote non-returning functions as defined in a separate EIP.
 
 #### EOF version 1 validation rules

EIPS/eip-3670.md

@@ -55,6 +55,12 @@ Allowing implicit zero immediate data for `PUSH` instructions introduces ineffic
 
 The deprecated instructions `CALLCODE` (0xf2) and `SELFDESTRUCT` (0xff) are removed from the `valid_opcodes` list to prevent their use in the future.
 
+### BLOCKHASH instruction
+
+The `BLOCKHASH` instruction is well replaced by the system contract introduced in [EIP-2935](./eip-2935).
+However, despite a replacement being introduced this opcode has not been deprecated.
+This opcode will remain valid in EOF not to differentiate from legacy bytecode.
+
 ## Backwards Compatibility
 
 This change poses no risk to backwards compatibility, as it is introduced at the same time EIP-3540 is. The validation does not cover legacy bytecode (code which is not EOF formatted).