-
Notifications
You must be signed in to change notification settings - Fork 27
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
Recycling for Paladin Bribs #1459
Comments
Here is an example claims payload from Paladin: |
Main push from BD/Partnerships on this front comes from saving some face and doing what we promised. We had told Aave / GHO stakeholders we would up our votes from vlAura to help raise their APRs/TVL on top of the bribes they were placing but instead neutralized the bribe market instead of working in tandem with it. Essentially this situation caught us not delivering on a promise. |
Discussed with jalbrekt. Autoclaimer may already be done. Tricky part is the next steps. As a first step. 1: Pay 70% of all tokens as bribs to the pool they came from in the same payload Later advancements if we keep doing this: (not in scope now) 1: Batch mainnet bribs into the next fee_allocator run to save gas Potential governance changes: 1: 100% to recycling I'll be less available. @Zen-Maxi is a good partner to work with once you get close/have something and to keep you up to date on any changes to governance. |
Context
The omnichain multisig is accumulating bribs from BD voting. In order for the BD voting to have effect, this value needs to be redirected back into the same pool it was earned from. BIP-715 specifies that in cases of recycling 30% is taken as a treasury fee and 70% is paid in as bribe markets. There has been some discussion around a new BIP that proposes 100% is paid in as direct incentives.
Techincal requirements
Parser for HH claims API
We need to be able to understand what is available to claim and where it came from so that we can claim it and pay it back in.
Claim data can be found on the Paladin API here: https://api.paladin.vote/quest/v3/copilot/claims/0x9ff471F9f98F42E5151C7855fD1b5aa906b1AF7e
It is a list of json maps shaped like this:
We need to
1: create a transaction builder tx that claims everything per chain.
2: print out a CSV of chain/pool_id/something human readable/amount that shows where redirect needs to go>
Redirecting value
Depending on the method decided, we either need to parse the above CSV, take our 30% cut, and then place bribs on HH , or potentally swap for other coins to avoid overlap and then place schedules on an injector.
Note we should seek to brib on the Balancer market if the bribs are aura bribs to avoid the "double payout" of voters problem.
For now should assume 30% cut and rebrib
End result
A workflow that you run, which generates a final payload to claim all available bribs per chain and pay them back out using the desired logic.
The text was updated successfully, but these errors were encountered: