Welcome to deBridge Governance! This is the first post on deBridge governance forum, and to kick off community discussions, we’re sharing a potential outline for how DBR staking could work to collect feedback and ideas from the community.
Here’s a general overview of the overall process and how things could work:
DBR token holders can stake DBR to participate in governance. There is a cooldown period of unstaking (14 days).
Staked DBR is used to vote on governance posts (similar to how it’s done on Jupiter: https://vote.jup.ag/).
Active stakes generate deBridge points in real-time. During cooldown (unstaking) stakes don’t yield any voting power and don’t yield points.
Points are also accounted for every governance proposal voted on.
Restaking
Staked DBR (as well as other liquid assets approved by the DAO) can be restaked for one of the active validators of deBridge messaging, to provide crypto-economic security guarantees in the form of slashable collateral, and to generate additional points on it. Active restaked DBR yields voting power to its owner.
Unstaking from a validator has a cooldown period as well. It returns the liquid asset to the owner’s balance.
Voting power generated from active staked and restaked DBR is used by the owner to participate in governance voting.
Staking mechanics will also be important for solvers of the deBridge Liquidity Network (DLN), who are competing for cross-chain order flow. Now, competition is open for everyone who has experience in development and running automated inventory management and taking scripts. The fastest solver taking the biggest finality risk is the one winning the order flow.
Solvers have been among the biggest recipients of the initial DBR airdrop, as they paid protocol fees for cross-chain messages that unlock fulfilled orders. With the introduction of staking, the DAO can introduce an onboarding flow for all solvers, and grant solvers an admission to the order flow competition, only if it has at least X of DBR voting power.
In the event of a validator fault (e.g. forging of the message or downtime/censorship) governance can vote to pause staking/unstaking for a specific validator (part of the stake that is under cooldown of this validator is paused as well). E.g. If a validator fault happens at “slashing_event_timestamp”, then all stakes queued for unstaking after this timestamp are returned to the active validator’s stake to be part of the slashable collateral.
After pausing staking/unstaking for a specific validator and fixing the total slashable amount, governance can vote on what amount should be slashed (transferred from restaking contract to the DAO treasury). If the DAO vote is positive, the governance multisig then executes a slashing transaction, leading to stakes of all assets restaked for the validator be reduced proportionally to the slashed amount. After slashing, staking/unstaking is unpaused, and all staking/unstaking operations return back to normal.
Users can vote on slashing-related decisions as long as it does not concern the validators they have re-staked to, in this situation, their respective stake is to be excluded from these governance decisions due to conflict of interest.
The governance multisig should also be able to add other assets that can be used for restaking (e.g. jitoSOL). For non-DBR assets, smart contracts will return an LP token that represents ownership over restaked assets. LP tokens enable composability for restaked assets.
When users vote on governance posts, the voting contract should calculate the voting power of each address as a sum of:
-
The total amount of staked DBR
-
The total amount of restaked (and not paused) DBR for all validators
-
If that’s a post that is part of the slashing process of N’th validator, deduct restaked DBR for N’th validator from voting power
The final total amount is the voting power of each address participating in governance.
Our goal is to build a thriving ecosystem governed by DBR token holders.
Based on the suggested design for staking, DBR will have the following utilities:
- Staking DBR to participate in governance
- Restaking of DBR for deBridge validators to provide crypto-economic security guaranteed for the deBridge messaging
We truly appreciate everyone in the deBridge family, and we hope that our newly launched governance forum can be a place to brainstorm, collaborate, and optimize deBridge.
What do you think of the post?
Please let us know in the replies, we appreciate anyone that gives input on how we can improve it for the benefit of the deBridge ecosystem. Thank you!
