• © Goverland Inc. 2026
  • v1.0.3
  • Privacy Policy
  • Terms of Use
Gotchi VaultGotchi Vaultby0x10bFc18F848AdB42fe95e330111622D9497431770x10bF…3177

Sig-Prop: Return 0VIX funds to multisig

Voting ended over 2 years agoSucceeded

Authors: 0VIX Protocol

GotchiIDs: 22864 (@Maxicrouton)

Quorum requirement: 20% (9M)

Vote duration: 7 days

Discord Thread: Aavegotchi>DAO>0VIX Discussion

Introduction:

To achieve a final resolution and ensure a definitive closure to this more than 2 months old issue, we propose advancing with the conclusive vote on sending the funds. These funds will be used to compensate users who have been affected by the 0vix exploit. The longer the process takes, the more uncertainty it brings for them. It is crucial to resolve this so that 0VIX can reopen the markets and distribute the shares to the users in question. For anyone that wants to read up on the topic here are the preceding CoreProps:

  • 0vix exploit : Return the funds
  • How to return the GHST from the 0VIX exploit that was transferred to the Aavegotchi DAO Treasury to 0VIX users

Objectives:

We all have a strong desire to move forward and put this situation behind us, and we want to take a moment to thank you for your help in bringing us to this point.

Details:

The multisig address to which the funds shall be sent to is: 0xa50bB0c6e80618D215b48352df0644006289d2B7

It is controlled by the following three signers:

  • 0VIX deployer wallet: recipient of Vitalik's message and 0.01ETH by Vitalik on Polygon zkEVM’s launch day
    • PubKey: 0x7A10033Fb8F474F28C66caB7578F4aF9e6dAd37D
  • Hamzah Khan: Polygon Head of DeFi & Director of Growth
    • PubKey: 0xc156C57231a9302D9f5C7b5eF22871cC25F40736
  • Benjamin.lens: QiDAO core team member
    • PubKey: 0xd39c1775e98a73fd0a9c8ecac8c9fedb9bb81e45

Options:

  • Option A: Return the funds to specified address
  • Option B: Further Discussion needed

Off-Chain Vote

Accept the proposal
27.41K VLT90.8%
Further Discussion needed
2.78K VLT9.2%
Download mobile app to vote

Timeline

Jul 12, 2023Proposal created
Jul 12, 2023Proposal vote started
Jul 19, 2023Proposal vote ended
Oct 26, 2023Proposal updated