search

safe-global / safe-user-allocation-reports

The proposed list of SAFE user allocations has been published on the Safe forum.
Creative Commons Zero v1.0 Universal
34 stars 10 forks source link

What is the definition of airdrop farmer? Seems Safe team also have no answer. #506

Closed Neverlander0 closed 2 years ago

Neverlander0 commented 2 years ago

First, Safe team give the reason for invalid report like this:

图片

Rule 1、were created by the same address 2、have the same owner 3、conducted the same transactions 4、received assets from the same address 5、receive the same amount of SAFE

and now we see some valid reports.

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/246 Just the same owner to be a valid report? about Rule 2

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/219

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/218

Just conducted the same transactions and be a valid report? about Rule 3

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/223

Just Same create time and Same airdrop amount? about Rule 5

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/115

Just Same creator and Same transactions ? about Rule 1 and 3

图片 https://github.com/safe-global/safe-user-allocation-reports/issues/58

Just Same creator and Received assets from the same address ? about Rule 1 and 4

Actually all valid reports is all about the five rules , i don't want to elaborate one by one.

I don't means valid reports above all is invalid, i just feel unfair.

What i want to say is the Safe team need to have more justice and patience.

If a batch of Safe wallets 1、were created by the same address (may be a relayer) 2、have the same owner 3、conducted the same transactions (all of them have only one) 4、received assets from the same address (may be not) 5、receive the same amount of SAFE

Dont u think they are real users and deserve Safe airdrop?

https://github.com/safe-global/safe-user-allocation-reports/issues/486 https://github.com/safe-global/safe-user-allocation-reports/issues/467 https://github.com/safe-global/safe-user-allocation-reports/issues/466 https://github.com/safe-global/safe-user-allocation-reports/issues/465 https://github.com/safe-global/safe-user-allocation-reports/issues/463

If u think they deserve ,that's all right, it's your choice. but some valid reports also have relations with 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D ,how could you explain it ? https://github.com/safe-global/safe-user-allocation-reports/issues/246 https://github.com/safe-global/safe-user-allocation-reports/issues/219 https://github.com/safe-global/safe-user-allocation-reports/issues/218

Why these reports can be valid? What is difference deciding valid or not between them and my reports about 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D , Could you elaborate it plz?

Finally,these reports about 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D are marked as staker. https://github.com/safe-global/safe-user-allocation-reports/issues/228 https://github.com/safe-global/safe-user-allocation-reports/issues/237

And my reports about 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D were just closed without even a chance for discussion. Is it the way your Safe team do ? We also spend lots of time on sybil-attack reports and you just close my reports in batch lol.

No matter what the final result is ,my reports should be reopened and labelled as staker,i think it would be fair enough. https://github.com/safe-global/safe-user-allocation-reports/issues/486 https://github.com/safe-global/safe-user-allocation-reports/issues/467 https://github.com/safe-global/safe-user-allocation-reports/issues/466 https://github.com/safe-global/safe-user-allocation-reports/issues/465 https://github.com/safe-global/safe-user-allocation-reports/issues/463

Please check @tschubotz @lukasschor