ERC-7968 Owner-authorized token transfer protocol

Draft · Tokens · created 2025-06-11

An ERC-20 token transfer standard in which a payment facilitator pays gas on the owner's behalf and processes token transfers, while ensuring only transfers authorized by the owner's signature are executed.

Why it is needed

To use token-based payments, companies or ordinary users typically have to manage their own wallet, pay gas fees, and handle transactions themselves. For non-crypto businesses or users unfamiliar with cryptocurrency, this technical and operational burden becomes a barrier to adoption. Conversely, if a payment processor tries to handle this on their behalf, it must either custody the tokens directly or receive delegated authority over them, which blurs the boundary of ownership and creates the risk that the processor could move funds arbitrarily. There is also no standard for whether the user has pre-approved a given transfer, or for how to recover assets if the processor stops responding. Without such a standard, each company has to design its own delegation structure and safeguards from scratch.

What to implement

In depth

Proposing a transfer: proposeTransaction

The payment processor (paymentProcessor/transactionProvider) proposes a transfer by passing tokenAddress, amountToSent, and destinationAddress. The proposal is stored in the contract, a unique uint256 hash is generated for use in the approval process, and that hash is recorded on-chain via the TransactionProposed event.

Signature-based execution: completeTransaction

The payment processor calls this with the proposal's hash and the owner's signature. The signature is produced by signing a message containing just the hash with the owner's private key. Inside the function, the signature is verified as valid and belonging to the token owner; once it passes, the tokens are transferred to the destinationAddress recorded in the proposal, and a TransactionCompleted event is emitted.

Signature verification: verifySignature

A pure function that takes _signer, tokenAddress, amountToSent, destinationAddress, and signature, and returns a bool indicating whether that signature was signed by _signer for those terms. The owner can call it directly to verify before handing a signature to the processor, and it must also be used inside completeTransaction as a verification step before executing the transfer.

Proposal expiration time

According to the Abstract, each proposal includes an explicit expiration time, so that if a signature is not submitted and verified within the set validity period, the proposal becomes invalid and the transfer cannot be executed. However, this expiration mechanism is not concretely reflected in the function signatures or parameters in the Specification section.

Safeguard: sendFundsToOwner

A function callable only by the owner, which transfers the contract's entire balance of a specified tokenAddress to the owner's own address. It serves as a safeguard for the owner to reclaim assets if the payment processor stops responding, behaves improperly, or if external conditions such as gas costs turn unfavorable, and it emits a FallbackScenarioExecuted event upon execution.

Off-chain compensation structure

The payment processor bears all on-chain transaction costs, including gas fees, and is compensated off-chain (e.g., in fiat currency). The owner must cryptographically sign and approve every transfer, and retains explicit on-chain ownership of the assets at all times.

What remains unresolved

This proposal is in Draft status; the Rationale section is left as 'tbd', and Security Considerations only states 'Needs discussion.' Reference implementation and test cases have not yet been written either, so the detailed behavior and safety review may still change or be added to.

Original ERC · ← ERCs