TL;DR

• Proposal to update eligible list to prevent fraud claims.

• We would like users to vote on three options of requirements for a new eligible list.

- Option A: Update the eligible list require At least one ERC-20 token Tx by 2022/7/12

- Option B: Update the eligible list require At least one ERC-20 token Tx by the airdrop application deadline (2021/9/20)

- Option C: Update the eligible list require At least one ERC-20 token Tx by the airdrop application deadline (2021/9/20) and “Last Tx Date is after the launch date (2022/2/22).”

- Option D: Restart the airdrop claim without any update

Background

We have identified multiple fraudulent accounts included in the current testnet airdrop eligible list.

Since the multiple claims by fraudulent accounts could cause the large sell pressure and it’s not aligned with our airdrop goal to expand the InsureDAO community, we are going to detect and exclude potential bot accounts as much as possible.

Examples of fraudulent accounts

1. The large amount of CLAIMs in a short time

2. Send that claimed INSURE token to another address

3. Sold in large quantities

The Large amount of CLAIMs

https://etherscan.io/tokentxns?a=0x98E5790f343b83E850C20fb2D100B28dE5e8AEEB&p=11

Multiple addresses are being grouped together into one address after Claim & Sold in large quantities

https://etherscan.io/address/0xc88444c3db2c49bd96b4f12ac5b3c66896328be8#tokentxns

Proposal

Update the Eligible list by excluding wallet addresses without any ERC-20 token Tx.

In order to eliminate fraudulent users, we investigated each potential fraudulent address and found the common feature shared by those addresses. In short, they have never sent an ERC-20 token transaction. Thus, we decided to eliminate those addresses and update the Eligible list.

Adding to the number of Tx, we also consider screening the list with additional criteria, the tx date.

In this proposal, we are proposing Option A~C, which has different requirements for the tx date each.The results after the update for each Option are shown in the table below.

We would like users to vote on which Option should be adopted.

The eligible list with each Option applied is below

Eligible list

Where exclude goes

As for the exclude Token destination, excluded INSURE tokens will be distributed toward the community treasury, and community treasury will be utilized by DAO governance in the future.

Voting power

1vlINSURE -> 1 veINSURE 1veINSURE -> 1 veINSURE A quorum of at least 35k veINSURE is required for snapshot voting.