Skip to content

docs(spec-exact-evm): clarify extra fields per assetTransferMethod and fix two→three typo#2044

Open
ryanRfox wants to merge 1 commit intox402-foundation:mainfrom
ryanRfox:docs/spec-exact-evm-extra-field-tables
Open

docs(spec-exact-evm): clarify extra fields per assetTransferMethod and fix two→three typo#2044
ryanRfox wants to merge 1 commit intox402-foundation:mainfrom
ryanRfox:docs/spec-exact-evm-extra-field-tables

Conversation

@ryanRfox
Copy link
Copy Markdown
Contributor

Description

The exact-EVM scheme spec describes three asset transfer methods (eip3009, permit2, erc7710) but documents the extra object only by example. Readers can't tell which of the extra.* fields are required, conditional, or optional for each method, as they may differ for each.

This PR:

  • Fixes a typo related to when erc7710 was added
  • Adds a per-assetTransferMethod field-classification block after each method's PAYMENT-SIGNATURE example

…d fix two→three typo

The exact-EVM scheme spec documented the extra object only by example,
leaving readers unable to tell which fields are required vs conditional
vs optional for each of the three asset transfer methods (eip3009,
permit2, erc7710). Per-method classification is authoritative in the
code but was not documented in the spec.

Adds three field-definition blocks (one per assetTransferMethod) after
each method's PAYMENT-SIGNATURE example, classifying:

  - extra.assetTransferMethod
  - extra.name
  - extra.version

Classification per method:

  - eip3009:   name and version are REQUIRED (needed for
               transferWithAuthorization signature construction).
  - permit2:   name and version are CONDITIONAL (required when the
               token supports EIP-2612 for gasless Permit2 approval).
  - erc7710:   name and version are OPTIONAL (not used by delegation-
               based transfers).

Also fixes a stale count: 'one of two asset transfer methods' →
'one of three', since erc7710 was added without updating the summary
sentence.

Pure documentation. No new fields. No code changes.
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 16, 2026

@ryanRfox is attempting to deploy a commit to the Coinbase Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions bot added the specs Spec changes or additions label Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specs Spec changes or additions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant