Open a0910841082130913312 opened 2 years ago
Your API keys are in the Python file.
As additional evidence, I found that many of these addresses have identical timestamps in the provided user data. I believe this means their first Hop transfer was executed in the same block?
address | totalTxs | totalVolume | timestamp | diff (seconds)
0xac9d1dacc304715b4d47791cc937b19dbeedb907 | 12 | 1687.89 | 1639637195 | NaN
0xf225295bf689dfc9eb2a2305ec7b4d505c92a4f8 | 12 | 1691.26 | 1639637195 | 0
0xcf2a1afe14bc0c9ecbda9142415c078d76c3325a | 12 | 1688.68 | 1639637200 | 5
0x1a03dea2fbd2e338ff25382c2eae97a163a48fee | 12 | 1689.36 | 1639637205 | 5
0x2691dfa2997382738783fbca51e4424fab8bb2a5 | 12 | 1690.7 | 1639637205 | 0
0x2ec75b5178ce60d1ba7c2e6d59c41e5eea2f127e | 12 | 1686.16 | 1639637205 | 0
0x486e84bc8f5ff529169d62f7c8230dd906db8b50 | 12 | 1688.56 | 1639637205 | 0
0xf0cab4ad737ec90b087b9a2e5049e85b2d0acf84 | 12 | 1687.92 | 1639637205 | 0
0xf812bf8d5f8308d3449baec8e545a8413dc52bcb | 12 | 1689.26 | 1639637205 | 0
0xfc1237b84e686e6932948014afe32158c64aff3f | 12 | 1688.56 | 1639637205 | 0
0x6def6bb054bbdd89649ea18b9dc71a06ef4bfea2 | 12 | 1687.92 | 1639637210 | 5
0x40e32323fceb42b7d60ca5efff64ff4214b7bb26 | 12 | 1689.21 | 1639637245 | 35
0xc4b3da8bdae1a7d81819ba46efd880d87c2a4ca8 | 12 | 1689.57 | 1639637245 | 0
@0910841082130913312
Thank you for the submission. Unfortunately, this submission does not meet one of the criteria for submissions:
Methodology that has a non-negligible chance of eliminating legitimate users will not be considered
There will need to be additional proof submitted in order to consider this a valid group that does not include any legitimate users. Please consider providing more information about the behavior of these addresses, such as identical types of transactions or similar timing of transactions. Please note that another user that submits an issue with a detailed, non-negligible chance of eliminating legitimate users, their submission will be considered before yours.
Related Addresses
Reasoning
Addresses which receive native token (ETH on Arbitrum/Optimism/Ethereum, MATIC on Polygon) via disperse.app are controlled by the same user. Therefore, if two addresses in the airdrop list have received native token from the same disperse.app transaction, they should be counted as sybils.
Methodology
disperse.py
).disperse.py
,disperse_data.csv
).See
disperse_data_filtered.csv
for a list of disperse.app transactions that send native token to airdrop eligible addresses. Each row is one transaction (precisely, one internal transaction which sends native token), and all disperse.app transactions listed in this table send native token to two or more airdrop eligible addresses.Filtering was done with the following R code:
Rewards Address
0x61C1511D2645C1Fd1C5e71f07586d35779D85D79
Attachments
Provided as
.txt
as.py
cannot be uploaded: disperse.py.txt disperse_data.csv disperse_data_filtered.csv