EXECUTED

Ends Jan 11 at 10:15 AM UTC

[EP2] Retrospective Airdrop Enacts EP2 as approved by Snaps...

Proposed byBy

on Jan 5, 2022

[EP2] Retrospective Airdrop Enacts EP2 as approved by Snapshot vote, and described in full here: https://github.com/ensdomains/governance-docs/blob/main/governance-proposals/ep2-executable-retrospective-airdrop-for-accounts-that-owned-another-accounts-primary-ens-1.md

Votes

Quorum progress: 329.05%

For votes: 3.29M

Against votes: 82.77K

0x9831...6744voted for

470.79K

0x81b2...581avoted for

371.59K

0xb8c2...67d5voted for

321.38K

0xbdb4...f1dcvoted for

298.46K

0xed11...bb04voted for

273.69K

0x809f...f68evoted for

258.37K

I am in favor of airdropping both for the edge cases and the locked ens due to accidental send–although I previously voted against the second case because I thought it should be done in a separate transaction at a later time.

0x2b88...7d12voted for

234.95K

0x8393...0780voted for

177.28K

0x54be...7ab6voted for

173.94K

0x1904...a561voted for

167.91K

0x399e...5541voted for

132.57K

0x8ab1...c9e6voted for

61.49K

0x0457...13dbvoted for

59.47K

0x48db...d85dvoted for

56.36K

0xbc8d...7c63voted for

54.73K

0x7ae9...0c0bvoted against

45.42K

https://discuss.ens.domains/t/retrospective-2x-airdrop-multiplier-application-process-for-unfortunate-edge-cases/5795/18

0xf07a...d89cvoted against

36.22K

I do not believe we should relitigate previous airdrop decisions. Leads to a slippery slope of individuals trying to justify future rewards and chewing up DAO resources.

0x6e0d...6f62voted for

31.38K

The users included in this retrospective airdrop were meant to be included in the initial airdrop but were not due to a technical issue. I am supportive of resolving that issue through this proposal.

0x3335...81e1voted for

27.9K

0x8d07...a265voted for

25.53K

0x7b34...e9ecvoted for

24.14K

0xe11d...a20bvoted for

11.4K

0x48a6...fab0voted for

10.02K

0x782c...153fvoted for

8.53K