Skip to content

meronym/erc20-scanner

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

22 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

ERC20 Scanner

Monitors the balance changes of an ERC20 token contract.

This is a bytecode analyzer that scans through the traces of a given transaction and figures out which token holder addresses had their corresponding balances changed as a result of the tx execution.

This approach should work for any Solidity-based ERC20 contract, no ABI or source code needed. It also detects changes that happen at the time of contract creation (“pre-mines”) and hard-coded balances. Since it doesn’t rely on logs, it should catch minting/burning and other custom balance shifts as well, regardless of the emitted Transfer() events.

get_nonce.py

Scans an ERC20 transfer tx to identify the internal nonce that's associated with the storage pattern of the balances map in the token contract.

Current heuristic

This can be improved, but works for now.

  • We start with a sample tx that is guaranteed to include a single Transfer event for the token we're interested in.
  • The script replays the transaction (via a Parity trace_replayTransaction call) and analyzes the state diffs to collect a set of storage location keys that got changed by the execution of the transaction. The keys associated with the balances that got changed during the transfer are a strict subset of this set of keys.
  • We ask Parity to simulate a balanceOf(sender) and compile a list of all values that circulated on the stack during this call.
  • We expect that the only common element of the two sets created above will be the storage location key of the balance for the token sender, which needs to be accessed by both routines. Let this key be called sender_sloc.
  • We know that sender_sloc = sha3(sender + nonce) where nonce is a unique value allocated by the Solidity compiler to the internal balances mapping. We assume all versions of Solidity use the same memory mapping strategy [needs to be validated]. This allows us to brute force the nonce in very few steps, as the compiler typically allocates the nonce values in increasing order starting from zero and there is a small upper bound on how many data structures (hence nonces) will be defined in the typical token contracts.

Example

$ python get_nonce.py 0x7cd824bc5c11a16dc52f738fef5c6e3aca923af7a7cd9ecc136547c9606eac13

Token contract: 0xb8c77482e45f1f44de1745f52c74426c631bdd52
Balance map nonce: 5

scan.py

Receives a nonce and a tx. Analyzes the execution of tx and identifies the holder addresses whose corresponding balances have changed - by looking at the internal contract map identified by nonce.

Current method

  • Gather the set of storage location keys that were changed in the contract as a result of executing tx
  • Gather all 'address-like' values that got pushed on the stack while executing tx. We assume these to be the only possible address values whose balance could have changed as a result of tx.
  • We compute a rainbow table that maps each sha3(candidate + nonce) back to candidate. We expect to process a max. of ~1000 candidates for an average token transfer transaction, so this step is not too computationally intensive and doesn't need external caching/pre-processing.
  • We scan through the storage location keys that got touched during the execution (by looking at the state diffs) and for each key we make a lookup in the rainbow table. If the preimage of the hash is found there, we know that this value corresponds to the balance mapping of the candidate.
  • This makes it possible to export an event each time a balance key is touched, on the form BalanceChange(holder_address, old_value, new_value)

Analysis

Both the time and memory complexity are linear in the number of values that get pushed in the VM stack when the tx gets executed, which in turn has an upper bound on the block gas limit. This makes retrieving the traces from Parity the main computational overhead. Other than that, the number of sha3 computations is relatively small (<1000) for analyzing a transaction.

Example

  • Scanning a contract deployment transaction outputs the tokens allocated in the constructor code.
$ python scan.py --nonce=5 0x436fc7d21ed4a0a634f41b50ccb42fca12be7322de5bf9a20c97bdccbb5b2a04

Analyzing 39 candidates...
Holder:0x00c5e04176d95a286fcce0e68c683ca0bfec8454 +200000000000000000000000000 Tx:0x436fc7d21ed4a0a634f41b50ccb42fca12be7322de5bf9a20c97bdccbb5b2a04
  • Scanning a standard ERC20 transfer transaction
$ python scan.py --nonce=5 0x9934bb687357d81d8d92076ba63164cc3ee8f5d5c7a9ce2f0c64c27b707abca1

Analyzing 56 candidates...
Holder:0xab6e89eae31e9f8053a77f743a78e5e858595407 +13016785137944555173 Tx:0x9934bb687357d81d8d92076ba63164cc3ee8f5d5c7a9ce2f0c64c27b707abca1
Holder:0x52fc65ef2937cc83c4f70685562283ab8f690e33 -13016785137944555173 Tx:0x9934bb687357d81d8d92076ba63164cc3ee8f5d5c7a9ce2f0c64c27b707abca1

TODO

  • Check compatibility with openzeppelinos / proxy, upgradeable contracts
  • Check compatibility with Augur (forking and stuff)
  • Check compatibility with Jordi's MiniMe (e.g. Status Token)

Setup

  • Clone the repository
  • Make sure you're running Python 3 (no external code dependencies, so no need for using Pip or the like)
  • Tunnel your localhost:8545 to a json-rpc instance of Parity with --tracing support enabled
  • Run python get_nonce.py or python scan.py as described above. Or use --help to get minimal rescue

Showcase

Everything below relates to mainnet data and pricing information as of February 2019.

Binance Token (BNB)

https://etherscan.io/address/0xB8c77482e45F1F44dE1745F52C74426C631bDD52#code Market cap: $842M

