Practical overview
When it fits
Use the repository when a wallet or integration needs structured ADAMANT asset data and must account for blockchain-level defaults or token-specific overrides.
Who it is for
- Developers building or maintaining ADAMANT wallet applications.
- Teams integrating structured asset and blockchain metadata into wallet interfaces.
- Developers creating tooling that uses the repository’s node and service details.
Documented uses
- Retrieve shared coin or token properties and associated icons for wallet display.
- Apply blockchain defaults and token-specific overrides in the documented order.
- Use node, service and health-check metadata as inputs for reliability-related tooling.
- Consult the OpenAPI specification for metadata object structure.
Requirements & limits
The repository contents are publicly available. A license is not specified in the provided repository evidence.
- Metadata is divided among shared asset records, blockchain defaults and token-specific overrides; consumers should apply them in that order.
- The JSON assets are the stated source of truth for current wallet metadata.
- Icon assets are identified for PWA and iOS apps, while the repository itself is a data resource rather than a finished wallet.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Resolve asset metadata with blockchain overrides
Assemble the metadata record for an asset, applying shared data, chain defaults and any token-specific overrides in the documented order.
Before you start
- Access to the repository’s JSON metadata files.
- The asset or token name and, where applicable, its blockchain.
Steps
Load shared metadata from
assets/general//info.json.If the asset belongs to a blockchain family, apply defaults from
assets/blockchains//info.json.For a token with chain-specific settings, apply
assets/blockchains///info.json.
Expected outcome
A layered metadata record for wallet display and behavior, following the repository’s stated override order.
Guide limitations
- The guide describes metadata composition only; it does not cover implementing or running a wallet.
- The JSON assets are the stated source of truth if they disagree with the README or OpenAPI schema.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- Adamant-im/adamant-wallets · Official homepage title · retained in its source language

