OpenChainGraph Suite · ART-614 · Ethereum / Account-Abstraction Crypto Primitive
EIP-7702 Authorization-Tuple Decoder
Recomputes the EIP-7702 authorization-tuple hash (keccak256(0x05 || rlp([chain_id, address, nonce])), the "Set EOA account code" standard live on Ethereum mainnet since the Pectra upgrade, 2025-05-07), recovers the ECDSA signer, and reports the address the recovered signer is authorizing as its delegate. The tuple's own address field IS the delegate: the code the EOA is pointing itself at. This node stops at that address: it never inspects, fetches, or judges the delegate contract's bytecode.
EIP-7702 / Pectrasecp256k1 recovery (vendored, no hand-rolled crypto)Address-only, no code-safety verdict
๐ All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data โ use synthetic or anonymised inputs only.
What This Does and Does Not Prove
This node recovers the address whose private key signed the supplied authorization tuple: "this EOA authorized this specific delegate address, under this specific chain_id and nonce." It does not inspect, fetch, or judge the delegate contract's code, and issues no safe/unsafe verdict, ever. It does not confirm the authorization was ever submitted or applied on-chain, and does not confirm the EOA's account nonce matches the declared nonce at any block. chain_id = 0 is EIP-7702-defined as a valid, deliberate cross-chain authorization (replayable on any chain), never treated as malformed input. This node never fetches chain state and is never a party to a transaction.
Authorization Tuple
The address field is the delegate the EOA is authorizing itself to point at, reported as a plain fact below, never analyzed. chainId = 0 is a deliberate, spec-valid cross-chain authorization, not an error.
Signature
Supply either signature (full hex blob) OR the split r/s fields, plus a recovery marker: yParity (the authorization tuple's native field name) takes priority, else v, else the byte embedded in a 65-byte signature.
Copy this paragraph into Claude, OpenClaw, or any MCP-aware agent to run this exact tool, with this sample, and verify the artifact.
Run the AINumbers MCP tool `decode_eip7702_authorization_tuple`. Task: Recompute the EIP-7702 authorization-tuple hash from declared (chain_id, address, nonce), recovers the ECDSA signer, and reports the address-only fact of the delegate the EOA is authorizing.
Call it with arguments: {"policy_parameters":{"chainId":1,"address":"0x1234567890123456789012345678901234567890","nonce":0,"r":"0xbcc0abd2b842f32cc9c8844ec50c0d5c9b41563f825ef1a143ad93428fb23ad8","s":"0x12678a935e15a1d1fae421fa00abd642222fb4db4aaf4f95a894ba0e38eebbae","yParity":0}}
Verify before trusting: call `verify_execution_hash` on mcp.ainumbers.co (https://mcp.ainumbers.co/mcp) with the parameter `claimed_hash` set to the returned `execution_hash`, passing the full artifact the run returned (the object containing `policy_parameters` + `output_payload` + `execution_hash`; equivalently `policy_parameters` + `output_payload` with `claimed_hash`), not the bare hash string, or re-run the in-page WebMCP tool `decode_eip7702_authorization_tuple`.
Return the ledger link https://ledger.ainumbers.co/ so a human can re-verify without contacting us.
PII rule: All inputs are processed locally in your browser. No data is transmitted. Do not enter real personal data โ use synthetic or anonymised inputs only.
Open the tool with the sample prefilled: https://ainumbers.co/chaingraph/art-614-eip7702-authorization-tuple-decoder.html#p=v1.H4sIAAAAAAAA_wHsABP_eyJjaGFpbklkIjoxLCJhZGRyZXNzIjoiMHgxMjM0NTY3ODkwMTIzNDU2Nzg5MDEyMzQ1Njc4OTAxMjM0NTY3ODkwIiwibm9uY2UiOjAsInIiOiIweGJjYzBhYmQyYjg0MmYzMmNjOWM4ODQ0ZWM1MGMwZDVjOWI0MTU2M2Y4MjVlZjFhMTQzYWQ5MzQyOGZiMjNhZDgiLCJzIjoiMHgxMjY3OGE5MzVlMTVhMWQxZmFlNDIxZmEwMGFiZDY0MjIyMmZiNGRiNGFhZjRmOTVhODk0YmEwZTM4ZWViYmFlIiwieVBhcml0eSI6MH1LD7Kk7AAAAA