New Ethereum Draft Proposes Allowing Wallets to Permanently Disable EIP-7702 Delegation

Source: PANews2026/10/31 18:55
Analysis
This draft targets a structural weakness introduced by EIP-7702: once an EOA delegates to contract code, the owner has no native way to revoke that delegation permanently, so a compromised or malicious delegate can keep executing at the address. The proposed mechanism is deliberately minimal, writing a non-executable three-byte marker via a currently invalid type 4 transaction so future authorizations are skipped while transfers and outbound calls still work. The practical effect is a one-way safety switch, which means users must weigh it against recovery schemes and assets that depend on delegated code, and the proposal's own caveats confirm it does nothing about key theft itself. Watch whether it receives an EIP number and client implementations, how wallet teams expose such an irreversible option in their interfaces, and whether recovery-focused projects propose a reversible alternative before any network upgrade bundles it.

If you have any feedback or questions about this content, please contact us at crypto.news@kcex.com

PANews, Oct. 31 — According to The Defiant, Ethereum developer nicolashw submitted a draft core EIP proposal on Oct. 30 titled "Permanent Exit from EOA Delegation," which would allow key-controlled wallets to permanently disable EIP-7702 delegation, letting account owners refuse smart contract execution at their existing addresses. The proposal has not yet been assigned a number and remains open and unmerged; activation would require a network upgrade. The draft would use a currently invalid EIP-7702 type 4 transaction to install a non-executable three-byte marker in the account, causing future delegation authorizations to be skipped. The account retains its address, normal transfer and contract-calling capabilities, but incoming calls will not execute code.

The draft notes that this feature can only block EIP-7702 delegation and cannot guard against other risks after a private key is stolen. If the private key is leaked, an attacker can still move funds, grant token approvals or sign contract authorizations, and existing approvals would not be revoked. Exiting delegation could also disable recovery features that rely on delegation, or render assets that require the old delegation code inaccessible.

Disclaimer: The articles reposted on this website are sourced from public platforms and are for reference only. These articles do not represent the views or opinions of KCEX. All copyrights belong to the original authors. If you believe that any reposted article infringes upon the rights of a third party, please contact crypto.news@kcex.com for removal. KCEX makes no representations or warranties regarding the timeliness, accuracy, or completeness of reposted articles, and shall not be liable for any actions or decisions made based on such content. Reposted materials are for informational purposes only and do not constitute advice, endorsement, or basis for any commercial, financial, legal, and/or tax decisions.