Were unintentionally excluded from the distribution.
So we’ll need to do a governance proposal to get tokens to them.
Please approve this proposal so that Users who were POD participants on Pooltogether and also fit the requirements of the Airdrop be airdropped the POOL token.
Hey Torgin, dm’d you a a day or two ago, I also dm’d Leighton and he responded this: Yes, we’ve looked into it and we fond that there were
17 USDC Pod users
270 Dai Pod users
So I guess the addresses are already on your database, but we as users have no clue on how to calculate the rewards, is there anything I can do to help?
I also whole heartedly support this proposal. I think it will be a nice gesture to the community to also include other small holders who were left out from the airdrop.
After several users reported the issue of not receiving any POOL, we investigated and discovered a bug in the original retroactive query code regarding Pods. Users that had deposited into the USDC Pod and the Dai Pod were not being compensated correctly. We’ve fixed the problem and are currently polishing the code in preparation for making it public.
I think this will make a great first proposal for the community, and will require the involvement of a technical community member.
I suggest:
The community looks at the revised drop and determines an appropriate distribution for the Pod users that were missed, or received less than they should have. This could be constructed as a simple CSV.
The CSV is published publicly to a Github repo
A developer forks the Merkle Distributor project and updates it to instead consume the CSV to generate the merkle proof.
The developer deploys the new Pod Merkle Distributor.
The community approves of a proposal to transfer the appropriate amount of POOL into the Pod Merkle Distributor contract. It’s important to note that the the community should verify the deployed contract’s merkle distribution!. It would be very easy to slip additional claims in.
The developer could be compensated in POOL for the gas spent and the time taken, as well. A proposal can have more than one transaction, so a second transaction could transfer POOL directly to the developers address.
I think this is a great issue for the community to tackle! We’ll have the amended code up for you all shortly.