$ python get_nonce.py 0x7cd824bc5c11a16dc52f738fef5c6e3aca923af7a7cd9ecc136547c9606eac13

Token contract: 0xb8c77482e45f1f44de1745f52c74426c631bdd52
Balance map nonce: 5
  • Opaque initial allocation in the contract constructor - doesn't emit Transfer().
$ python scan.py --nonce=5 0x436fc7d21ed4a0a634f41b50ccb42fca12be7322de5bf9a20c97bdccbb5b2a04

Analyzing 39 candidates...
Holder:0x00c5e04176d95a286fcce0e68c683ca0bfec8454 +200000000000000000000000000 Tx:0x436fc7d21ed4a0a634f41b50ccb42fca12be7322de5bf9a20c97bdccbb5b2a04
  • Available balances can change via non-standard freeze() and unfreeze()
$ python scan.py --nonce=5 0x72af0f55b97b033af3b6e6162463681730c6429d0bc9c6c6ae9ad595aa2fbc57

Analyzing 59 candidates...
Holder:0x00c5e04176d95a286fcce0e68c683ca0bfec8454 -64000000000000000000000000 Tx:0x72af0f55b97b033af3b6e6162463681730c6429d0bc9c6c6ae9ad595aa2fbc57
  • Emits Burn() instead of Transfer(_, 0x0)
$ python scan.py --nonce=5 0xbc4290d9bd404f03575db80446bd82954698c3fe99729d1eb098a765bb0e479b

Analyzing 44 candidates...
Holder:0x24b29cc8a5570bf728bd56679e1089d6c27891bb -10 Tx:0xbc4290d9bd404f03575db80446bd82954698c3fe99729d1eb098a765bb0e479b

BasicAttentionToken (BAT)

https://etherscan.io/address/0x0d8775f648430679a709e98d2b0cb6250d2887ef#code Market cap: $140M

$ python get_nonce.py 0x52eb28f810dc413588d320d0fce5d58a755d7deb815c4ac5a8438c6f0c21fe6b

Token contract: 0x0d8775f648430679a709e98d2b0cb6250d2887ef
Balance map nonce: 1
  • Creates token supply with dedicated ICO functions, logs it with a custom CreateBAT() event
$ python scan.py --nonce=1 0x3bf792736cea9760b7cb604dc5b6527f5b9ddd3d3f7db046fa4103ac489d7626

Analyzing 38 candidates...
Holder:0x88e2efac3d2ef957fcd82ec201a506871ad06204 +500000000000000000000000000 Tx:0x3bf792736cea9760b7cb604dc5b6527f5b9ddd3d3f7db046fa4103ac489d7626
  • Participants can ask refunds during the ICO, these are logged with a custom LogRefund() event

0X (ZRX)

https://etherscan.io/address/0xe41d2489571d322189246dafa5ebde1f4699f498#code Market cap: $146M

$ python get_nonce.py 0xeea79c5e417ffb23d15c44d6ac4e49279c43a310faa8e6de6695ece117f8097e

Token contract: 0xe41d2489571d322189246dafa5ebde1f4699f498
Balance map nonce: 0
  • Doesn't log initial token allocation in constructor
$ python scan.py --nonce=0 0xbdab447ba2fd0a493d93635da202ebcfaa309bcc6a22a95d808c93ce8f1c6c2d

Analyzing 12 candidates...
Holder:0xa3b2d1087bcebe59d188a23f75620612d967df72 +1000000000000000000000000000 Tx:0xbdab447ba2fd0a493d93635da202ebcfaa309bcc6a22a95d808c93ce8f1c6c2d

FirstBlood Token (ST)

https://etherscan.io/address/0xaf30d2a7e90d7dc361c8c4585e9bb7d2f6f15bc7#code Market cap: $2M

$ python get_nonce.py 0x62289182c4154e9220c1bb25a43f8bca669224b82f66491344994e6c6b57eb34

Token contract: 0xaf30d2a7e90d7dc361c8c4585e9bb7d2f6f15bc7
Balance map nonce: 0
  • Initial allocations from allocateBountyAndEcosystemTokens() are not logged.
$ python scan.py --nonce=0 0xfeadc97031765564aa55be00c205f453fb9b8f78eb5c2338fa69e46a4ac2c0bb

Analyzing 121 candidates...
Holder:0xa5384627f6dcd3440298e2d8b0da9d5f0fcbcef7 +6455160169530275892500000 Tx:0xfeadc97031765564aa55be00c205f453fb9b8f78eb5c2338fa69e46a4ac2c0bb

Maker (MKR)

https://etherscan.io/address/0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2#code

Market cap: $276M

  • Emits Mint() and Burn() instead of Transfer(_, _)

Holo (HOT)

https://etherscan.io/address/0x6c6ee5e31d828de241282b9606c8e98ea48526e2#code

Market cap: 166M

  • Emits a Mint() event instead of Transfer(0x0, _)
  • Non-standard Burn() event, doesn't log the holder address

ChainLink Token (LINK)

https://etherscan.io/address/0x514910771af9ca656af840dff83e8264ecf986ca#code

Market cap: $140M

  • Doesn't log initial token allocation in constructor

About

Low-level monitor for ERC-20 balance changes

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages