ERC-7641 Built-in Revenue Sharing Token (Intrinsic RevShare Token)
Draft · Tokens · created 2024-02-28
An extension standard that builds revenue sharing functionality into ERC-20 tokens. At each snapshot, holders can claim their share of ETH from a common revenue pool, and by burning tokens they can immediately redeem their share of the pool.
Why it is needed
Many projects raise funds by issuing tokens, but an ordinary ERC-20 token is not directly tied to the revenue the project earns. Since holders receive no share, there is little reason to hold the token long term, and there is no minimal mechanism backing the token's value. In particular, open source projects and open source AI models have no good way to turn contributions into money, which weakens the motivation of both contributors and organizations. This standard pools revenue arriving from multiple sources into a single common revenue pool, making the token itself represent a share of that pool. Holders can claim a portion of the revenue at each cycle, and if they wish, they can burn the token to immediately withdraw their share from the pool. Thanks to this burn mechanism, as long as there is money in the pool, the token's value is guaranteed to be at least equal to its share of the pool.
What to implement
function claimableRevenue(address account, uint256 snapshotId) external view returns (uint256);: Calculates and returns the amount of ETH that a given address can claim at a specific snapshot.function claim(uint256 snapshotId) external;: Claims one's share of ETH based on the token balance at that snapshot.function snapshot() external returns (uint256);: Records the token balance and the claimable revenue balance, and returns the snapshot number.function redeemableOnBurn(uint256 amount) external view returns (uint256);: Calculates the amount of ETH that would be returned when burning amount tokens.function burn(uint256 amount) external;: Burns the token and redeems the corresponding revenue.function claimableERC20(address account, uint256 snapshotId, address token) external view returns (uint256);: An optional extension function that calculates the amount claimable in a specific ERC-20 revenue token at a specific snapshot.function redeemableERC20OnBurn(uint256 amount, address token) external view returns (uint256);: An optional extension function that calculates the amount to be returned in a specific ERC-20 revenue token upon burning.
In depth
Required interface and basic structure
A compliant contract MUST implement both the IERC7641 and ERC-20 interfaces. The token represents a share of a common revenue pool into which money from multiple revenue sources flows. The interface consists of five functions. claimableRevenue is a view function that calculates the amount of ETH a holder can claim at a specific snapshot, and claim is the function that actually receives that share. snapshot records the token balance and claimable revenue balance and returns a snapshotId. redeemableOnBurn is a view function that calculates the ETH to be returned upon burning, and burn is the function that burns the token and redeems the corresponding revenue.
Snapshot-Based Revenue Distribution
Revenue distribution is done per interval between two consecutive snapshots. In the reference implementation example, the revenue between two snapshots is denoted R, the distribution ratio p (0% to 100%), and pR is divided according to token holding ratio. The ETH a holder with amount tokens can claim is pR * amount / totalAmount. The remaining (1-p)R stays in the pool and can only be withdrawn through burning. Each holder can claim only once per snapshot, which guarantees a fair distribution. snapshot must be called periodically, and the source specifies that a require check should be in place to prevent DDoS attacks.
Burn and Redemption Calculation
A holder can burn up to the full amount of tokens they hold. The redemption formula in the reference implementation example is redeemableETH = amount / totalSupply * totalRedeemableETH. totalSupply refers to the total token supply, and totalRedeemableETH refers to the total ETH in the burn pool. Burning reduces the total supply, creating a deflationary structure, and once a token is burned it can no longer participate in future revenue distributions. Thanks to this mechanism, as long as the revenue pool is not empty, the token's value is maintained at or above its share of the pool. redeemableOnBurn is defined as a view function to reduce gas costs.
Optional Extension AltRevToken
The base standard treats ETH as revenue, but implementing the OPTIONAL AltRevToken extension allows other ERC-20 tokens to be accepted into the revenue pool as well. The interface is named IERC7641AltRevToken and inherits from IERC7641. claimableERC20 calculates the amount claimable in a specific revenue token (token address) at a specific snapshot, and redeemableERC20OnBurn calculates the amount to be returned in that token upon burning.
IMO and Open Source Fundraising
The source presents the IMO (Initial Model Offering) as a use case. Open source AI models and organizations that struggle to monetize can use this token to raise funds and continue development, distributing tokens to active contributors to turn project participation into a tangible asset. Afterward, when a project using that open source model pays a set fee into the revenue pool, a distribution structure runs in which token holders claim a proportional share. The source explains that this revenue sharing serves as a mechanism guaranteeing holders long-term returns, driving sustained participation in the open source AI community.
Compatibility and proposal status
This standard adds a new interface on top of existing functionality, so it is backward compatible with ERC-20. The reference implementation is located under contracts/ in the repository, and the corresponding unit tests are under test/. However, this proposal is in Draft status, registered on February 28, 2024, and its content may change or progress may stall going forward. The latest source should be checked before implementing it.
Things to watch out for
- Liquidity Risk of the Deflationary Model: If burning continuously reduces the token supply, it can affect liquidity, increasing volatility and leaving the token vulnerable to price manipulation. The source recommends verifying through sufficient stress testing and market simulation that the system holds up under various scenarios.
- Spam Revenue Tokens: The AltRevToken extension allows multiple revenue tokens to be added, but if large numbers of worthless spam tokens are added, the gas cost of the burn and claim processes increases and can discourage user participation. The source stresses that only reputable, valuable tokens should be added, through transparent governance involving community voting, security audits, and review of gas cost impact.