Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Slashing #139

Open
p-offtermatt opened this issue Oct 10, 2024 · 1 comment
Open

Slashing #139

p-offtermatt opened this issue Oct 10, 2024 · 1 comment
Labels
priority: must-have Features that must be done before we can deploy. q4 These are things that we want to do during q4

Comments

@p-offtermatt
Copy link
Member

p-offtermatt commented Oct 10, 2024

We would like to implement a mechanism to slash voters who vote on liquidity positions that turn out to lose some of the PoL.

We want to add an endpoint thats permissioned to be only usable by the whitelist admin and that slashes the voters for a certain proposal by a certain amount.

This needs user funds to be locked until liquidity is returned (end of deployment round + a few days)
Decision: does the Hydro DAO need to say "Proposal returned all funds" that unlocks the voters funds; or do the voters funds get unlocked automatically and the Hydro DAO just needs to be quick enough with slashing?

Useful notes:

  • Max slash percentage enforced by the smart contract
  • Only slash once for a given proposal
  • Decide on a slash function (linear vs quadratic; can 100% of voters stake get slashed; what happens if the whole liquidity is lost)
@p-offtermatt p-offtermatt added v2 priority: must-have Features that must be done before we can deploy. labels Oct 10, 2024
@p-offtermatt p-offtermatt added q4 These are things that we want to do during q4 and removed v2 labels Oct 17, 2024
@p-offtermatt
Copy link
Member Author

Spike: A slash transaction that takes a certain amount of LSM shares, transfers them to the Hub, and via ICA untokenizes them

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: must-have Features that must be done before we can deploy. q4 These are things that we want to do during q4
Projects
None yet
Development

No branches or pull requests

1 participant