ERC-7770 Fractional Reserve Token Standard (Fractional Reserve Token)
Draft · Vaults & DeFi · created 2024-09-17
An interface for minting, burning, and disclosing risk information for synthetic tokens whose value is pegged to an underlying asset but where only part, not all, can be immediately redeemed for that underlying asset, with the remainder backed by other collateral.
Why it is needed
Bridged assets that cross L1 and L2 (for example, ETH on Arbitrum or WETH on BSC) can only be issued if fully backed by the underlying asset, so the only way to increase a given ecosystem's token supply is to bring more of it across the bridge. A fractional reserve approach, where tokens are issued against pledged collateral as loans, allows supply to grow more flexibly, but when various risk curators and lending markets each manage mint/burn authority and reserve ratios in their own way, token holders have no way of knowing how much of the current supply has been lent out or what fraction is immediately redeemable. Without a standard interface, wallets and apps also cannot consistently surface these risks, and it is hard to compare tokens from different issuers.
What to implement
event MintFractionalReserve(address indexed minter, address to, uint256 amount);: An event emitted when a token is minted through the fractional reserve mechanism.event BurnFractionalReserve(address indexed burner, address from, uint256 amount);: An event emitted when a token minted through the fractional reserve mechanism is burned (redeemed).event SetSegregatedAccount(address account, bool segregated);: An event emitted when a specific account is designated as a segregated account or has that designation removed.function fractionalReserveMint(address _to, uint256 _amount) external;: An authorized party mints new tokens to _to on the basis of collateral.function fractionalReserveBurn(address _from, uint256 _amount) external;: An authorized party burns _from's tokens to reduce the borrowed supply.function totalBorrowedSupply() external view returns (uint256);: Returns the total amount of tokens issued through fractional reserve minting that have not yet been redeemed.function requiredReserveRatio() external view returns (uint256);: Returns the minimum reserve ratio (in units of 1e18) that must be maintained to allow additional minting.function segregatedAccount(address _account) external view returns (bool);: Returns whether the given address is designated as a segregated account.function totalSegregatedSupply() external view returns (uint256);: Returns the sum of the token balances held by all segregated accounts.
In depth
ERC-20 extension requirement
This standard MUST be compatible with ERC-20. The IERCXXX interface is defined as inheriting from IERC20, and only mint/burn/reserve-ratio-related functions and events are added on top of existing ERC-20 functionality such as transfer and balanceOf.
State changes of the mint and burn functions
If fractionalReserveMint(_to, _amount) succeeds, totalSupply(), totalBorrowedSupply(), and _to's balance MUST all increase by _amount, and it MUST emit a MintFractionalReserve event. Conversely, if fractionalReserveBurn(_from, _amount) succeeds, the same three values must decrease by _amount, and it must emit a BurnFractionalReserve event.
Reserve ratio calculation (the source gives two formulas side by side)
The 'Reserve ratio' section defines the reserve ratio as (totalSupply() - totalBorrowedSupply() - sum of segregated account balances) / totalSupply(), and states that if this value multiplied by 1e18 is lower than requiredReserveRatio(), additional minting MUST NOT be allowed. The 'Mint and burn functionality' section, however, redefines the same reserve ratio as (totalSupply() - sum of segregated account balances) / (totalSupply() + totalBorrowedSupply()), and states that if this value multiplied by 1e18 exceeds requiredReserveRatio(), fractionalReserveMint MUST revert. The source specifies the two formulas differently, and the reference implementation follows a check in the same direction as the first formula (reserveRatio >= requiredReserveRatio).
Segregated account
At any point in time, the sum of all segregated account balances MUST equal totalSegregatedSupply(). The balance of an address designated as a segregated account is not counted as cash in the reserve ratio calculation, and as a result additional tokens cannot be minted on the basis of money that has gone into a segregated account. This is a mechanism to prevent supply growth from being distorted when DAO voting power or dividends are tied to token holdings.
Mint/burn authority and collateral requirements
fractionalReserveMint and fractionalReserveBurn SHOULD only be callable by an authorized address, for example a risk curator or a lending market. These SHOULD only mint new tokens to addresses that have already locked collateral in a dedicated contract. The standard does not specify this authorization or collateral valuation method itself; it leaves the token holder responsible for the trustworthiness of the entity granted minting rights.
Interest revenue distribution
Tokens lent out via fractionalReserveMint SHOULD be used alongside lending operations, that lending SHOULD bear interest, and a portion of the interest revenue SHOULD be distributed to token holders rather than a segregated account. The distribution method is not specified by the standard; it notes this could be done by making the token a rebasing token or by paying out via staking or airdrops.
Supply structure when used standalone
A fractional reserve token can also be used standalone, without being pegged to a known underlying asset like DAI. In this case the initial supply is fixed, but additional supply can be borrowed, and even when supply temporarily increases, net holdings (totalSupply() - totalBorrowedSupply()) remain unchanged.
Proposal status
This standard is currently in Draft status, not yet finalized, and is a proposal whose content may change or be abandoned.
Things to watch out for
- Economic risk is out of scope for the standard: Fractional reserve banking carries various economic risks such as insolvency or bank runs, but the standard explicitly states it does not provide guidelines for managing such risks.