There is an abnormal behavior that is understandable 🍄
However, if there are many abnormal behaviors, then there is enough reason to determine that these addresses are airdrop farmer.
All of group1 the owner is same 0x0d0051608c23c64533d10fef230f96bd31341a54, only this address
All of group2 the owner is same 0xe062084d2fec1c9334e67a9dcd7b4a12af98bc55, only this address
All of the multi-sign address, the behaviour is always same and stange .
99% of the group1 multi-sign adddress addOwner and removeOwner transaction took place from 2021-02-03 to 2021-02-15.(at the same tx, no exception)
99% of the group2 multi-sign adddress addOwner and removeOwner transaction took place from 2021-06-29 to 2021-06-30.(at the same tx, no exception)
The group1 and the group2 , All of them execute 1 transactions, add owner and remove owner in 1 tx, always the same tx.
the group1 add owner address is always 0x0d0051608c23c64533d10fef230f96bd31341a54 , remove owner address is always 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
the group2 add owner address is always 0xe062084D2FEc1C9334E67A9dcd7b4A12AF98bC55 , remove owner address is always 0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
Please Check Table
Address -- multi-sign address
Execute transactions -- The number of execute transactions by multi-sign address
Addresses are reported by retrieving information from the chain, using bitquery's graphql, and detecting abnormal behavior, such as empty wallets, mutual transfers, etc.
When only some of the anomalous behaviors are present, we can consider the address reasonable, but when an address has all the anomalous behaviors, we have good reason to suspect that the address is false. Especially if the multi-signature address and the owner address have obvious exceptions both, then it is obvious that this is airdrop farmer.
Abnormal behaviors include
For Multi-Sign Address
Few transactions were executed
There is a lot of overlap in the interactions, such as the destination address, and the time
The owner of multiple multi-signature addresses is exactly the same, and never changes from start to finish
For Owner Address
Empty address
The first source of funds is the owner.
Mutual transfer
Behavior similarity
If the verification is passed and my strategy is great, I can provide my source code, but for now it is not conveninet
Related Safe Addresses
Reasoning
All of group1 the owner is same
0x0d0051608c23c64533d10fef230f96bd31341a54
, only this addressAll of group2 the owner is same
0xe062084d2fec1c9334e67a9dcd7b4a12af98bc55
, only this addressAll of the multi-sign address, the behaviour is always same and stange .
99% of the group1 multi-sign adddress addOwner and removeOwner transaction took place from
2021-02-03
to2021-02-15
.(at the same tx, no exception)99% of the group2 multi-sign adddress addOwner and removeOwner transaction took place from
2021-06-29
to2021-06-30
.(at the same tx, no exception)The group1 and the group2 , All of them execute 1 transactions, add owner and remove owner in 1 tx, always the same tx.
the group1 add owner address is always
0x0d0051608c23c64533d10fef230f96bd31341a54
, remove owner address is always0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
the group2 add owner address is always
0xe062084D2FEc1C9334E67A9dcd7b4A12AF98bC55
, remove owner address is always0x66A0FF664f8509370C5D718A0f69AC1DC01f5c3D
Please Check Table
Methodology
Addresses are reported by retrieving information from the chain, using bitquery's graphql, and detecting abnormal behavior, such as empty wallets, mutual transfers, etc.
When only some of the anomalous behaviors are present, we can consider the address reasonable, but when an address has all the anomalous behaviors, we have good reason to suspect that the address is false. Especially if the multi-signature address and the owner address have obvious exceptions both, then it is obvious that this is airdrop farmer.
Abnormal behaviors include
For Multi-Sign Address
For Owner Address
If the verification is passed and my strategy is great, I can provide my source code, but for now it is not conveninet
Safe Address
0xce495858e36c95f491b5a32ca2664405cf10ab76
Thanks