ERC-1080 Loss and theft recovery tokens (Recoverable Token)

Stagnant · Tokens · created 2018-05-02

A standard that extends ERC-20 and ERC-721 so that an account can go through a recovery process if it is lost or stolen, or so a transfer can be chargebacked within a certain time window.

Why it is needed

On Ethereum, there is no protocol-level way to undo a lost private key or a stolen account. According to the original Motivation, the Ethereum protocol itself should not be modified because of losses, theft, or disputes, but that does not mean the resulting harm must simply be left unaddressed. Without a common standard for solving this at the smart contract layer, a user whose tokens are stolen or mistakenly sent has no path to recourse, and every service ends up building its own ad hoc workaround.

What to implement

In depth

Loss reporting and recovery process (claimLost / cancelLostClaim)

Calling claimLost(lostAccount) reports that address as lost and triggers the AccountClaimedLost event. Once the time set in getLostAccountRecoveryTimeInMinutes has passed, the implementer must provide a process that determines the rightful owner and moves the tokens to a new account, triggering the AccountRecovered event once recovery is complete. If the recovery process has not yet started, cancelLostClaim can be called to cancel the loss report, triggering the AccountClaimedLostCanceled event. Once the recovery process has already begun, it cannot be canceled.

Theft reporting and account freezing (reportStolen)

Calling reportStolen reports msg.sender's current account as stolen, triggers the AccountFrozen event, and freezes that account's tokens. The implementer must provide a mechanism to determine the rightful owner and transfer the tokens, triggering the AccountRecovered event once recovery is complete.

Chargebacks and pending transfers (chargeback / PendingTransfer)

chargeback(pendingTransferNumber) requests the reversal of a specific pending transfer on behalf of msg.sender. The implementer must provide a mechanism to determine the rightful owner of the disputed tokens and move them to the correct account, and this request must respect the chargeback waiting period set via setPendingTransferTimeInMinutes. In the process, the PendingTransfer, ChargebackRequested, and Chargeback events are recorded at the moment the pending transfer occurs, the chargeback is requested, and the actual reversal happens, respectively.

Per-account waiting period settings

getPendingTransferTimeInMinutes/setPendingTransferTimeInMinutes query and set the time window during which an account can chargeback a transfer. The time cannot be changed while a transfer is pending. getLostAccountRecoveryTimeInMinutes/setLostAccountRecoveryTimeInMinutes query and set how long must be waited before a loss dispute can begin, and cannot be changed while a dispute is open. Each account can adjust its own waiting periods.

Opt-in structure

According to the original Rationale, this standard aims to provide a safeguard that users or contracts can optionally adopt when they choose to. Whether to use a recoverable token and how to structure the dispute resolution process are left to the implementer's choice, premised on the idea that the Ethereum protocol itself should not be modified because of loss, theft, or disputes.

Status

This proposal has Stagnant status, meaning it is no longer being advanced and has stalled. The Implementation item is also marked Pending, so no concrete implementation is given in the source.

Original ERC · ← ERCs