AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 36 Bitcoin

feat(core/ethereum): integrate EIP-7702 delegation into `EthereumSignTxEIP1559`

Public commit record

What the developer wrote

Authored by Roman Zeyde

90/100 · Strong
feat(core/ethereum): integrate EIP-7702 delegation into `EthereumSignTxEIP1559`

For now, let's support at most one EIP-7702 authorization tuple per transaction.

The feature is still experimental, so no changelog entry is added.

[no changelog]
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
The short version

What changed, and why it matters

This commit adds experimental support for a new Ethereum feature (EIP-7702) that lets an account temporarily delegate control to a smart contract. The change is feature work, not a bug fix, and includes several safety guardrails: it is blocked unless experimental features are enabled, requires relaxed safety checks for authorizations (but not revocations), rejects cross-chain delegation, and only allows known delegate addresses. There is no direct evidence in the commit that this fixes a security vulnerability.

Recommended action

Treat this as a feature addition rather than an urgent security patch. Reviewers should verify that the EIP-7702 signature digest construction matches the final EIP-7702 specification, that the allowlist lookup cannot be bypassed, that the transaction type override is correct, and that the UI confirmation screens accurately describe the delegation. Because it is experimental, ensure the feature flag and safety-check gating are enforced in all code paths.

Security signals we found

01

New cryptographic signing path added for EIP-7702 authorization tuples

02

Transaction type switched from 0x02 to 0x04 when EIP-7702 delegation is present

03

Cross-chain delegation explicitly rejected (chain_id == 0)

04

Non-revocation authorizations gated behind relaxed safety checks and an allowlisted delegate address

05

Revocation (delegate == zero address) permitted under strict safety checks

06

Experimental feature flag required; no changelog entry

07

Payment requests, non-zero value, calldata, and unknown networks rejected for EIP-7702 path

Risk score

Why this scored 36/100

Our methodology →
Potential impact 8/30
Exploitability 6/25
Stealth signal 4/15
Affected reach 7/15
Confidence 7/10
Evidence quality 4/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.