ERC-8114: NFT Transfer With Signature

Abstract

This proposal extends 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

Wallets require 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.

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 smart contract wallets that wish to support this extension MUST implement the IERC8114 interface (in addition to ERC-165 for interface detection and ERC-1271 for signature validation).

Interface

interface IERC8114 {
    function nftTransferNonce(address asset, uint256 tokenId) external view returns (uint256);

    function nftTransferWithSig(
        address asset,
        address to,
        uint256 tokenId,
        uint256 deadline,
        bytes calldata signature
    ) external returns (bool success);
}

• nftTransferNonce MUST return a monotonically increasing nonce scoped to (asset, tokenId).
• nftTransferWithSig MUST verify the signature using isValidSignature, reject expired signatures (unless deadline == 0), verify the nonce, increment the nonce before the transfer, and execute IERC721(asset).safeTransferFrom(address(this), to, tokenId).

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.

Every permit MUST use the EIP-712 domain:

• name = "ERC8114 NFT Transfer"
• version = "1"
• chainId equal to the executing chain
• verifyingContract = address(this)

Nonce Semantics

• nftTransferNonce MUST be scoped per (asset, tokenId).

Each WithSig function MUST increment its nonce immediately before state changes and MUST revert on signature reuse.

Execution Requirements

Implementations MUST:

1. Treat deadline = 0 as non-expiring; otherwise enforce block.timestamp <= deadline.
2. 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).
3. Verify the provided nonce matches the current stored nonce for the corresponding scope.
4. Increment the scoped nonce before invoking the underlying ERC-721 function. The nonce MUST remain incremented even if the downstream NFT transfer call reverts.
5. 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-721 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

Clients can detect permit support by checking for IERC8114 via ERC-165 or probing the new function selectors.

Security Considerations

• Improper nonce handling can enable signature replay if a failed downstream transfer leaves the signature reusable. Implementations must ensure nonce updates occur before invoking external NFT transfer logic.
• Wallet owners should use bounded deadlines to reduce the risk of long-lived signatures.

Copyright

Copyright and related rights waived via CC0.