Consistent wallet queries
Planned wallet-centred queries use a consistent format while retaining the network, address and requested scope. Cross-network views should not erase differences between networks.
Multi-Chain Wallet API / Planned
One API.
Multiple Blockchains.
Unified Wallet Data.
Access wallet information across supported blockchain networks through a consistent API. Retrieve wallet activity, discover assets and integrate blockchain data without maintaining separate integrations for every network.
Planned · no public production endpoint
CONTRACT DIRECTIONILLUSTRATIVE
{
"example": "future-wallet-view",
"networks": [
"illustrative-network"
],
"assets": [],
"assetUniverseComplete": false,
"historyComplete": false,
"synthetic": true
}This example explains a design principle. It is not a live API response or a stable production schema.
04 / Why this matters
One wallet view. Explicit network boundaries.
The long-term goal is a consistent way to request wallet information across supported networks. Network and asset identities must remain explicit: combining views must not suggest every network, token or historical period is covered.
Source evidence and interpretation should travel together. A downstream product must be able to distinguish observed data, a supported interpretation and an unresolved question.
The intended contract
Native coins, tokens and possible NFTs
Asset discovery is a product goal, not an available complete inventory. Native coins and tokens are intended scope; NFT discovery is a possible later extension. Unknown metadata and missing assets must remain visible.
Combined views with context
Bring supported wallet information together for tax, accounting, portfolio and financial applications. Exact quantities, data provenance and per-network coverage remain part of the result.
USE CASES / Built for technical teams
A better basis for your product.
Wallet and portfolio tools
Plan a consistent wallet view without maintaining a separate customer integration for every supported network.
Tax and accounting applications
Keep wallet facts, evidence and unknowns distinct from tax decisions and automatic bookkeeping.
Financial applications
Compare explicitly scoped wallet information across networks without assuming matching symbols identify the same asset.
What is available today?
Planned / Long-Term Product Vision. The Multi-Chain Wallet API is not publicly available. Ethereum and BNB Smart Chain are early target networks. Polygon, Arbitrum, Base, Solana and Bitcoin are possible later extensions, not an existing support list. Network and asset coverage will expand only as separately stated capabilities become available.
Read the implementation statusQUESTIONS / Multi-Chain Wallet API
Before you build.
Which networks can I query today?
None through a public Multi-Chain Wallet endpoint. Ethereum and BNB Smart Chain are targets, not available coverage. Additional networks are possible future extensions without release dates.
How does this differ from the other wallet products?
Wallet History concerns historical transactions; Historical Balance concerns holdings at a cutoff; Normalized Transactions provides consistently structured movements. This planned API focuses on wallet information across networks.
Is this the same as the Multi-Chain Data API?
No. The Multi-Chain Data API is a separate planned general blockchain-data offering, independent of individual wallets. See both directions on the product roadmap.
Does asset discovery guarantee every asset is found?
No. Coverage will be declared by network and asset type. An unknown or unsupported asset must not be treated as a zero balance, and a completed request is not a complete-history guarantee.
Built with a long view
Help shape the next
layer of blockchain data.
Explore the direction. Early access is not open yet.