# EIP-8477 comment seeks an exception for pre-signed revocations

Canonical: https://forkbrief.com/news/9c3d9994-c670-4e47-9cd1-cb9587d10bd7
Published: 2026-11-03T20:36:50.366Z
Publisher: Fork Brief

A new proposal discussion distinguishes authorization expiry from installed delegation and raises a question about offline revocation workflows.

A November 3 [Ethereum Magicians discussion](https://ethereum-magicians.org/t/eip-8477-recent-block-bound-delegation-authorizations/30269) of EIP-8477 has drawn a request to exempt pre-signed revocations from a proposed expiry rule. The question concerns whether an authorization prepared offline could remain usable after its signed block falls outside the draft’s inclusion window.

The discussion’s author describes a change to EIP-7702 delegation authorizations: each would additionally sign an execution block number and that block’s header hash. For inclusion in block N, the anchor would have to match one of the preceding 256 ancestors. An anchor 256 blocks behind would qualify; one 257 blocks behind would not. Current and future blocks would be excluded.

According to that summary, an expired or mismatched anchor would cause the authorization to be skipped before signature recovery or authority-specific state access. That entry would neither consume the authority’s nonce nor clear an existing delegation. Structurally malformed authorizations would instead invalidate the transaction.

The distinction is between accepting an authorization and retaining an installed delegation. The author says a delegation already installed would remain in effect after its original anchor expired. The proposed freshness rule would apply to installation, replacement and zero-address revocation alike.

In a subsequent comment, participant Zealynx asked whether revocations could receive an exception. The comment identifies an offline recovery workflow as a reason to examine that choice and asks for its treatment to be explained in the rationale. It is feedback, not an accepted amendment.

The discussion records an initial draft dated October 30. Its [standards pull request](https://github.com/ethereum/EIPs/pull/12601) remained open and unmerged when checked on November 3. The author says adoption would require a coordinated network upgrade, with an eight-field authorization replacing the legacy six-field format. This discussion does not establish an activated Ethereum change or implementation adoption.

## Sources

- [EIP-8477: Recent Block Bound Delegation Authorizations](https://ethereum-magicians.org/t/eip-8477-recent-block-bound-delegation-authorizations/30269) — Ethereum Magicians

- [Editorial policy](https://forkbrief.com/editorial-policy)
- [Request a correction](https://forkbrief.com/corrections)