Try Quests to earn cryptoSuperFluid Validating
Project Overview
There are 16 SuperFluid Staking pools currently available on Osmosis (1, 678, 704, 712, 674, 722, 9, 604, 497, 812, 584, 3, 481, 42, 463, 15). What impact would a slashing event have on the OSMO liquidity of these pools?
** \n **
Analyze the distribution of superfluid-staked OSMO across these pools. Which validators have the most SFS OSMO in total, and per pool?
Introduction
In traditional proof-of-stake, staking is the key to maintaining integrity of the consensus mechanism. Tokens can be delegated to a validator to provide an economic collateral that can be penalized, or slashed, for misbehavior. Superfluid staking allows Osmosis users to delegate the OSMO underlying their bonded liquidity pool tokens to strengthen the security of the Osmosis network, expand the utility and demand for the OSMO token, and increase their yields.
How does Superfluid Staking work?
Superfluid staking allows users to stake their bonded LP tokens. This option is available to LP tokens for OSMO pairs that are bonded for an amount of time that is equal to or longer than the staking unbonding time — currently 14 days. Bonded LP tokens delegated to a validator will continue to earn swap fees and liquidity mining incentives, and the OSMO underlying the LP tokens will now earn staking rewards from inflation and transaction fees.
Unlike traditional staking, where rewards must be claimed, superfluid staking rewards are distributed to accounts directly at epoch, similar to liquidity mining incentives. A key feature of superfluid staking is the “superfluid discount factor” parameter. This parameter adjusts the percentage of underlying OSMO of a superfluid staked LP token that is counted as delegated. It represents the amount that is “discounted”, or removed from a user’s superfluid delegation. For example, a superfluid discount factor of 10 means that 90% of the OSMO underlying a given LP can be counted as delegated. The superfluid discount factor does not apply to slashing to punish validator misbehavior. Superfluid staked LP tokens will be subject to slashing at full value. Slashed LP tokens are sent to the community pool. As the amount of OSMO underlying a given LP token will constantly change, the amount of OSMO that is credited to a user’s delegation will be recalculated each epoch.
In terms of how superfluid staking works on the UI level, users can utilize the new Superfluid button on a given pool’s page on Osmosis.zone, or interact with the superfluid module via the command line. The unstaking period from superfluid staking is the same as traditional staking, however if initiated on the Osmosis front end, the LP tokens will be unstaked and unbonded at the same time and the timers will run concurrently for a total period of 14 days. As with traditional staking, rewards are not earned when unstaking from superfluid staking. ** \n **
Features of Superfluid Staking
Superfluid Staking is described as “the biggest addition to Proof of Stake since slashing.” It applies a method by which those who provide liquidity to certain pools can earn additional yield by also staking these bonded assets to a validator for staking rewards. Initially, one provides liquidity to a pool, in return an LP token is provided. Users can then stake their LP token, thus securing the network whilst earning rewards through a traditional delegation process.
Notably, Superfluid Staking has several caveats (which will likely be modified as time goes on):
- You are only able to delegate your LP share to one validator;
- With Superfluid Staking active, you give up your delegator governance voting power related to the assets provided to the LP. In technical terms, this means your ability to individually override governance votes made by the validator you’ve chosen is no longer possible;
- You are not able to redelegate your LP share to other validators 1
Methodology
This dashboard is made up of two made parts . in the first part , you can find useful stats about all SFS pools and compare them in terms of total, average , median and max SFS amount , Number of delegators and validators ,aggregate metrics per pool and etc. also, you can find top validators among all pools and in each pool. top delegators among all pools and also in each pool are presented.
in the second part , you can select your desired pool from top right and find its overall and timely stats. you can also select another pool from compare to part and compare your selected pools.
Observations
-
The chart on the left shows the cumulative SPF amount throughout all pool over time in daily basis. as can be seen, the pool number 9 which indicated CRO/OSMO is ranked first in this metric and could have separate itself from all other spf pools. the pool 1 (ATOM/OSMO) is ranked second by far.
-
19.5 % of SPF amount (1.93B) gone throughout pool #9 and 16.6% (402M) gone to #1
-
The last pools in the list are 481(EEUR/OSMO) and 604 (STARS/OSMO) with an amount od 89 and 282 respectively
Slashing
It’s what happens when validators misbehave badly, double-signing a transaction or colluding to attack the chain. Bonded assets can be burned to raise the costs of such an attack. In the case of superfluid staking, any slashed funds will be sent to the Osmosis Community Pool. Slashing is another reason to be thoughtful about your validator selection.
Slashing works by gathering all accounts who were superfluidly staking and delegated to the violating validator and slashing their underlying lock collateral. The amount of tokens to slash are first calculated then removed from the underlying and synthetic lock. Therefore, it is important to select a reputable or reliable validator as to minimize slashing risks on your tokens. At the moment we are slashing at latest price rather than block height price. All slashed tokens go to the community pool.
We first get a hook from the staking module, marking that a validator is about to be slashed at a slashFactor of f, for an infraction at height h.
The staking module handles slashing every delegation to that validator, which will handle slashing the delegation from every intermediary account. However, it is up to the superfluid module to then:
- Slash every constituent superfluid staking position for this validator.
- Slash every unbonding superfluid staking position to this validator.
Add Text Here
Observations (top 3 pools)
-
**in terms of SFS OSMO per POOL : **
- #9→1.93B , #1→402M , #3→54M
-
**in terms of tot #Delegators per POOL : **
- #1→77k , #722→13k , #678→10.88k
-
**in terms of tot #Validators per POOL : **
- #1→181, #678→171, #722→170
-
**in terms of SFS OSMO per Delegator per POOL: **
- #9→419k, #3→33k, #1→5.2k
-
**in terms of SFS OSMO per Validator per POOL : **
- #1→181, #678→171, #722→170
-
**in terms of SFS OSMO per Day per POOL : **
- #9→7.3M, #1→1.31M, #3→231k
-
**in terms of #Delegators per Day per POOL : **
- #1→262, #722→79, #678→52
-
**in terms of #Validators per Day per POOL : **
- #812→1.95, #722→1, #678→0.82
