web3wagmi
← All standards

ERC-7730 Structured Data Clear Signing Format

DraftERCcreated 2024-02-07requires EIP-155, EIP-712

JSON format describing how to clear-sign smart contract calls and typed messages.

Authors: Laurent Castillo (@lcastillo-ledger), Derek Rein (@arein), Pierre Aoun (@paoun-ledger), Arik Galansky (@arikg), Bartosz Rozwarski (@llbartekll), Kaan Uzdogan (@kuzdogan), Fredrik (@Fredrik0x), Alex Forshtat (@forshtat)

Functions this standard introduces (1)

0x9db3887cmyFunction(address,uint256,(string,uint256))

Depends on (2)

Proposals this one names in its requires field.

EIP-155Simple replay attack protectionEIP-712Typed structured data hashing and signing

What the specification covers

AbstractMotivationSpecificationSimple exampleVersioningVersion numbersSchema files and the $schema keyReleased versionsCommon conceptsKey naming conventionStructured dataPath references— structured data (decoded)$ — merged ERC‑7730 file@ — container (transaction / message)Path slicesValue interpolationOrganizing filesContext sectionEVM smart contract binding context (denoted 'calldata')EIP-712 messages binding context (denoted 'messages')Metadata sectionDisplay sectionStructured data format specificationField format specificationGroup format specificationSlices in pathsEmbedded CalldataReferenceContainer structure valuesEVM Transaction containerEIP-712 containerField formatsInteger formatsString formatsBytes formatsAddressInteroperable addressesAddress types and sourcesEncryption schemesRationaleHuman readabilityWallet limitationsInternationalizationUser Operations (ERC-4337)Batch transactions (EIP-5792)Extensibility to other structured data formatsCommon keywordsBackwards CompatibilityTest CasesSecurity ConsiderationsBinding contextRegistry poisoningExternal data resolutionProxy supportInterpolated intent securityEncryption supportFuture workCopyright

Compare with

Parsed from the canonical specification · discussion