Parsing and collecting public wallets from CEX (Etherscan + L2)
Brief: need to compile a database of all publicly available (tagged/identified) wallets of centralized exchanges (CEX) in the Ethereum ecosystem and popular L2s (Arbitrum, Optimism, Base, zkSync, Polygon, etc.). The result is a clean deduplicated list
Mandatory tasks for the executor
Data Collection
Parse Etherscan/Arbiscan/Optimism Explorer/Base Explorer/zkSync Explorer/Polygonscan and similar (where applicable) to obtain addresses tagged as exchange (tags/labels), as well as publicly published deposit addresses from verified contracts/exchange pages.
Use official APIs (Etherscan API, etc.) and/or web-scraping where APIs do not provide the necessary tags.
Collect addresses explicitly marked as belonging to CEX (e.g., “Binance 1”, “Huobi Deposit”, “Coinbase Custody”, etc.).
Identification and Validation
- For each address, record: network, address, label, exchange name (if available)
Outputs / Formats
Main output: .xlsx and .csv with columns (at minimum):
address(checksum)network(ethereum/arbitrum/optimism/base/zkSync/polygon/…)exchange_name(if defined)
If there is a ready-made solution - very good.
-
1251 35 1 3 Hello Sergey, I will do it.
I have extensive experience working with crypto exchange APIs, web3, blockchain.
Write to me privately, we will discuss the terms.
-
2536 51 1 I can compile a database of all public exchange wallets CEX in the Ethereum and L2 networks (Arbitrum, Optimism, Base, Polygon, zkSync). I will use the official APIs of Etherscan-compatible explorers, as well as additional page parsing with tags, to obtain all “exchange-tagged” addresses. The result will be a clean deduplicated list in CSV/XLSX format with the fields address, network, exchange_name. I can create an asynchronous implementation for fast collection, and optionally — a utility script that can be run repeatedly to update the database.
Sincerely,
Andriy