Unverified50% confidenceFactExact time
After EIP-7702 authorization the account is still an EOA—the address, private key, and nonce semantics are all preserved, it is just that each call additionally executes the code of the delegated address, and the EOA is not turned into a contract account.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedThe EIP-7702 authorization tuple contains six fields: chain_id, address, nonce, y_parity, r, s; the signer can be recovered from the tuple via ecrecover.72% similarUnverifiedCalling eth_getCode on any address: returning empty indicates an ordinary EOA, returning data beginning with 0xef0100 indicates it has been delegated, and the following 20 bytes are the delegation address; a delegated account can have a completely clean and very short transaction history.72% similarUnverifiedecrecover is a built-in precompiled contract of the Ethereum Virtual Machine whose purpose is to "recover the signer's address given a message hash and an ECDSA signature", requiring no private key, no network connection, and no reliance on centralized services.68% similarUnverifiedIn EMA scenarios, account linking should rely on signed assertions issued by the enterprise IdP rather than manual user confirmation—this is one resolution pattern.66% similarUnverifiedThe Token Exchange specification in the OAuth 2.0 framework (RFC 8693) allows an authenticated principal to delegate a portion of its permissions to another entity while retaining authorization chain provenance information.66% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1032661API
curl https://kongchang.com/api/v1/knowledge/claims/1032661MCP
get_claim(id=1032661)