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

[BIP-560] Enable Single Recipient Gauge for GEM/ETH on [Ethereum] #841

Merged
merged 3 commits into from Mar 21, 2024

Conversation

Xeonus
Copy link
Collaborator

@Xeonus Xeonus commented Mar 14, 2024

  • enable ve80/20 GEM/ETH single recipient gauge on mainnet
  • recipient is a msig that approves spending on the reward manager contract to distribute to vlGEM

- enable ve80/20 GEM/ETH single recipient gauge on mainnet
- recipient is a msig that approves spending on the reward manager contract to distribute to vlGEM
Copy link
Contributor

BIP validation results for file BIPs/2024-W12/BIP-560.json:
Commit: f6672722ddac7f1480123d1cbb0747f825ac69d8

+-------------------------------+--------+
|           Validator           | Result |
+-------------------------------+--------+
|     validate_contains_msig    |   OK   |
| validate_msig_in_address_book |   OK   |
|    validate_chain_specified   |   OK   |
|     validate_file_has_bip     |   OK   |
|  validate_path_has_weekly_dir |   OK   |
+-------------------------------+--------+

@gosuto-inzasheru
Copy link
Member

report script currently breaks on the recipient, which is their multisig, not having the getVotingEscrow attribute (https://github.com/BalancerMaxis/multisig-ops/actions/runs/8276693450/job/22645692288#step:7:227). thus being unable to programmatically retrieve the address of the veGEM token

@Xeonus
Copy link
Collaborator Author

Xeonus commented Mar 14, 2024

withhold and move to following week

@Xeonus
Copy link
Collaborator Author

Xeonus commented Mar 18, 2024

@Tritium-VLK @gosuto-inzasheru This is the answer from the proposer: https://forum.balancer.fi/t/bip-xxx-enable-single-recipient-gauge-for-gem-eth-on-ethereum/5608/3

Basically MSig receives yield from the SingleRecipientGauge weekly and it will be queued on the vlToken contract to be distributed. Later on we can see for an onchain permisionless system

I think we can move forward this week unless there are objections

Copy link
Contributor

BIP validation results for file BIPs/2024-W13/BIP-560.json:
Commit: f12af6fcead5a56dfcd28a06e347d74a91afdc60

+-------------------------------+--------+
|           Validator           | Result |
+-------------------------------+--------+
|     validate_contains_msig    |   OK   |
| validate_msig_in_address_book |   OK   |
|    validate_chain_specified   |   OK   |
|     validate_file_has_bip     |   OK   |
|  validate_path_has_weekly_dir |   OK   |
+-------------------------------+--------+

Copy link
Member

@gosuto-inzasheru gosuto-inzasheru left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yield is being distributed manually (permissioned) via a multisig

@Tritium-VLK Tritium-VLK merged commit 34114b9 into main Mar 21, 2024
3 checks passed
@Tritium-VLK Tritium-VLK deleted the BIP-560-GEM-WETH-singlerecipient-gauge branch March 21, 2024 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants