Summary
Objective of this proposal is to create a new decentralized AFT which can automatically be pegged to 1$ and defend the peg value during market volatility.
Motivation
Terra’s core existence was based on the idea of decentralized money. Though the initial creation of UST (currently USTC) has failed to succeed, it is not the end of road for decentralized money. New attempts are made by several users to create decentralized money and this is one such idea towards it.
INTRODUCTION
As mentioned above, Terra’s core existence was based on the idea of decentralized money. Though the initial creation of UST (currently USTC) has put the community in lot of troubles due to the de-peg event, there are lots of discussion, time and research spent on repegging USTC to $1 by several community members. I want to put forth the below points of concern before I discuss on my proposal.
-
There are several community members who advocate that it is highly unlikely to generate sufficient funds to repeg to 1$ (through any sources like fund raising / self-initiative burn / others). Have made attempts with few logics on the possibilities of repeg to 1$ and due to huge bad debts none of my attempts were fruitful. Though I am not ruling out the possibility of repegging USTC to $1, which can be brought to the table by bright minds in the community, I couldn’t arrive at any possible solutions for the same.
-
There are large amounts of USTC held by whales as the current top 10 USTC holders hold a significant amount compared to the rest of the market. Even if we end up with a solution of 1$ repeg, it is highly likely that whales with sell USTC and exit the market with good profits and the small holders will again pay the price of losing their hard-earned money. I see this as yet another risk and not in favor of working on the current USTC. Besides that, there are unforeseen legal implications for which I don’t have any insights to it.
-
Luna Classic is now a community owned chain and working towards achieving decentralization at its highest level possible. Hence, I am in favor of a decentralized community owned coin. The idea of UST was created as decentralized community owned coin, however, the current situation of USTC has created uncertainty on USTC decentralization. This leads us to the question, what is the way forward?
After careful consideration, I have arrived at the conclusion to move away from USTC for the above 3 reasons. I would suggest to create a new community coin as the way forward for the betterment of rejuvenated LUNC community.
ALGORITHMIC FUNGIBLE TOKEN — COMMUNITY TERRA (CUST)
Crypto prices are derived based on supply and demand which leads to high volatility (speculative pump and selloff) where volume also plays a crucial role in fear of missing out (FOMO). However, objective of the new AFT should be decentralized and not have volatility irrespective of volume, supply and demand. In order to overcome these challenges, I propose that the AFT be adequately backed up with a digital asset. There were proposals initiated by “Alex Foreshaw” earlier, by creating a backup fund with BTC (twBTC), however, I propose to create a backup with the native asset (LUNC) which will also serve the purpose of its very own existence in first place.
Yes, you read it RIGHT. I mentioned LUNC as the asset which should back up the new AFT (CUST). The first question everyone will have is “Why should LUNC be considered as the back up asset when LUNC itself is on life support?” LUNC (formerly LUNA) was the native asset to back the UST but the flawed design led to the death spiral and crashing of the coin. With a modified approach, LUNC can act as a savior and add more value to the chain. This will create more demand to the coin and will also stay decentralized. To control crypto volatility (to a practically possible extent), I propose a pool be created where funds will be accumulated to control volatility. This pool will release funds whenever there is high volatility and so that the AFT stays pegged to 1$ to a maximum possible period. Incase of a de-peg, measures are in place so that it gets pegged as early as possible.
Being decentralized, if Bitcoin can be considered as a standalone store of value without dependency on any assets (like FIAT, gold, digital et al.) why cant LUNC thrive as standalone asset like bitcoin when the chain is decentralized. That’s the very same reason of considering LUNC as backup asset. LUNC will only fail when there are no utilities to the chain, which is the one of the primary reason why a new AFT is required at this point in time to add more value and benefits to the community members.
PROPOSAL
As part of the proposal 5234, tax was reduced to 0.2% and 10% of the collected seigniorage gets added to the community pool at the end of the epoch. The rest 90% of the tokens are not regenerated as it is burnt based on community decision. Objective of this text proposal is to utilize the burn tax funds to mint new Algorithmic Fungible Tokens with proper reserves and refill Oracle pool rewards. New pools are to be created and the funds should be distributed as below from the current tax rate of 0.2%.
-
Community Pool — 10%
-
Reserve Pool — 10%
-
Oracle Rewards Pool — 20%
-
AFT Pool — 60%
Community Pool — 10% (No Changes)
Reserve Pool — 10%
10% of the tax volume should be sent to LUNC Reserve Pool. Until DEX is operational in LUNC chain, funds will be accumulated in LUNC. Once DEX is operational, LUNC should be periodically converted to BTC, ETH, BNB which will act as a backup for buy back and burn at a later stage. Funds will be divided equally based on the number of coins chosen in Reserve Pool. To start with, we can go with the top 3 coins of BTC, ETH, BNB. More alt coins, if required, can be added at a later stage.
During bull run / when the reserve coin domination against LUNC is high, LUNC will be bought back and burnt through a governance proposal with 50% of the reserve funds. These reserves will also back up during any market conditions when LUNC is weak. Hence maintaining a reserve pool becomes a necessity for the chain’s long-term growth.
Oracle Rewards Pool — 20%
Oracle Rewards are slowly depleted and needs to be refilled at some stage. Allocating 20% of coins from tax will replenish the rewards pool and encourage more users to stake. In addition to the portion of rewards from tax, the to be created Algorithmic Fungible Tokens (AFT)* will also be sent to the rewards pool which will be discussed in the next few pages. These AFTs will also be distributed as staking rewards.
If ORD is to be funded by other means, this 20% of 0.2% tax should be directly credited to Volatile Control Funds and will remain out of circulation.
AFT Pool — 60%
The most important section of this text proposal is the AFT Pool. AFT Pool (60% of tax funds) is further segregated into 3 sub-pools. Break-up % for the pools is as below.
-
Volatile Control Funds (VCF) — 60%
-
LUNC Collateral Funds (LCF) — 20%
-
CUST Pool — 20%
The purpose of creating 3 pools is that the 1st pool (VCF) will act as volatility controller which will play a vital role in rebalancing the peg value on 1:1 basis. The 2nd (LCF) and 3rd pool (CUST) will have the same % of funds flowing in the respective pools so that $ value remains 1:1 at the time of allocation. VCF Funds will start to rebalance any LUNC price variations as its only existence is to control the price variations and keep the peg value on 1:1 basis.
**‘x’ amount of LUNC equivalent to 1 $US = 1 CUST
Let me share a sample calculation of the tax amount distribution & AFT pool usage with the below data.

