-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
AIP1 - Tokenomics #1
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Auctus Improvement Proposal
Abstract
In this proposal we will address the unsubsidized incentive structures and token economy of the Auctus Protocol. In a second proposal we will address potential long and short term incentive usages of the reserve pool. However, understanding that the reserve pool is limited, it is important to first set timeless frameworks that will allow the project to run regardless of whether or not the reserve is full or depleted. This proposal will use mechanisms including supply sinks, buy and burn, and earnings to tie token value accrual to the usage of its on-chain options protocol.
To learn more about why we believe Auctus fits a unique market need, read our memo here.
Background
As token economy is an often misunderstood field of study, the basic premise that must be respected is this: Incentives must be aligned to maximize utility, fiscal safety, and innovation of the network.
Many networks have printed unfathomable amounts of tokens to maximize utility, at the cost of fiscal safety. A project whose token diminishes in value will soon lose its power to incentivize participants. Therefore, a healthy and growing network is generally one that sees its underlying token appreciate in value as well. Equally, to stay competitive, there should be the option for reinvestment in the network’s infrastructure.
To align incentives, we first must identify the ‘jobs’ that need to be done to make the Auctus network function:
Finally, Auctus started with a hard-capped supply, and should remain this way. Therefore this proposal will not focus on issuance, but rather token flows based on usage.
Auctus Tokenomics Overview:
1. To incentivize liquidity providers to support the fiscal safety of the network, we will double their claim to the trading fee pool, if they hold AUC.
This will be determined by the staking factor. The staking factor is a variable adjustable by the governing body on a monthly basis reflecting a percentage of the liquidity they provide. A staking factor of 1% would mean that a liquidity provider providing $100,000, would need to stake $1,000 worth of AUC to double his earnings on trading fees.
Here are three examples we find could function as a good starting point. The horizontal axis reflects price of AUC, the vertical axis reflects liquidity provided. The grid highlights what percentage of the total fully diluted supply would be staked just by LPs. Dark green highlights the combinations where there is more natural demand than available supply and price has no other way to go but up.
This way, AUC will have organic demand backed by real unsubsidized earnings.
2. To incentivize users to support the fiscal safety of the network, users will receive discounts on their trading for holding AUC.
This will be determined by the discount stake. The discount factor is a variable adjustable by the governing body on a monthly basis. A discount stake of $500 would mean that a user would need to hold $500 worth of AUC in their wallet used for trading to receive a discount on their fees. This number would be AUC denominated on a monthly basis for simplicity.
Here are three examples we find could be effective to start with. The horizontal axis reflects price of AUC, the vertical axis reflects active users holding AUC. The grid highlights what percentage of the total fully diluted supply would be staked just by users. Dark green highlights the combinations where there is more natural demand than available supply and price has no other way to go but up.
Keep in mind that one can buy options without AUC. In such a scenario the buyer would pay higher fees. Higher fees in turn result in more incentive for liquidity providers to provide options liquidity and stake AUC. One user's choice to not support the network therefore, incentivizes another user to support the network even more.
3. Finally we propose diverting 10% of fees collected into a quarterly pool that token holders can allocate to development or burn.
This quarterly pool can either be used to fund development, whether that is to accelerate growth when resources are plenty or fund development in a future where the finite reserve is running low. Alternatively should token holders choose not to allocate funds to a quarterly development project, the collected pool will be used to buy and burn AUC tokens.
This ensures that token holders have the ability to choose between improving the technology or strengthening the hardness of AUC tokens. Here’s an overview of what such a burn could look like. To ensure LPs are rewarded properly for making the platform work, we suggest a .03% fee on notional volume with a $5 minimum order fee, as known from traditional markets.
This gives an overview how many tokens may be burnt on a quarterly basis based on notional volume or number of trades. Dark green highlights the combinations where there is more natural demand than available supply and price has no other way to go but up.
These are our recommendations to create a self-sustaining, long term oriented token economic system that will encourage a positive feedback loop of security, growth and usage.
We look forward to your feedback!
In the coming weeks and months upon passing this proposal we will look towards the next steps:
DISCLAIMER:
This model is not a solicitation to buy or sell any security or token. It is strictly informational to understand the levers within Auctus Project’s token economic structure. The creators of this model hold AUC at time of sharing. This model is a proposition, and is not a current implementation at time of publication.
The text was updated successfully, but these errors were encountered: