# Proposal: Initiate Rollout of Spot v2 **URL:** \ **Category:** Ampleforth Governance\ **Created:** [April 9, 2024, 9:09pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738 "2024-04-09T21:09:46Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 9, 2024, 9:09pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/1 "2024-04-09T21:09:46Z")
# What is Spot? SPOT is a decentralized flatcoin that uses tranching instead of liquidation markets to provide durable long-term stability. SPOT can be held directly as a refuge from inflation, used as a peer-to-peer digital cash, or held as alternative collateral to USDC within reserves. Spot has been successfully operating [since Dec of '22](https://blog.ampleforth.org/spot-the-inflation-resistant-store-of-value-87e8112468b2?source=collection_home---5------0-----------------------), and the Rotation Vault since [in Aug '23](https://blog.ampleforth.org/the-spot-rotation-vault-4f1e9e7d408b). We believe this protocol [has the potential to be an important innovation](https://blog.ampleforth.org/scaling-spot-7f56ef1b28c9) for society at large—and that healthily scaling SPOT is important for that long run success. With that in mind, the Fragments development team has been hard at work developing features that can execute on that vision, and we would like to begin the rollout of these in collaboration with the broader Ampleforth community. # Spot v2 Spot v2 introduces two key features. They serve to: - Facilitate SPOT \<\> AMPL arbitrage through **Swapping** , and - Balance demand for stability and volatility using a **Dynamic Rotation Fee** For more background, please refer to the linked resources below. - [The Path to Counter Cyclical Demand](https://blog.ampleforth.org/spot-v2-the-path-to-counter-cyclical-demand-0548d273a2c0) - [How Spot v2 Makes Arbitrage More Efficient](https://blog.ampleforth.org/how-spot-v2-makes-arbitrage-more-efficient-4b5c13acaa95) - [Scaling SPOT](https://blog.ampleforth.org/scaling-spot-7f56ef1b28c9) - [v2 Docs](https://docs.spot.cash/spot-documentation/spot-documentation/about-the-rotation-vault-and-stampl#rotation-vault) # Rollout Steps Provided there is support from the community, as determined by rough consensus here and by signal vote, the rollout will be performed as an **inplace upgrade**. Existing SPOT holders and stAMPL stakers will not need to remove or migrate their assets. If, however, the vote passes and you’d like to opt out of an upgrade, you would need to exit the system before that happens. There are no changes to the underlying ButtonTranche contracts. # Timeline Once there is rough consensus in community discussion, we can move to a signal vote, which takes 5 days. There is no Timelock associated with Snapshot, so we will wait at least two days following the conclusion of voting before executing the rollout. ## Implementation & Details - [Github](https://github.com/ampleforth/spot/tree/43755a4c609e30ab71b5d55c6fe838fb42bda9b4) - [Peckshield Security Audit](https://github.com/ampleforth/ampleforth-audits/blob/master/spot/v3.0.0/PeckShield-Audit-Report-Spot-v1.0.pdf) ## Proposed Fees & Configuration | Rollover Fee Curve | | | --- | --- | | rolloverFeeLower (Debasement) | -10% / yr | | rolloverFeeUpper (Enrichment) | 20% / yr | | rolloverFeeGrowth | 7 | _Rollover Fee % vs Deviation Ratio Plot_ ![Rollover Fee % vs Deviation Ratio](https://canada1.discourse-cdn.com/flex030/uploads/governance1/original/1X/ced7da0b1a5e675ee1e29e11b51869655a88d117.png) | Other Fee Values | | | --- | --- | | perpMintFee | 1% | | perpBurnFee | 1% | | underlyingToPerpSwapFee | 4% | | perpToUnderlyingSwapFee | 4% | | vaultMintFee | 0% | | vaultBurnFee | 5% | | Configuration Values | | | --- | --- | | targetSubscriptionRatio | 1.5 | | deviationRatioBoundLower | 0.9 | | deviationRatioBoundUpper | 1.25 | | minUnderlyingBal | 100k | | minUnderlyingPerc | 33% | | minDeploymentAmt | 25k AMPL | ---
**Author:** ![Pascal](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@Pascal](https://forum.ampleforth.org/u/Pascal)\ **Post date:** [April 9, 2024, 11:44pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/2 "2024-04-09T23:44:29Z")
> [@Brandon](#): > > rolloverFeeLower (Debasement) -10% rolloverFeeUpper (Enrichment) 20% rolloverFeeGrowth 7 I think I need a better grasp on these fees. Can anyone ELI5 with maybe an example with numbers on how this will work for debasement and enrichment? I dont understand the context of rollover fee growth either. Is this annually? Weekly? How does this factor in with debasement and enrichment? ---
**Author:** ![RomanPope](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/romanpope/32/244_2.png) [@RomanPope](https://forum.ampleforth.org/u/RomanPope)\ **Post date:** [April 10, 2024, 10:43am UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/3 "2024-04-10T10:43:18Z")
Ditto, I think more details are always welcome. ---
**Author:** ![Pascal](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@Pascal](https://forum.ampleforth.org/u/Pascal)\ **Post date:** [April 10, 2024, 12:33pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/4 "2024-04-10T12:33:09Z")
“How Spot v2 Makes Arbitrage More Efficient” in the original post links to the wrong article. ---
**Author:** ![mataklap](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@mataklap](https://forum.ampleforth.org/u/mataklap)\ **Post date:** [April 10, 2024, 12:37pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/5 "2024-04-10T12:37:26Z")
![Screenshot 2024-04-10 at 14.31.19](https://canada1.discourse-cdn.com/flex030/uploads/governance1/original/1X/ddeb4d2e77290a07436b1046837543563958f0b0.png) My question is, how does the proposal incentivise arb profits stay in the AMPL ecosystem? Surely the stakers get a fee from the swaps but additional profits could be drained. Should this fee % not be on a curve so it adjusts with price movements? With the Aave implementation, the capped 72,000% API also basically drained all lenders over time, as the rebase API was exceeding that 72,000% at a certain price level.This will not happen with the Rotation Vault? ---
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 10, 2024, 9:47pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/6 "2024-04-10T21:47:46Z")
Good questions Pascal. I’ll answer here, and make sure they’re included in the docs when applicable. For those willing to look at the protocol code, most fee details can be found in the [FeePolicy](https://github.com/ampleforth/spot/blob/dev/spot-contracts/contracts/FeePolicy.sol). # Fee Values `perpMintFee` - The fee a minter pays when minting SPOT. For example, if the collateral value of 1 SPOT token is 1 AMPL (as it is now), a minter receives 1 SPOT for 1 fully collateralized AMPL A-tranche when the fee is 0%. If there were a 1% fee, a minter would receive .99 SPOT for that 1 tranche. This is non-extractive, so the all the input tranches still go to the SPOT collateral base, effectively enriching SPOT. `perpBurnFee` - The fee for redeeming SPOT tokens for the underlying collateral. Similar structure as the mint fee. A 1% burn fee means a redeemer would get 1% less collateral compared to the 0% fee case. The remainder stays in the SPOT collateral set. `underlyingToPerpSwapFee` and `perpToUnderlyingSwapFee` - These are the trade fees when swapping between AMPL and SPOT through the Rotation Vault. Since this swapping is enabled by the liquid AMPL provided by Rotation Vault stakers, these fees go to the Rotation Vault, in the form of increased collateral base for vault stakers. Note that swapping also results in SPOT minting or redemption. So the total swap fee for a user is the sum of perpMint/Burn and the SwapFee. `vaultMintFee` and `vaultBurnFee` - Similar to perp mint and burn fees, but for the Rotation Vault (i.e. stAMPL). This is similarly non-extractive, so all fees result in increasing the collateral base for the remaining stAMPL holders. # Rollover Fee Curve The rollover fee curve is a shaped Sigmoid function, similar to the sigmoid curve [of the AMPL supply policy](https://forum.ampleforth.org/t/rebase-curve-upgrade-proposal/327). The shape of this sigmoid curve is defined by three shaping parameters: ceiling, floor, and growth factor. `rolloverFeeLower` determines the lower asymptote, and `rolloverFeeUpper` defines the upper asymptote. `rolloverFeeGrowth` determines the slope at the origin. So the higher the growth facter, the more sensitive the fee is to changes in the input, and the quicker the system reaches the ceiling or floor. The input of this curve is the “[Deviation Ratio](https://github.com/ampleforth/spot/blob/8b61acb9d823b4d2d31ea73c7883080dcbd672c2/spot-contracts/contracts/FeePolicy.sol#L18)”, which is a measure of how far the SPOT/stAMPL ratio is from the desired equilibrium. # Configuration Values `targetSubscriptionRatio` - This determines what is considered a “healthy equilibrium” between SPOT and stAMPL. A subscription ratio of 1.0 is exactly equal to the tranche ratio of the current minting bond. Today, the bond minting ratio is 33/67, so a target subscription ratio of 1.0 would be 33 AMPL worth of SPOT for every 67 AMPL worth of stAMPL. 1.5 adds a 50% buffer to guard against underfunded SPOT rotations. `deviationRatioBoundLower` - The point below which swapping from AMPL to SPOT is no longer offered by the rotation vault. `deviationRatioBoundUpper` - The point above which swapping from SPOT to AMPL is no longer offered by the rotation vault. `minUnderlyingBal` - A safety buffer of AMPL that must always exist inside the Rotation Vault. See [3.1 here](https://github.com/ampleforth/ampleforth-audits/blob/master/spot/v2.0.0/PeckShield-Audit-Report-Spot-v2.0.pdf), for reasons for this safety measure. `minUnderlyingPerc` - This guards the swap functions from locking up free AMPL that would otherwise be needed to perform rotations. Rotation uptime is always given priority over swapping. `minDeploymentAmt` - The smallest size rotation needed to execute, denominated in AMPL. This guards against gas griefing attacks. ---
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 10, 2024, 10:07pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/7 "2024-04-10T22:07:41Z")
First, see the post above on fee structure so there’s no misunderstandings on those mechanics. The total swap trade fee would be a healthy 5%, and that portion is completely non-extractive. It stays in the the SPOT/stAMPL system. If an arber decides that a 1% profit (very large for one trade!) is what they consider worthy, then 5/6ths of that stays in the system (it would take a 6% deviation to trigger). But real arb markets are hypercompetitive. 1% profit per trade, risk-free is nearly unthinkable. So in practice, even in the worst cases, we’re talking very small numbers. Secondly, the flows described in that blog post are just one example. There are alternate flows an arber can use if they preferred to stack AMPL or stack SPOT instead of stacking USDC. They would even be simpler in some ways since they would never need to touch any outside asset. However, the broader point perhaps is that we can’t control how traders trade assets in open markets. It’s essential that people are able to trade both SPOT and AMPL for, say, ETH, in the open market for liquidity and safety reasons. An alternate formulation of your question could also be “How can we ensure value stays in the ecosystem when a fast trader trades AMPL for something else like ETH or USD?” In the past, there were no options. But now there is – SPOT. ---
**Author:** ![Pascal](https://avatars.discourse-cdn.com/v4/letter/p/e9a140/32.png) [@Pascal](https://forum.ampleforth.org/u/Pascal)\ **Post date:** [April 11, 2024, 1:25pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/8 "2024-04-11T13:25:25Z")
The fee breakdown was very helpful, there are a lot of moving pieces here so having an understanding of them is important. Overall I am in favor of this rollout. I think the fee structure as it stands makes sense, and poses no significant threat to the AMPL / SPOT ecosystem. I think we can spend months analyzing this until we’re blue in the face, but I’m in favor of seeing how this behaves in the wild and receiving market feedback in real time, and avoiding analysis paralysis. The fees can always be altered in the future if desired, worst case. ---
**Author:** ![mataklap](https://avatars.discourse-cdn.com/v4/letter/m/ecd19e/32.png) [@mataklap](https://forum.ampleforth.org/u/mataklap)\ **Post date:** [April 11, 2024, 3:23pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/9 "2024-04-11T15:23:23Z")
Thanks, clear - looking forward to see how this plays out in the market! ---
**Author:** ![Greg](https://avatars.discourse-cdn.com/v4/letter/g/71c47a/32.png) [@Greg](https://forum.ampleforth.org/u/Greg)\ **Post date:** [April 11, 2024, 7:18pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/10 "2024-04-11T19:18:39Z")
Is the deviation ratio not taking into account the target subscription ratio of 1.5? In other words, a 1.0 deviation ratio equals a 1.5 subscription ratio, the lowerbound is 0.9 x 1.5 = 1.35, and the upperbound is 1.25 x 1.5 = 1.875 subscription ratio? ---
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 11, 2024, 8:26pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/11 "2024-04-11T20:26:14Z")
Yes, exactly. The Deviation Ratio is defined as the Subscription Ratio / Target Subscription Ratio. So your calculated 1.35 and 1.875 SR examples are also correct. ---
**Author:** ![Forthwhale](https://avatars.discourse-cdn.com/v4/letter/f/a5b964/32.png) [@Forthwhale](https://forum.ampleforth.org/u/Forthwhale)\ **Post date:** [April 12, 2024, 1:41am UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/12 "2024-04-12T01:41:34Z")
I am in favor of this proposal. ---
**Author:** ![Eele](https://avatars.discourse-cdn.com/v4/letter/e/f05b48/32.png) [@Eele](https://forum.ampleforth.org/u/Eele)\ **Post date:** [April 12, 2024, 4:11am UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/13 "2024-04-12T04:11:07Z")
Looks good to me, i will vote in favor of this ---
**Author:** ![Richard\_Meng](https://avatars.discourse-cdn.com/v4/letter/r/258eb7/32.png) [@Richard\_Meng](https://forum.ampleforth.org/u/Richard_Meng)\ **Post date:** [April 13, 2024, 10:41am UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/14 "2024-04-13T10:41:29Z")
Looking forward to the next step! Any idea when we can start vote process? Can’t wait. ---
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 15, 2024, 7:05pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/15 "2024-04-15T19:05:51Z")
Thanks for the comments and support everyone! I’ve kicked off a signal vote [here](https://signal.ampleforth.org/#/proposal/0x79065e6876a2b9c1e79965bc263317d55f70516a9aa5a420dd499f83f7ef08fe), and voting begins tomorrow. ---
**Author:** ![Brandon](https://yyz2.discourse-cdn.com/flex030/user_avatar/forum.ampleforth.org/brandon/32/301_2.png) [@Brandon](https://forum.ampleforth.org/u/Brandon)\ **Post date:** [April 19, 2024, 9:11pm UTC](https://forum.ampleforth.org/t/proposal-initiate-rollout-of-spot-v2/738/16 "2024-04-19T21:11:19Z")
The signal vote has passed. Following the timeline from above, we plan to execute the rollout no earlier than next Monday. As a safety measure, swaps are currently planned to be disabled until after the first rollover occurs. Assuming all goes well after the first rollover, swapping will be turned on immediately after.