Skip to content

About

A self-hosted blockchain scanner that delivers matching transactions to applications watching addresses across 18 networks.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Repository files navigation

ChainScanner

ChainScanner

Watch blockchain addresses and receive their transactions over WebSocket, gRPC or HTTP.

English · 简体中文 · Tiếng Việt · Español · Русский

Go 1.25+  ·  MIT  ·  17 networks

Quick start  ·  Networks  ·  API reference


Why we built ChainScanner

While developing GM Wallet and GMPay, we kept running into the same problem. The wallet needed to know which balances to refresh, and the payment service needed to know when a receiving address had new activity. Polling RPC endpoints for each address in each app spent quota twice when both apps were looking for the same transaction.

ChainScanner gives all subscribers on a network a shared block scan. Each service receives transactions that match its addresses and acknowledges them independently. A wallet can refresh just the affected balances, while GMPay can verify the corresponding orders. In an Ethereum mainnet replay, reading the same four blocks took 11 upstream RPC calls when watching one address, when watching 100 addresses, and when two services watched those same 100 addresses.

Each application manages its own business logic, order status and wallet balances. ChainScanner provides shared infrastructure for address subscriptions, block scanning and event delivery.

Important

Public RPC limits for frequent transaction lookups on Solana, TON (GRAM) and Plasma. Strict verification needs matching results from two independent providers. In a 15-minute mainnet test using free public RPCs, all three strict lookups failed on Solana and all three failed on Plasma. All three succeeded on TON. If you expect frequent lookups, configure two fallback nodes per network, each from a different provider. ChainScanner scans each block once for all watched addresses and subscribers, reducing duplicate RPC requests. At most providers, a free or entry-level plan is usually enough for occasional block retries and transaction checks. For sustained traffic, check each plan’s rate limit and monthly quota. Configure fallback nodes · Compare fallback providers

Use cases

  • On-chain checkout. The EPUSDT integration subscribes to deposit addresses, marks a matching order as confirming and checks the transaction with two nodes before crediting it.
  • Telegram wallet bot idea. Subscribe to a personal address, record each delivery, then send a message identifying an incoming or outgoing transfer.
  • Treasury reconciliation idea. Watch operational wallets once and deliver the same activity to accounting and alerting as separate consumers, each with its own acknowledgement.

Subscribe to an address

With a local server running, use the consumer token from the quick start as $TOKEN. Replace the example with your Base address. This request sets the consumer’s entire watch list.

curl -fsS -X PUT http://127.0.0.1:9081/v1/subscriptions \
  -H "Authorization: Bearer $TOKEN" \
  -H 'Content-Type: application/json' \
  -d '[{
    "network": "base",
    "address": "0x1111111111111111111111111111111111111111"
  }]'

The response includes from_height, the first block covered. Receive and acknowledge transactions

Recommended fallback node

Register two independent fallbacks on the same network by calling the endpoint once per provider. Failed ranges rotate across eligible fallbacks. Strict lookups prefer two fallback votes. With only one eligible fallback, an ordinary node can supply the other vote. API

BASE=http://127.0.0.1:9081
ADMIN_TOKEN=$(jq -er '.admin_token' chainscanner.json)
curl -fsS -X POST "$BASE/v1/admin/nodes/fallback" \
  -H "Authorization: Bearer $ADMIN_TOKEN" \
  -H 'Content-Type: application/json' \
  -d '{"network":"base","protocol":"http","url":"https://paid-rpc.example.org","api_key":"YOUR_PROVIDER_KEY"}'

Fallback providers

Provider shortlist, checked 2026-11-21. Choose independently. ChainScanner does not guarantee availability, data accuracy or pricing. Credits, CU and RU depend on the RPC method and are not interchangeable. Check network, history and protocol support for both endpoints.

Website Founded or first public release Free allowance
Ankr 2017 · distributed node infrastructure 200M API credits/month with a Freemium account
Infura 2016 · Consensys Ethereum and IPFS infrastructure 3M credits/day on Core, per the pricing documentation
PublicNode 2018 · operator Allnodes began offering node infrastructure Shared public RPC, no fixed per-user monthly allowance published
QuickNode 2017 · managed multichain RPC and data streams 10M API credits for a 30-day trial
Alchemy 2017 · blockchain developer APIs and node access 30M CU/month
BlockPI 2022-10-25 · distributed RPC network alpha launch 50M RU/month for registered users
dRPC 2023-03 · decentralized RPC gateway opened to the public 50M CU per 30 days

A note from the maintainers

If your project uses ChainScanner or builds on its design, we’d appreciate a link in your README. Your recommendation helps other developers find us and means a lot to our team. We’re glad we could help. Thank you for using ChainScanner!

Reference: [ChainScanner](https://github.com/GMWalletApp/ChainScanner)

Thanks to imToken and Bitget Wallet for public RPC resources, and to ChainList, OpenChainBench and CompareNodes for their public node directories. Thank you to everyone who uses and trusts ChainScanner.

About

A self-hosted blockchain scanner that delivers matching transactions to applications watching addresses across 18 networks.

Topics

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages