Algorithmic stable coin protocols & in particular elastic supply tokens (e.g. AMPL, Base) have emerged as contenders for decentralized price-stable assets. The premise of such tokens is to convert price-volatility into supply-volatility, in search of a price peg (e.g. 1 USD)
$DEBASE - A Composable/Modular Algorithmic Stable Coin Protocol
https://t.co/v3383S9VsP
https://t.co/mAul2JSyWE
A guest post, written by the Debase community.
Algorithmic stable coin protocols & in particular elastic supply tokens (e.g. AMPL, Base) have emerged as contenders for decentralized price-stable assets. The premise of such tokens is to convert price-volatility into supply-volatility, in search of a price peg (e.g. 1 USD)
The idea is that at sufficiently large market capitalisations supply-volatility will taper off and you are left with a price-stable asset. So far this has not been the case
Projects like Ampleforth continue to experience sustained price and supply volatility even as market capitalisation has ballooned. Subsequent iterations have tried to improve on this model by modifying one or more of the static parameters; BASE, RMPL etc., come to mind
While the subsequent iterations modified a fixed set of ‘flexible’ parameters, the fundamental mechanism of elastic supply tokens remains static. Debase is the first elastic supply token to introduce completely dynamic parameters (16+).
Debase is the most dynamic algorithmic stable coin:
1. A composable and modular protocol
2. Infinite iteration and experimentation, virtually any DeFi composition is possible, mediated through Debase’s in-built gov. layer
3. Over 16 dynamic parameters
4. Composability w/ a wide range of DeFi elements appeals to the full spectrum of stakeholders in the DeFi ecosystem, including but not limited to yield farmers, options traders, other stable coins/DeFi projects who can build "stabilizer pools".
5. Stabilizer pools (s-pools)
S-pools act as plugins that add additional logic/function, to stabilize $DEBASE, to the core protocol. Ecosystem participants are incentivized to coordinate & ensure Debase gravitates to a peg. It is only limited by smart contract capability & what governance permits
Given the infinitely modular nature of Debase, It can absorb innovative new ideas in its stride as it evolves and matures. S-pools with various, unique strategies will sit on a spectrum of passive to active designs
Passive S-pools:
These do not have an active agent of stabilization, and rely on pure game theory to stabilize supply (and therefore price).
For example, a S-pool that rewards stakers with $DEBASE if there are less than 'n' number of negative rebases over m time periods
Active S-pools:
These have an active agent of stabilization, for example a S-pool that acts as a yield vault. This vault may take $DEBASE/DAI LP tokens or assets as capital, use a yield farming strategy and set aside part of the profits to peg $DEBASE to its target price
S-pools will exist on a spectrum between the two extreme types of pools (active and passive).
Debase needs to attract as many diverse strategists as possible - to this end it is already working on onboarding these stakeholders to governance e.g. 88MPH - governance partner.
How can all the active/passive S-pools coordinate to stabilise $DEBASE, despite their varied interests? Aligned incentives. Debase’s incentive structure enables governance ($DEGOV) to share protocol profits in DAI/other assets in treasury when $DEBASE is stable
Governance plays an important role in growth & stabilization. Because governance can be rewarded for driving utility, governance partners are incentivised to ulitilize Debase as a stable reserve. Large DeFi protocols, once onboarded to governance, can push for stable utility
More from Crypto
Where should I start?
1) Is Blockfi profitable?
2) How much money does BlockFi have on its balance sheet?
3) Is the yield that BlockFi pays to its depositors earned or subsidized by billionaire investors?
4) Has BlockFi ever been profitable?
5) Are you planning to go public?
1) Is Blockfi profitable?
2) How much money does BlockFi have on its balance sheet?
3) Is the yield that BlockFi pays to its depositors earned or subsidized by billionaire investors?
4) Has BlockFi ever been profitable?
5) Are you planning to go public?
When is the interview published? @otisa502
— Jakob.Cel (@HedegaardJakob) February 14, 2021
You May Also Like
A brief analysis and comparison of the CSS for Twitter's PWA vs Twitter's legacy desktop website. The difference is dramatic and I'll touch on some reasons why.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.
Legacy site *downloads* ~630 KB CSS per theme and writing direction.
6,769 rules
9,252 selectors
16.7k declarations
3,370 unique declarations
44 media queries
36 unique colors
50 unique background colors
46 unique font sizes
39 unique z-indices
https://t.co/qyl4Bt1i5x
PWA *incrementally generates* ~30 KB CSS that handles all themes and writing directions.
735 rules
740 selectors
757 declarations
730 unique declarations
0 media queries
11 unique colors
32 unique background colors
15 unique font sizes
7 unique z-indices
https://t.co/w7oNG5KUkJ
The legacy site's CSS is what happens when hundreds of people directly write CSS over many years. Specificity wars, redundancy, a house of cards that can't be fixed. The result is extremely inefficient and error-prone styling that punishes users and developers.
The PWA's CSS is generated on-demand by a JS framework that manages styles and outputs "atomic CSS". The framework can enforce strict constraints and perform optimisations, which is why the CSS is so much smaller and safer. Style conflicts and unbounded CSS growth are avoided.