Table 1 — Transaction and Burn Tax Volume

Table 2 — Proposed Tax Funds breakup in lieu of LUNC Burn

Table 3 — Community Terra (CUST) Generation

Table 4 — VCF rebalancing CUST pool when LUNC price increases from $0.00017

Table 5 — VCF rebalancing LUNC Collateral pool when LUNC price decreases from $0.00017
As seen above in table 4 & 5, VCF releases funds to LCF / to mint CUST (by burning LUNC) during price fluctuations in order to retain the peg. Lets check the scenario what happens during price pumps 35X and immediately drops 90%. 35X price pump is explained in table 4. CUST will remain pegged in normal market conditions and control volatility to a practically possible extent. The scenario here describes extreme market conditions. CUST cannot hold the 1$ value in such extreme market conditions and this is temporary as there will be continuous inflow of funds to VCF based on transactions and it will start distributing funds to LCF to balance the peg. Eventually, it will return back to 1$ in some time. The temporary de-peg time is based on the amount of LUNC deficiency in LCF to retain the peg value.
With the current proposal (and assuming both pump and selloff happens before next epoch, i.e. no refilling of funds to VCF), VCF will be drained to from 48.68M to 0 and a bad debt of $100K will remain. LCF will have 72M. As such CUST price will be $0.3 when this happens. The below calculation is considering that LUNC directly drops from $0.006 to $0.0006. As the pump and selloff is going to happen in stages (even if it is calculated hourly), CUST price is definitely expected to be more than $0.3.

