Exchange Hot and Cold Wallet Labels API
Tell exchange-operated wallets apart from ordinary wallets. Bitquery labels more than 10,000 exchange hot and cold wallets and more than 400,000 proof-of-reserves addresses across EVM chains, Bitcoin, Tron and Solana.
ProductUsing this in production? See the Address Labels API page for plans, free trial and enterprise delivery options.
What it is
Label.Type | Meaning | Example Label.Value |
|---|---|---|
cex-hot-wallet | Wallet the exchange uses for withdrawals and daily operations | binance-hot, okx-hot, kraken-hot-1, upbit-hot |
cex-cold-wallet | Exchange cold storage | binance-cold, okx-cold, coinbase-cold, bybit-cold |
proof-of-reserves | Address the exchange lists in its proof of reserves | okx-proof-of-reserves, binance-proof-of-reserves |
Customer deposit addresses are a separate type. See Exchange Deposit Address Labels.
How to get it
Query the Metadata.Labels cube of the Address Labels API with the three types:
{
Metadata {
Labels(
where: {
Address: {in: [
"0x28c6c06298d514db089934071355e5743bf21d60",
"0x03ffb8cc16499d20cf79261ebc7064f72984330e",
"34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo"
]}
Label: {Type: {in: ["cex-hot-wallet", "cex-cold-wallet", "proof-of-reserves"]}}
}
limitBy: {by: [Address, Chain, Label_Type], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Chain
Label {
Type
Value
}
}
}
}
The response identifies a Binance hot wallet on several EVM chains, an OKX cold wallet that is also in OKX's proof of reserves, and a Binance Bitcoin cold wallet.
How it is derived
Bitquery's labelling pipeline compiles each label from many inputs and returns one finished result: a type, a value and the date it was recorded. Responses carry the label itself, not a per-label source reference.
Fields
| Field | Meaning |
|---|---|
Address | The address you queried |
Chain | Chain the label applies to |
Label.Type | cex-hot-wallet, cex-cold-wallet or proof-of-reserves |
Label.Value | Exchange slug plus the role. A number suffix such as -hot-1 separates wallets of one exchange |
RecordedAt | When the label was added to Bitquery's label table |
Examples
Remove exchange wallets from a top-holders list
Take the holder addresses from the Balances and Holders cubes, run them through this query, and drop every address that returns a row. What remains is closer to real holder concentration.
Keep only cold storage on one chain
{
Metadata {
Labels(
where: {
Address: {in: [
"0x03ffb8cc16499d20cf79261ebc7064f72984330e",
"0x28c6c06298d514db089934071355e5743bf21d60"
]}
Label: {Type: {is: "cex-cold-wallet"}}
Chain: {is: "ethereum"}
}
limitBy: {by: [Address], count: 1}
orderBy: {descending: RecordedAt}
) {
Address
Label {
Value
}
}
}
}
Only the OKX cold wallet comes back.
Pitfalls
- A withdrawal comes from the exchange, not a person. A transfer out of a
cex-hot-walletis an exchange payout. Do not treat the hot wallet as the trader. - Roles can overlap. One address can be both
cex-cold-walletandproof-of-reserves. KeepLabel_TypeinlimitByto see both. - Lowercase EVM addresses. A checksummed address returns no rows.
Get the full dataset
The complete list of labelled exchange wallets is part of the Address Labels dataset on the Bitquery Data Store. Use it when you need every exchange wallet at once, for example to tag a whole transfers table.
Frequently Asked Questions
How do I find out if a wallet belongs to an exchange?
Query Metadata.Labels with the address and filter Label Type to cex-hot-wallet, cex-cold-wallet and proof-of-reserves. Label.Value names the exchange and the role, for example binance-hot or okx-cold.
What is the difference between a hot wallet and a deposit address label?
A hot wallet is operated by the exchange and pays out withdrawals. A deposit address is assigned to one customer and uses the type cex-deposit-address.
Which chains are covered?
Exchange wallet labels cover Ethereum, BNB Chain, Arbitrum, Base, Polygon, Bitcoin, Tron, Solana and more. One EVM address is usually labelled on every chain where the exchange uses it.
Related
Ready to run this in production?
Get an API key and run these queries in minutes, or talk to us about plans and enterprise delivery.