Wallet Asset

Overview

Wallet assets can include native network coins, fungible tokens, non-fungible tokens, staking positions, liquidity shares, or tokenized claims. The wallet may discover them from blockchain data, a curated registry, user-added contract information, or a custody provider’s ledger.

Display does not prove legitimacy, ownership rights, or market value. Scam tokens can appear without consent, symbols can be duplicated, and token contracts may restrict transfer or change behavior. A listed balance may also depend on another contract, network, or provider.

Users should verify the network, contract address, issuer, token behavior, decimals, transfer restrictions, and relevant rights before interacting. Unknown assets should not be approved, traded, or sent merely because they appear in a wallet. Organizations need asset eligibility rules, valuation sources, ownership records, and reconciliation between wallet balances and authoritative ledgers.

Wallet Asset should be distinguished from the asset balance and from the application that displays it. For example, a customer-facing success message does not prove that the intended transaction executed on the correct network; operations should verify execution and reconcile the result before irreversible fulfillment.

The Wallet Asset workflow operates through several distinct states: request creation, user or policy approval, signature generation, network submission, execution, confirmation, balance recognition, and accounting. For Wallet Asset, a wallet interface or provider response can report progress, but it cannot replace verified transaction and ledger evidence.

Material risks for Wallet Asset include credential compromise, malicious destinations, unsupported assets, wrong-network transfers, stale balances, compromised software, provider outage, privacy leakage, and inaccessible recovery material. For Wallet Asset, controls should reflect value, automation, reversibility, and whether the organization or a third party controls signing.