This proposal extends ERC-7564 compliant smart contract wallets with an off-chain signature flow for NFT transfers, allowing wallet owners to delegate transfers via typed-data signatures presented by any relayer. The extension defines a canonical EIP-712 schema, nonce accounting, and execution requirements for compliant implementations. Unlike nft-native standards, this extension operates at the wallet level, enabling gasless transfers for any ERC-721 nft without requiring nft contract modifications.
Motivation
ERC-7564 enables programmable asset management directly in smart contract wallets but requires on-chain transactions for every NFT transfer. This creates friction for gasless use cases such as gifting, claimable drops, custodial listings, and relayer-sponsored transfers.
By implementing authorization at the ERC-7564 compliant wallet level, this extension enables gasless transfers for all ERC-721 nfts managed by the wallet, significantly expanding the reach of gasless NFT applications.
A standardized off-chain transfer signature reduces bespoke integrations and paves the way for widespread adoption of NFT-based interactions in Web3.
Specification
The key words “MUST”, “MUST NOT”, “REQUIRED”, “SHALL”, “SHALL NOT”, “SHOULD”, “SHOULD NOT”, “RECOMMENDED”, “MAY”, and “OPTIONAL” in this document are to be interpreted as described in RFC 2119 and RFC 8174.
Compliant ERC-7564 implementations that support this extension MUST include the following functions and behavior.
Interface
interface IERC8189 { function nftTransferNonce(address asset, address to) external view returns (uint256); function nftTransferWithSig( address asset, uint256 tokenId, address to, uint256 deadline, bytes calldata signature ) external returns (bool success); }
nftTransferNonceMUST return a monotonically increasing nonce scoped to(asset, to).nftTransferWithSigMUST verify the signature viaisValidSignature, reject expired signatures (unlessdeadline == 0), increment the nonce before performing the transfer, and execute the same logic asnftTransferin ERC-7564.
Implementations MUST support wallets that validate signatures through ERC-1271. Wallets MAY wrap signatures but the module MUST unwrap them prior to verification.
Typed Data
Compliant implementations MUST use the following EIP-712 typed data structure. The wallet field identifies the smart contract wallet that will execute the transfer.
| Function | Primary Type | Fields |
|---|---|---|
nftTransferWithSig |
NFTTransferWithSig |
wallet, asset, to, tokenId, nonce, deadline |
Every permit MUST use the EIP-712 domain:
name = "NFTManage Transfer"version = "1"chainIdequal to the executing chainverifyingContract = address(this)
Nonce Semantics
nftTransferNonceMUST be scoped per(asset, to).
Each WithSig function MUST increment its nonce immediately before state changes and MUST revert on signature reuse.
Execution Requirements
Implementations MUST:
- Treat
deadline = 0as non-expiring; otherwise enforceblock.timestamp <= deadline. - Recover the signer from the EIP-712 digest. Validate the digest using ERC-1271 on the wallet address. The recovered/validated signer MUST be authorized to act on behalf of the wallet (typically its owner).
- Verify the provided nonce matches the current stored nonce for the corresponding scope.
- Increment the scoped nonce before invoking the underlying ERC-7564 function.
- Emit the same events as the underlying ERC-7564 functions.
- Revert if signature validation fails, inputs mismatch, or deadlines are exceeded.
Wallets MAY offer helper wrappers, but they MUST NOT alter the semantics described above.
Rationale
- Reusing the existing ERC-7564 entry points keeps events and accounting compatible with current deployments.
- This wallet-level approach supports gasless transfers for all ERC-721 NFTs, including those without native off-chain authorization mechanisms.
Backwards Compatibility
Existing ERC-7564 implementations remain valid. Clients SHOULD feature-detect permit support by checking for IERC8189 via ERC-165 or probing the new function selectors.