The Draft proposal combines a recipient, amount, validity window and random nonce. A signature and a completed transfer remain different records.

What the primary record establishes

ERC-3009, created on 28 September 2020, is labelled Draft in the official EIP repository. It describes signed authorizations for fungible-token transfers and uses random 32-byte nonces, unlike the sequential nonce approach discussed for ERC-2612. Ethereum EIPs — ERC-3009: Transfer With Authorization, Draft ↗

An authorization specifies the sender, recipient, value, validAfter, validBefore and nonce. The receiveWithAuthorization variant requires the caller to be the payee, a restriction relevant when a transfer is combined with another action. Ethereum EIPs — ERC-3009: Transfer With Authorization, Draft ↗

What the distinction changes

The practical distinction is scope. A transfer authorization describes a particular movement with stated conditions. An allowance belongs to a different authorization pattern, where a spender can draw within the approved limit.

A wallet displaying “signed” has therefore not necessarily shown an executed transfer. Submission, contract checks and inclusion still matter. An unused signature and an on-chain balance change should not share one undifferentiated status.

What to check before drawing a conclusion

WFN’s review points are the token contract, destination, amount, time window, nonce state and signing domain. A familiar token symbol is not enough to identify the contract the user is authorizing.

The proposal’s status should be stated accurately, and support checked for the particular implementation. ERC-3009 is neither a newly launched 2026 network feature nor a guarantee that every ERC-20 token accepts this authorization format.