Proposal #780
Passed on 12 May 2024 with 75.5% of the votes for yes.
Yes
75.5%
93.8% without abstain
Veto
0.0%
of votes cast
Ended
12 May 2024
75.54%
of votes cast
19.47%
of votes cast
4.99%
of votes cast
0.00%
of votes cast
This proposal would restructure Strideās delegation program on Osmosis to deprecate the existing Stride delegation process in favor of copy-staking. The full proposal, with a description of how the proposed copy-staking model will work as well as the benefits and tradeoffs, is outlined below.
Background
Stride governance has the final say on all aspects of the host-chain delegation process, selecting the means by which validators on host-zones like Osmosis are chosen to receive delegations as well as how tokens delegated with Stride are divided up amongst the chosen set.
Historically, Stride governance has elected to utilize a council process to manage delegations on Osmosis. At a high level, this process selects Osmosis validators for Stride delegations by:
The council process, however, assumes that the Osmosis community wants liquid staking providers to be opinionated delegators. While some chain communities will undoubtedly prefer LSPs to play an active role in decentralizing the chain via their delegations, an obvious tradeoff to this model is that delegation decisions for tokens staked with a LSP are made by the LSPās users rather than by the host-chainās users.
Some chains may prefer a delegation model in which the LSP takes a neutral approach to making delegations, opting instead to preserve the existing staking dynamics between a chainās validators and its community of stakers. This is where copy-staking comes into play.
Strideās Copy-Staking Model
Thanks to a recent software upgrade, Stride can now delegate to Osmosisās entire set of 150 validators, making copy-staking a viable model for Strideās OSMO delegations on Osmosis.
Copy-staking works exactly as it sounds. Stride ācopiesā the delegation preferences of the host-chainās community by delegating to all validators in the active set according to existing stake weight. Strideās existing delegations to any validator are not included in the stake weight calculations.
For example, if the rank 1 validator has 5% of a chainās existing delegations after subtracting any existing Stride delegations, 5% of all tokens liquid staked with Stride will be delegated to that validator. If the rank 2 validator has 4% of delegations, Stride will delegate 4% to that validator, and so on. As stake weight across the set changes over time, Strideās delegations will also change accordingly.
Stride adjusts copy-staking delegation weights on a monthly basis. In a future upgrade it will be possible to rebalance delegation weights continuously as organic stake weight changes.
Copy-Staking can be considered a truly neutral approach to LST delegations because it preserves the existing power dynamic between stakers and validators. If a validator consistently behaves in a manner that doesnāt align with a chainās community of stakeholders, those stakeholders can redelegate away from that validator and reduce that validatorās vote power. In turn, Stride will reduce the allocation to that validator to match the validatorās new vote power.
By emulating the delegation preferences of a chainās stakers, liquid staking protocols like Stride can also preserve the chainās existing governance dynamics by preventing any one validator (or any subset of validators) from having more voting power than they otherwise would without liquid staking delegations.
Stride is the first liquid staking provider in the Cosmos Ecosystem to offer this neutral solution to its host chains. Copy staking is already in place for stTIA and stDYM delegations. The purpose of this proposal is to determine whether Strideās OSMO delegations should also transition from the existing council model to the more neutral copy-staking model.
Implementation Details
Governance proposals will go live on both the Stride and Osmosis chains to approve the transition to copy-staking. If both proposals pass, Stride will transition its OSMO delegations to a copy-staking model by delegating across the entire active set of 150 validators according to existing stake weight for each validator with the following limited exceptions:
The purpose for these exclusions is to keep liquid staking costs low and eliminate potential risk vectors associated with a copy-staking delegation model. Stake that would have gone to a validator excluded from delegations under these exceptions will be redistributed amongst the remaining validators according to existing stake weight.
Final Thoughts
Copy-staking represents Strideās commitment to more closely align with the needs and wishes of its host-zones. While some chains will continue to prefer the existing Stride delegation process, copy-staking gives chains the opportunity to opt-in to a more neutral delegation model.
Given how active Osmosisās governance community is, Osmosis is a prime candidate for copy-staking. A copy-staking model will allow for the existing voting dynamics, built by the delegation habits of Osmosisās community of stakers over time, to be preserved.
Forum Post: [Hidden link]