ethrex v27.0.0 adds state and block overrides to the RPC simulation methods. It also ships the Ethereum Foundation's new bootnode fleet for mainnet, Sepolia, and Hoodi, and stops transaction-admission rules from rejecting simulated calls. The override sets are the headline. eth_call, eth_estimateGas, eth_createAccessList, and debug_traceCall now accept the State Override Set and Block Override Set that geth defines, on both L1 and L2: per-address balance, nonce, code, state, and stateDiff, plus movePrecompileToAddress. Tooling that assumes those parameters exist, from forge script to Tenderly-style and MEV simulators to wallet balance previews and Multicall3 aggregators, now works against an ethrex RPC. Also in v27.0.0: - Bootnodes: the Ethereum Foundation's Node Infrastructure team is replacing the fleet that ships as the EF entries, and the new records are here. Five nodes per network, each serving mainnet, Sepolia, and Hoodi, geographically distributed, multi-cloud, dual stack, and spread across several discovery implementations, so one implementation bug cannot take the whole set down. It is a replacement rather than an addition, and third-party bootnodes and DNS discovery roots are untouched. Nodes pick the records up on upgrade, with no configuration change. - Simulated calls are no longer refused by transaction-admission rules. A call object carries no signature, so EIP-3607's contract-sender rule has nothing to protect: a smart contract wallet previewing its own transaction now gets a result instead of an error saying the sender should not be a contract. Transaction admission and block execution are unchanged. - A method in a namespace that is not enabled now says so, instead of reporting itself as not implemented. --http.api defaults to eth,net,web3, so debug_* probes against a stock node were reading as missing functionality when the handler was simply never reached. - Stateless-validator guests are on ERE v0.17.0, with the ERE version pinned by tag across the guest manifests and the release workflow. If you run ethrex, upgrade. No resync is needed.

EIP-8141 (Frame Transactions) is now a Hegotá headliner! We backed frames from the moment they were first proposed as one, and we've been building an implementation in ethrex ever since. That implementation now runs two public testnets: one dedicated to frame transactions, and one dedicated to privacy, which adds the companion EIPs also up for Hegotá: EIP-8250 (Keyed Nonces), EIP-8272 (Recent Roots), and EIP-7805 (FOCIL). The future of Ethereum is looking good, and you can already get a taste of it: faucet.privacy.ethrex.xyz faucet.frames.ethrex.xyz

Frame transactions testnet post:

Following up on our execution EIP tier list, we wanted to share our combined execution and consensus rankings for Hegota. We've followed the same EF Protocol scoring system and tier definitions for both lists. We'd also like to make a special mention of the post-quantum-ready deposit contract proposal. It didn't make it onto the Hegota EIP selection list, but we think proposals like this one should be included in the fork to prepare validator deposits for future post-quantum credentials. We'll expand on our thoughts about Hegota and the reasoning behind our rankings in the blog post we're preparing.

Over the last few months, we've been working with EF researchers and EIP authors on Hegota proposals, implementing them in ethrex and opening our public testnets to users and other client teams. We wanted to share our execution EIP tier list, which follows the EF Protocol team's scoring system and tier definitions. After spending these months building and testing several of these proposals, we're excited to contribute to the discussion of what should come next for Ethereum. We'll also share our consensus EIP tier list soon, as part of a blog post where we'll expand on our thoughts about Hegota.