Table 6–90% Drop after LUNC Price pump
The reason why I mention the de-peg to be temporary is that VCF will consistently receive funds every epoch which in-turn will be transferred to LCF to fulfil the LUNC deficit of 163M (~$100K) or lesser. In the mean-time if LUNC price starts to increase, the LUNC deficit will start to decrease thereby increasing CUST value. Until CUST is repegged to $1 this will continue to happen.
In addition, we can send LUNC to VCF from community pool, use the reserves funds in BTC/ETH/BNB to buy back CUST from open market and do a burn, burn CUST in ORD pool until CUST is repegged back to 1$. If anyone does voluntary funding to VCF (like the current voluntary burn), the entire amount will be sent to VCF instead of splitting 60:20:20. Meaning VCF will have more LUNC than 3 times the value and will be able to stabilize the downfall. The final CUST price in such scenario will definitely a lot more than $0.3. Leaving it for financial experts’ opinion.
To minimize the risk of hyper minting CUST during LUNC price pumps and to defend the peg incase of huge selloffs, we need additional control mechanism.
Volatile Control Risk Limit (VCRL)
VCRL factor is set to determine the acceptable LUNC price variation limit during market volatility for minting CUST. Reason for introducing this factor is to avoid over minting CUST during toxic price pumps thereby reducing the risk of de-peg during market huge selloffs. Factoring 2 components, current LUNC price and lowest of last 3-day LUNC price to determine the VCRL factor and comparing the price variations of current LUNC price against the lowest of last 3-day LUNC price.
Below is the observation for the period Jun 1, 2022 to Nov 23, 2022 (Source of LUNC Price: Coinmarketcap)

Table 7 — Price variation comparison of current LUNC price against the lowest of last 3-day LUNC price
Assuming LUNC Market Close price to be Current Price:
34 out of 176 days had a price increase of more than 1.2X against the lowest of last 3-days price.
Assuming LUNC Market High Price to be Current Price:
56 out of 176 days had a price increase of more than 1.2X against the lowest of last 3-days price.
Based on the above analysis, VCRL factor is set as 1.2
My previous article (Community Terra — CUST) was based on the fact that irrespective of LUNC price increase, VCF will start burning LUNC and mint CUST to retain the peg. However, to avoid over minting CUST during price pumps and to reduce the risk of de-pegging during huge LUNC selloffs, introducing the VCRL into the play.
Acceptable VCRL: Current Price Variations up to 1.2X of last 3-day lows
VCF will burn LUNC and mint CUST equivalent to the total value of LCF funds. CUST will have a healthy mint within acceptable volatility range.
Extreme VCRL — Current Price Variations above 1.2X of last 3-day lows
VCF should not mint CUST as this is the RED ZONE which could lead to undesirable minting volume. To retain the peg and not to allow CUST price go beyond 1$, LCF funds should start burning LUNC (without minting CUST) to meet the equivalent value CUST holdings. i.e. LCF will start to offload its excess holdings via burn to defend the peg.
As long as the price variation is in extreme VCRL range, VCF will remain static and will keep accumulating LUNC (in VCF) that are distributed from transaction volume. Accumulating more funds in VCF will save CUST defend the peg to a larger extent. Once the current price variations against the lowest of 3-day price falls below extreme VCRL (i.e within acceptable VCRL range) VCF will start to burn LUNC and CUST minting gets enabled.
Conditions:
-
Value of Volatile Control Funds should be greater than or equal to 3 times*** of LUNC Collateral Funds and CUST Pool.
-
If Volatile Control Funds value falls less than 3 times the value of LUNC Collateral Funds / CUST value, no funds should be sent to LUNC Collateral Funds / CUST Pool. Instead, the 40% (20% + 20%) should be sent to Volatile Control Funds to increase its hold above 3 times value.
-
LUNC Collateral Funds Value is always pegged equivalent to CUST Pool Value. The equivalent CUST value is derived based on LUNC Collateral Funds value. Most of the scenario it remains as 1$ as it is pegged proportionately.
-
When LUNC Price goes down, Volatile Control Funds should be sent to LUNC Collateral Pool to peg the value equivalent to CUST Pool Value
-
When LUNC Price goes up, Volatile Control Funds should be burnt and CUST generated in AFT Pool to peg the value equivalent to LUNC Collateral Funds Value
-
If the Volatile Control Funds falls less than 50% of the total holdings (LUNC Collateral Funds + CUST Pool), community governance voting is initiated to send 10% of Community Pool Funds to Volatile Control Funds.
-
When current price variation goes above VCRL (1.2X), CUST mint should not happen. Instead, LCF should release funds from its pool and burn the released funds so that VCF does not lose out its supply by hyper minting CUST which is required to defend the peg during huge selloffs. During this period, VCF can keep accumulating funds and increase its holdings so that it has more supply to defend pegs during downtrends.
NOTE
*Minted AFTs are made available in oracle pool (ORD) which is distributed to all stakers.
** Refer Table 4 & 5 which illustrates how ‘x’ amount of LUNC value is equated to CUST value during price volatility ↑↓
*** 3 times is determined based on the acceptable control limit to stabilize the $ peg value at times of high volatility
Market Swap
The current AFT plan requires collateral and volatile control funds to defend the peg. My initial thoughts about market swap got clouded with this scenario as funds has to be distributed to balance and defend peg. To describe with an example, lets say you want to swap 1M LUNC (@$0.00017) and in ideal situation you would expect to get 170 CUST ($170). This is not the scenario that will happen based on the current proposal. To mint 1$ in CUST, VCF and LCF should be funded with $3 and 1$ equivalent LUNC respectively. i.e. if market swap is to be enabled then it would mint you only $34 (as 600K LUNC equivalent to $102 + 200K LUNC equivalent to $34 will be sent to VCF and LCF respectively to defend the peg). This was the primary reason why I couldn’t factor market swap earlier.
Thanks to some of the community members to make me reconsider this. A thought occurred my mind to make it is a possible option in theory. While technical challenges in reality are completely different from theoretical expectations, only the developers can comment on it.
Restricted Market Swap:
To defend the peg, both VCF and LCF should have adequate funds. The possibility of market swap with the current proposal has its own limitations. To have a fair distribution of CUST and / sustain volatility, Market Swap condition should be TRUE as shown in below table. Until LUNC total supply reaches 10B, one way market swap of LUNC to CUST should be enabled.

