Tokenomics 2.0
Introduction
The objective of this post is to present some ideas that could be implemented as part of a tokenomics update to Mars. The post will be divided into two broad sections. In the first section, we will present ideas that are relatively easier to execute and thus whose probability of being implemented (if they are well received) is higher. In the second section we will present a set of exploratory and more complex ideas whose whole implementation details might not be completely finalized, where the main motivation is to generate discussion and better understand the community’s interest around each of them.
We expect the result of the discussion around this post to be general consensus over the ideas to be implemented in the short term (first section) and those that the community is interested to see implemented (or at least keep thinking about) over a more extended time horizon (second section). For the implementation of the ideas presented in the first section, a governance vote would likely follow. For those in the second section, further posts providing more granularity and discussions might be needed before submitting them to governance votes for implementation.
Section 1
Reducing the Community Pool Size
The current community pool (CP) size is ~619M MARS. Most of these tokens are not being used or expected to be used in the short to medium term. As such, we propose to burn most of these tokens to leave only 300M MARS left in the CP. We believe these tokens should be enough to cover any short and mid-term needs of the protocol.
It is worth noting that with the deprecation of Mars Hub and the governance system moving to DAODAO, there will be no need to spend on security/validators rewards, which currently constitute a significant cost for the protocol. Historically, this cost has been paid from the CP, which further strengthens the case for reducing its size.
Improving the Fee Distribution Mechanism
In the current model, protocol fees, which are generated from interest payments within every market on the Red Bank, are distributed as follows:
- Safety Fund: 50% of fees go to the Safety Fund in the form of axlUSDC.
- Mars Stakers: 50% of fees go to Mars Hub stakers in the form of MARS.
We propose to change the distribution as follows:
-
Safety Fund: A share* of protocol fees will be used to buy nobleUSDC on the market to be sent to the Safety Fund.
-
Buy and Burn: A share* of protocol fees will be used to buy MARS on the market and burn those tokens.
-
Buy and LP: A portion* of protocol fees will be used to provide liquidity for MARS. The mechanics for LPing could work as follows:
-
50% of fees would be used to acquire MARS.
-
The remaining 50% would be used to acquire the pair token.
- This could be OSMO, NTRN, nobleUSDC or whatever governance decides. This decision should be made per outpost.
On Osmosis:
-
The MARS and pair tokens are deposited across the whole range of a MARS/PAIR 0.2% Supercharged Liquidity pool.
-
If the pool doesn’t exist it would need to be created first.
On Neutron:
- MARS and PAIR are deposited into the MARS/PAIR Astroport PCL pool.
- If the pool doesn’t exist it would need to be created first.
–
This new fee distribution methodology achieves the following:
- The buy and burn simplifies fee distribution to tokenholders and will have a deflationary effect on token supply.
- The buy and LP mechanism builds organic, protocol owned liquidity for the token, which might reduce or completely eliminate the necessity of introducing liquidity mining schemes to build up that liquidity.
- It maintains flows to the Safety Fund, which is a key component of Mars.
- The share of fees that should be allocated to each bucket are governance defined and updatable parameters.
Section 2
Implementing Staker Rebates
Users would be able to stake MARS to receive a rebate of protocol fees. The rebate could work as follows:
-
With a certain frequency (i.e. weekly, monthly), all protocol fees generated for that period are aggregated.
-
This could be done by converting all fees to nobleUSDC at the end of the period.
-
From these fees (the total accumulated by the protocol during that period), a certain % will be rebated back to users of the protocol.
- This % would be a governance defined and updatable parameter and could be as high as 100%.
-
There are 2 variables that determine the amount of fees attributable to each user as a rebate:
- The share of staked MARS the user has.
- The share of protocol fees paid by the user during the rebate period.
- And the final rebate is determined as:
Where:
- Rebate_i is the rebate attributable to user i.
- stakedMARS_i is the amount of MARS staked by user i at the beginning of the rebate period.
- totalStakedMARS is the total amount of MARS staked at the beginning of the rebate period.
- feesPaid_i are the total protocol fees* paid by user i during the rebate period. This value should be denominated in nobleUSDC.
- If the user paid fees in other assets, the conversion to nobleUSDC could be made at the end of the period.
- totalFeesPaid_t are the total protocol fees (in nobleUSDC) that were accumulated during rebate period t.
- RebatablePortion is the % of protocol fees rebateable.
Other Details:
- Unstaking Period: To be able to unstake, users would need to wait an unstaking period.
- The unstaking period would be a governance defined and updatable parameter.
Launching a Referrals Program
Referrers should be able to create their own referral code to share on any platform. When a user signs up using a given referral code, that code should be stored in the user’s account. This allows the referrer to be compensated from activity generated by the user from that moment onwards. When a referred user then uses Mars, the referrer would receive a share of the user’s paid fees.
The referral benefits (for the referrer and its referred users) would depend on a tiered system. The more activity a given referrer is able to promote, the higher the commission the referrer receives and the discount its users receive. The different tier benefits could work as follows:
-
Tier 1: X% rebate* to referrer, A% discount for users**.
-
Tier 2: Y% rebate to referrer, B% discount for users.
-
Tier 3: Z% rebate to referrer, C% discount for users.
-
The rebate means that the given % of protocol fees paid by its referred users are sent back to the referrer. Given that Mars is a complex protocol where fees could be generated from different activities such as lending and trading, it is to be defined what fees exactly could flow back to the referrer such that the system achieves its purpose but is also practical and pragmatic.
** In the same vein as the fees, it is to be defined how this discount can be applied such that it’s pragmatic. For instance, this discount could apply to certain activities (such as trading, where it’s easier to apply) and not others (such as borrowing, for instance).
And the following are some proposed requirements a referrer should meet to reach a certain tier:
- Tier 1: No requirement.
- Tier 2: At least a certain number of active users using the referral codes per week and a combined weekly volume above $X million
- Tier 3: At least a certain number of active users (higher than Tier 2) using the referral codes per week and a combined weekly volume above $Y million
The benefits, the requirements per tier and the rebate frequency should be governance defined and adjustable parameters.
Copyright
Copyright and related rights waived via CC0.
Disclaimers/Disclosures
This proposal is being made by Delphi Labs Ltd., a British Virgin Islands limited company. Delphi Labs engages in incubation, investment, research and development relevant to multiple ecosystems and protocols, including the Mars Protocol. Delphi Labs and certain of its service providers and equity holders own MARS tokens and have financial interests related to this proposal. Additionally, Delphi Labs is one of several entities associated with one another under the “Delphi Digital” brand. Delphi Digital’s associated entities and/or equityholders or service providers of such entities may hold MARS and may have financial interests related to this proposal. All such entities, service providers, equity holders and other related persons may also have financial interests in complementary or competing projects or ecosystems, entities or tokens, including MARS, Osmosis/OSMO and Neutron/NTRN. These statements are intended to disclose relevant facts and to help identify potential conflicts of interest, and should not be misconstrued as a complete description of all relevant interests or conflicts of interests; nor should they be construed as a recommendation to purchase or acquire any token or security.
This proposal is also subject to and qualified by the Mars Disclaimers/Disclosures. Delphi Labs may lack access to all relevant facts or may have failed to give appropriate weighting to available facts. Delphi Labs is not making any representation, warranty or guarantee regarding the accuracy or completeness of the statements herein, and Delphi Labs shall have no liability in the event of losses or damages ensuing from approval or rejection or other handling of the proposal. Each user and voter should undertake their own research and make their own independent interpretation and analysis of all relevant facts and issues to arrive at their own personal determinations of how to vote on the proposal.