New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
0xdf21b894a490cbdf49d9de7b9d780b79f7cb0ac7 #15
Comments
Full List.csv |
The safe has been created continuously by this address. |
Just creating a number of Safes with the same account is not airdrop farmingf per se - could you please elaborate on how you get to the conclusion that it's in fact airdrop farming?
I just checked the first address, there are a number of txs, hence "almost unused" is not really true. |
#301 this is the answer to 0xdf21 |
Ultimate answer. Must see #365 |
We haven't received any further information on this ticket and therefore deemed this submission invalid. Unfortunately just the pure fact that Safes...
... is not enough reasoning for a valid submission, as there are legit user behaviour leading to such as well (relayer, scripts, power users, exchanges) This submission didn't provide sufficient indicators to convince the team that there is some targeted airdrop farming behind the provided addresses. As per the rules, when in doubt we will default in favor of the airdrop recipients in order to not risk any false positives when sorting out airdrop hunters. |
Related Safe Addresses
Example List:
Full List
"https://etherscan.io/txs?a=0xdf21b894a490cbdf49d9de7b9d780b79f7cb0ac7&p=8"
-->
Reasoning
<--Each safe is almost unused but all created with the same address.0xdf21b894a490cbdf49d9de7b9d780b79f7cb0ac7
Safes are created with high frequency
-->
Methodology
MY Safe Address
<--
0xd052e46724C64e554F21C7d256A639d171692494
-->
The text was updated successfully, but these errors were encountered: