Token API returns total_supply (via the circulating_supply field) values that consistently differ from the on-chain totalSupply() reported by block explorers. The divergence is stable across every validation run — not caused by indexing lag.
The highest-impact cases on arbitrum-one:
| Token |
Contract |
Our Value |
Explorer Value |
Diff |
| SUSHI |
0xd4d42f0b6def4ce0383636770ef773390d85c61a |
65.9M |
500K |
130x |
| ARB |
0x912ce59144191c1204e64559fe8253a0e49e6548 |
60.4B |
10.0B |
6x |
| AAVE |
0xba5ddd1f9d7f570dc94a51479a000e3bce967196 |
381K |
64K |
6x |
| GMX |
0xfc5a1a6eb076a2c7ad06ed22c90d7e710e35ad0a |
18.9M |
10.8M |
1.8x |
| GHO |
0x7dff72693f6a4149b17e7c6314655f6a9f7c8b33 |
2.0M |
3.1M |
0.6x |
Other networks:
| Network |
Token |
Contract |
Our Value |
Explorer Value |
Diff |
| mainnet |
VVS |
0x839e71613f9aa06e5701cf6de63e303616b0dde3 |
1.16e59 |
165B |
broken |
| mainnet |
HSK |
0xe7c6bf469e97eeb0bfb74c8dbff5bd47d4c1c98a |
345M |
1B |
0.35x |
| mainnet |
QNT |
0x4a220e6096b25eadb88358cb44068a3248254675 |
24.4M |
45.5M |
0.54x |
| mainnet |
EIGEN |
0xec53bf9167f50cdeb3ae105f56099aaab9061f83 |
1.46B |
1.80B |
0.81x |
| mainnet |
NMR |
0x1776e1f26f98b1a5df9cd347953a26dd3cb46671 |
13.6M |
10.6M |
1.28x |
| polygon |
POL |
0x0000000000000000000000000000000000001010 |
7.3B |
10B |
0.73x |
| polygon |
CRVUSD |
0xc4ce1d6f5d98d65ee25cf85e9f2e9dcfee6cb5d6 |
9.9K |
24K |
0.41x |
All mismatched in 5/5 of the most recent runs. Full list of 31 affected tokens available in the validation run report.
VVS on mainnet (value 1.16e59) is a special case — the value looks like a max uint256 or overflow artifact. VVS is natively a Cronos token; the mainnet contract may be a bridge wrapper.
Reference: Both Blockscout and Etherscan agree on the explorer values listed above.
Token API returns
total_supply(via thecirculating_supplyfield) values that consistently differ from the on-chaintotalSupply()reported by block explorers. The divergence is stable across every validation run — not caused by indexing lag.The highest-impact cases on arbitrum-one:
0xd4d42f0b6def4ce0383636770ef773390d85c61a0x912ce59144191c1204e64559fe8253a0e49e65480xba5ddd1f9d7f570dc94a51479a000e3bce9671960xfc5a1a6eb076a2c7ad06ed22c90d7e710e35ad0a0x7dff72693f6a4149b17e7c6314655f6a9f7c8b33Other networks:
0x839e71613f9aa06e5701cf6de63e303616b0dde30xe7c6bf469e97eeb0bfb74c8dbff5bd47d4c1c98a0x4a220e6096b25eadb88358cb44068a32482546750xec53bf9167f50cdeb3ae105f56099aaab9061f830x1776e1f26f98b1a5df9cd347953a26dd3cb466710x00000000000000000000000000000000000010100xc4ce1d6f5d98d65ee25cf85e9f2e9dcfee6cb5d6All mismatched in 5/5 of the most recent runs. Full list of 31 affected tokens available in the validation run report.
VVS on mainnet (value 1.16e59) is a special case — the value looks like a max uint256 or overflow artifact. VVS is natively a Cronos token; the mainnet contract may be a bridge wrapper.
Reference: Both Blockscout and Etherscan agree on the explorer values listed above.