HomeEIPs
EIPsERC-1080
ERC-1080

Recoverable Token

StagnantStandards Track: ERC
Created: 2018-05-02
Bradley Leatherwood <bradleat@inkibra.com>
DiscussionsOriginal linkEdit
1 min read

ERC-1080 is a standard interface for tokens on the Ethereum blockchain that allows for the implementation of a standard API for tokens extending ERC-20 or ERC-791. This standard provides basic functionality to recover stolen or lost accounts, as well as provide for the chargeback of tokens. The RecoverableToken method includes claimLost, cancelLostClaim, and reportStolen, which trigger events and freeze tokens in the event of theft or loss. The purpose of this standard is to mitigate the effects of reasonably provable token or asset loss or theft and to help resolve other conflicts without modifying Ethereum's protocol. The ERC-1080 standard aims to provide a standardized format for fund recovery EIPs and an objective standard by which to measure future proposals. Each ethereum recovery proposal (ERP) will reference this EIP and follow the guidelines set out here. The purpose of each ERP is to clearly describe the issue to be corrected, describe why an irregular state change is both necessary and justified, and demonstrate that the proposed actions will achieve the ERP's objectives. Each ERP will be required to use a standard format to represent the set of proposed state changes and must include a verification script that can reliably generate those changes.

Video
Anyone may contribute to propose contents.
Go propose
Original

Simple Summary

A standard interface for tokens that support chargebacks, theft prevention, and lost & found resolutions.

Abstract

The following standard allows for the implementation of a standard API for tokens extending ERC-20 or ERC-791. This standard provides basic functionality to recover stolen or lost accounts, as well as provide for the chargeback of tokens.

Motivation

To mitigate the effects of reasonably provable token or asset loss or theft and to help resolve other conflicts. Ethereum's protocol should not be modified because of loss, theft, or conflicts, but it is possible to solve these problems in the smart contract layer.

Specification

RecoverableToken

Methods

claimLost

Reports the lostAccount address as being lost. MUST trigger the AccountClaimedLost event.

After the time configured in getLostAccountRecoveryTimeInMinutes the implementer MUST provide a mechanism for determining the correct owner of the tokens held and moving the tokens to a new account.

Account recoveries must trigger the AccountRecovered event.

function claimLost(address lostAccount) returns (bool success)

cancelLostClaim

Reports the msg.sender's account as being not being lost. MUST trigger the AccountClaimedLostCanceled event.

MUST fail if an account recovery process has already begun.

Otherwise, this method MUST stop a dispute from being started to recover funds.

function claimLost() returns (bool success)

reportStolen

Reports the current address as being stolen. MUST trigger the AccountFrozen event. Successful calls MUST result in the msg.sender's tokens being frozen.

The implementer MUST provide a mechanism for determining the correct owner of the tokens held and moving the tokens to a new account.

Account recoveries must trigger the AccountRecovered event.

function reportStolen() returns (bool success)

chargeback

Requests a reversal of transfer on behalf of msg.sender.

The implementer MUST provide a mechanism for determining the correct owner of the tokens disputed and moving the tokens to the correct account.

MUST comply with sender's chargeback window as value configured by setPendingTransferTimeInMinutes.

function chargeback(uint256 pendingTransferNumber) returns (bool success)

getPendingTransferTimeInMinutes

Get the time an account has to chargeback a transfer.

function getPendingTransferTime(address account) view returns (uint256 minutes)

setPendingTransferTimeInMinutes

Sets the time msg.sender's account has to chargeback a transfer.

MUST NOT change the time if the account has any pending transfers.

function setPendingTransferTime(uint256 minutes) returns (bool success)

getLostAccountRecoveryTimeInMinutes

Get the time account has to wait before a lost account dispute can start.

function getLostAccountRecoveryTimeInMinutes(address account) view returns (uint256 minutes)

setLostAccountRecoveryTimeInMinutes

Sets the time msg.sender's account has to sit before a lost account dispute can start.

MUST NOT change the time if the account has open disputes.

function setLostAccountRecoveryTimeInMinutes(uint256 minutes) returns (bool success)

Events

AccountRecovered

The recovery of an account that was lost or stolen.

event AccountClaimedLost(address indexed account, address indexed newAccount)

AccountClaimedLostCanceled

An account claimed as being lost.

event AccountClaimedLost(address indexed account)

AccountClaimedLost

An account claimed as being lost.

event AccountClaimedLost(address indexed account)

PendingTransfer

A record of a transfer pending.

event PendingTransfer(address indexed from, address indexed to, uint256 value, uint256 pendingTransferNumber)

ChargebackRequested

A record of a chargeback being requested.

event ChargebackRequested(address indexed from, address indexed to, uint256 value, uint256 pendingTransferNumber)

Chargeback

A record of a transfer being reversed.

event Chargeback(address indexed from, address indexed to, uint256 value, uint256 indexed pendingTransferNumber)

AccountFrozen

A record of an account being frozen. MUST trigger when an account is frozen.

event AccountFrozen(address indexed reported)

Rationale

  • A recoverable token standard can provide configurable safety for users or contracts who desire this safety.
  • Implementations of this standard will give users the ability to select a dispute resolution process on an opt-in basis and benefit the community by decreasing the necessity of consideration of token recovery actions.

Implementation

Pending.

Copyright and related rights waived via CC0.

Further reading
Anyone may contribute to propose contents.
Go propose
Adopted by projects
Anyone may contribute to propose contents.
Go propose

Not miss a beat of EIPs' update?

Subscribe EIPs Fun to receive the latest updates of EIPs Good for Buidlers to follow up.

View all
Serve EIP builders, scale Ethereum.
Resources
GitHub
Supported by