Unverified50% confidenceFactExact time
The 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.
1
Sources
50%
Confidence
Long-term
Relevance
10/15/2026
First Seen
Sources
Related Entities
Related Claims
UnverifiedAfter 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.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.66% similarUnverifiedThe OAuth 2.0 specification defines a standard Token Revocation interface in RFC 7009, allowing clients to actively revoke tokens.63% similarUnverifiedThere are two mainstream patterns for propagating original authorization information in multi-hop call chains: token passthrough and exchanging for a new token via OAuth 2.0 Token Exchange (RFC 8693).60% 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.59% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1032663API
curl https://kongchang.com/api/v1/knowledge/claims/1032663MCP
get_claim(id=1032663)