FeedProjects
Developers
Settings
🎉 A new chapter begins: Boardroom has joined Agora
Learn more
protocol logo
Explore / Projects
Indexed

Proposals

Members

Information

Create Proposal

Indexed

ProposalsMembersInformation
Proposal
Back to Proposals
closedEnded 4 years ago · Snapshot (Offchain)

Return assets drained to NDX Treasury by Proposal 16 to affected tokenholders

By 0x0000...C0bA6E

In November, the Indexed DAO passed Proposal 16 to drain the assets remaining in DEFI5, CC10, FFF and their respective market pairs. After the October hack, these pools were no longer functioning and were losing value. Proposal 16 was intended to prevent further losses by transferring the assets underlying the affected pools to the DAO, where they would be used to fund a compensation plan.

The gist of this compensation plan was that these assets would be sold into DAI, which would subsequently be moved into a pot which would be split by everyone that lost funds in the hack.

A couple of weeks ago, Dillon and Laurence put forward a proposal to use some of those assets for a different but related purpose, namely to fund the proposed class action lawsuit we’ve filed, which we viewed as the best opportunity to return the most value to all affected tokenholders.

While the Snapshot proposal for this plan was unanimously in favour, we have now reconsidered and no longer wish to pursue that course of action, as we don’t believe this approach is fair to all tokenholders. After the Snapshot vote was announced, one significant holder of both DEFI5 and NDX tokens contacted us through legal counsel to object to this plan to use assets from Proposal 16 to fund a lawsuit that they do not wish to participate in. Further, the user has requested that the DAO return the assets from Proposal 16 rather than use them to fund the compensation plan.

Some affected users chose to burn their tokens back into their underlying assets prior to Proposal 16. As a result, assets retrieved from that proposal were taken from those that did not do so. As such, going through with the compensation plan would effectively result in taking value away from users who recovered nothing in the aftermath and transferring it to users who recovered something (by burning their tokens).

In the time since November, some users have had a chance to reflect on their decision not to burn their tokens. Some users who were less active or less sophisticated may not have been aware of Proposal 16 or may not have understood its significance (and may still not understand them). These users may have acted differently if they understood the consequences.

As a result, we have taken no further action relating to the assets from Proposal 16, and propose unwinding Proposal 16 to the extent of returning the drained assets to the tokenholders affected by the drain.

This would be done as follows:

  • Setting up a Merkle distributor dictating the assets that affected users would have been able to burn their tokens (or LPs) for had they done so prior to the execution of Proposal 16,
  • Moving all drained assets from the DAO Treasury via a Governor Alpha vote to a separate - industry-standardised - smart contract with no expiry time on claims,
  • Creating a web interface for the affected to claim their assets (e.g. UNI, CRV, SUSHI),
  • Advertising the existence of said interface via Discord, Twitter, Telegram and the Indexed site itself.

We believe that the execution of this proposal will allow the DAO to draw a line underneath the ownership of affected assets, and grant the affected a degree of immediate relief in terms of assets available to them. We ask the rest of the Indexed DAO to join us in supporting its passing, both in this off-chain consensus gathering phase and - should this step pass - when its implementation is put forward for on-chain execution via Governor Alpha.

If you wish for the above to be executed, please vote “Yes: execute”. If you do not, please vote for “No: do not execute”.

The vote will run for 7 days - a majority vote in favour with 400,000 NDX votes cast will be considered a signal for the requisite Merkle tree and smart contracts to be built, and a proposal to execute the above put on-chain.

Continue Reading
Connect Wallet to Add Note
0
Votes 28
VoterCast PowerVote & Rationale
0x7322...E52303
574,851

Yes: execute

0x9D31...93abb5
400,002

Yes: execute

0xaeE1...11cbaC
159,226

Yes: execute

0xef76...E3F8dB
134,284

Yes: execute

0xE7f4...0F153e
61,593

Yes: execute

SHOW MORE
VOTE POWER
0
Connect Wallet
Proposal Status
  • Mon March 28 2022, 11:47 pmVoting Period Starts
  • Tue April 05 2022, 11:00 amEnd Voting Period
Current Results

1-Yes: execute

1.383M

DocumentationBrandingContact Us
Home
This Project is Currently Disabled

If you would like to enable it, please checkout below.

Boardroom Subscription

Sign up for an individual subscription (access all projects on the platform)

Subscribe
Enable Project

Enable the entire project for every user

Enable Project
Contact Us