Osmosis v7 Carbon Upgrade
passed
Expected result
Passed
Turnout / Quorum
36.41% / 20.00%
Voting period
Voting ended100.0%
Voting start 2022.02.25 at 09:06:58
Voting end 2022.02.28 at 09:06:58
Vote distribution
99.57%
75 155 078 osmo
Yes
0.02%
13 351 osmo
No
0.00%
1 068 osmo
Veto
0.41%
306 601 osmo
Abstain
Details
Proposer
-
Total deposit
500 osmo
Submit time
2022.02.25 at 08:54:31
Deposit end time
2022.03.11 at 08:54:31
Description
Osmosis Carbon Upgrade\n\nThis proposal proposes that the chain elect to do a software upgrade to the v7.0.0 software tag of the Osmosis codebase on block height 3401000, which is estimated to occur on February 28, UTC 8:00PM. Block times have high variance, so please monitor the chain for more precise time estimates. \n\n## Upgrade features\n\nThis upgrade adds the following features:\n* Superfluid Staking\n* Permissioned CosmWasm\n* IAVL improvements (improved epoch times)\n* UX improvements around LP bonding\n\nSee more in the changelog\n\n## Getting prepared for the upgrade\n\nAll nodes will require 64GB of memory. This must consist of a minimum of 32GB of RAM, while the remaining 32GB can be swap. For best results, use 64GB of physical memory. Note that this is double the recommendation for the Boron upgrade. Also note that the inclusion of wasm means that nodes must use amd64 to run.\n\nPlease refer to the following setup instructions on how to add swap (if needed), and how to configure cosmovisor to automatically switch binaries for this upgrade: Upgrade Guide.\n\nNamely, configure cosmovisor to auto-restart. (Please note, you should install the v1.0.0 release of cosmovisor) Then either auto-download binaries or manually build & copy the osmosisd v7.0.0 binary to .osmosisd/cosmovisor/upgrades/v7/bin/.\n\nIf you do not wish to use cosmovisor, be prepared to upgrade at around 8:00PM UTC, February 28th if this proposal passes.\n\nThe Osmosis blockchain will halt when network reaches the halt height. Cosmovisor, if configured properly, will then switch the binary used to v7.0.0, and the chain will proceed post upgrade.\n\n## Details of upgrade time\n\nThe proposal targets the upgrade proposal block to be 3401000, anticipated to be at Monday February 28th 8:00PM UTC. This uses a 1 day average block time of 6.46 seconds per block, derived from the Mintscan block explorer. Note that block times have high variance, so keep monitoring the time.\n\nThe upgrade is anticipated to take approx 120 minutes, during which time, there will not be any on-chain activity on the network.\n\nIn the event of an issue at upgrade time, we should coordinate via the validators channel in discord.\n\n### Testing your upgrade setup\n\nThere is a testnet which full nodes can sync to, to test that they have setup cosmovisor correctly on a new node. See #testnet-announcements and #testnet-discussion channels in the Osmosis Discord.\n\n\n### Superfluid delegation \n\nIn this upgrade"s superfluid module, you can stake LP shares for specific governance-approved pools. A "superfluid discount factor" parameter exists for the superfluid module to ensure stability in the early rollout of superfluid staking, the superfluid discount factor parameter is set to 50% in this upgrade. This parameter can be adjusted by Osmosis governance.\n\nThe user can designate one superfluid validator to delegate to for each superfluid enabled liquidity pool.\n\nHere is an example for how it would work with ATOM-OSMO pool:\n\n#### On Delegation Voting Power and Slashing\nCondition\n- Suppose the spot price in the pool is 1 ATOM = 2 OSMO.\n- Suppose you have provided 100 OSMO and 50 ATOM worth of liquidity to Pool #1.\n- Suppose you have designated validator "Dogemosis" as your superfluid validator.\n- Superfluid discount factor is set to 10%\n\nResult\n- Your delegation to "Dogemosis" will increase by 100 OSMO * (1-DISCOUNT_FACTOR) = 90 OSMO.\n- You would then get staking rewards for an equavalent amount of 90 OSMO delegated to Dogemosis. However, you also then take on slashing risk from Dogemosis.\n- If Dogemosis gets a 5% slash due to double signing, then 5% of your LP shares (5 OSMO, 2.5 ATOM) get sent to the community pool. Note that slashing amount does not take into account the risk factor parameter, and slashes the entire amount of superfluided LP shares. In essence, effective slashing rate increases to the lower the risk factor is set to.\n\n#### On Changes to the delegation amount depending on changes in spot price\nLets now suppose the spot price in the pool changes during this epoch to be 1 ATOM = 1 OSMO, and your LP share changes to being (75 OSMO, 75 ATOM). Upon the next epoch, the effective staked OSMO amount will be calculated as 75 OSMO * (1-DISCOUNT_FACTOR) = 67.5 OSMO to reflect the change in the underlying OSMO amount of the LP token.\n\nAs the amount of OSMO backing the LP share increased (hence increasing the effective superfluid staked amount), the staking rewards will also increase.
Votes
Voter
Answer