Table — 8 Market Swap Conditions and Daily Swap Limit per wallet
#CUST Refill Period — If CUST in ORD falls below 500K CUST, market swap should be disabled temporarily, i.e. until CUST supply in ORD is refilled to a minimum sustainable level set as 1.5M CUST. Once ORD cross the required threshold limit of 1.5M CUST in ORD, it should move away from Refill Period and market swap will immediately be enabled to all users. This process will follow in a loop, so that market swap gets enabled when ORD supply is greater than 1.5M CUST and gets disabled when ORD supply falls below 500K CUST. Reward distribution to stakers will be enabled at all times.
As CUST minted in ORD already has the backup funds in LCF to retain peg, market swap will result in exact equivalent value of CUST. i.e. based on above example 1M LUNC will be burnt and $170 CUST will be directly released to user wallet from ORD (or mint CUST in wallet and directly burn the exact numbers from ORD). I am not sure on the technical functionalities, hence suggesting that either one of the options should work so that there is no change in CUST supply and remains pegged. This will also speed up the removal of LUNC from total supply.
Market swap fees collected in LUNC should be sent to VCF to increase VCF holdings so that it can defend peg value during market selloffs.
CONCLUSION
First of all, I would like to extend my gratitude to all of you for taking time in reading the text proposal of creating new AFT, a real community owned not so called a stable coin, but a low or no volatile coin in normal market conditions. I strongly believe that CUST will revive decentralized money. Like LUNC reborn from the ashes, let CUST be born from the current burn tax.
I am open for any constructive feedback on this proposal. I have crafted this proposal with the best of my abilities and to bring more value to LUNC community. Please bear with me if any of my logics are incorrect. I am human too and tend to make errors or even may have missed out not considering critical factors.

