Built-in Assets

Every workspace is seeded at initialization with 32 curated tokens spanning the 15 built-in networks — each network's native gas coin plus the major stablecoins and wrapped-native tokens. They are also exposed as the frozen BUILTIN_ASSETS registry so you can inspect the catalog without opening a workspace. These ids and addresses are reserved: see Assets for how imports collide with them and why they cannot be dropped.

Each built-in token reports asset.isBuiltin === true — the flag a UI reads to show a token as non-deletable, with only its display fields (displayStatus, displayDecimals) editable. Built-ins stay current with the library: a token added to a network in a later wative-core appears automatically in existing workspaces, and a built-in's identity (symbol, name, decimals, address) always reflects the library's current values, while your display preferences on it are preserved.

Preloaded tokens by network

Token contract addresses

The 15 native coins all carry a placeholder address. The remaining 17 tokens each have a real contract address:

The BUILTIN_ASSETS registry

BUILTIN_ASSETS is a frozen record, keyed by network slug, of the curated token lists. Each entry is an array of AssetInit.

const BUILTIN_ASSETS: Record<string /* network slug */, ReadonlyArray<AssetInit>>

import { BUILTIN_ASSETS } from "wative-core";
import type { AssetInit } from "wative-core";

Object.keys(BUILTIN_ASSETS).length;            // 15 networks
BUILTIN_ASSETS["ethereum"].map((a) => a.symbol); // ["ETH", "USDC", "USDT", "WETH"]

const total = Object.values(BUILTIN_ASSETS)
  .reduce((n, list) => n + list.length, 0);     // 32 tokens

AssetInit

The literal shape of a built-in entry.

All fields are readonly. AssetInit differs from the constructor's AssetInitObject: it carries no network field (the network is the registry key), and its contractAddress is a required property (still nullable).

Native coins carry a placeholder address

Native gas coins have no contract, so the built-ins record a sentinel address rather than null. An Asset built from one reports native === true.

Built-in tokens: editable display, but not droppable

Built-in tokens cannot be removed: dropping one rejects with UNSUPPORTED_OP, because removing a native token would break balance lookups deep in the wallet flow.

const eth = ws.networks.bySlug("ethereum");
await eth.assets.drop(1); // ETH — rejects: WativeError { code: "UNSUPPORTED_OP" }

Their identity — symbol, name, decimals, contract address — is locked too: a write to one is refused with PARAMETER_ERROR. What a built-in token does allow is editing its display fields, displayStatus and displayDecimals, through network.assets.update, workspace.updateAsset, or asset.save().

An import also cannot re-use a built-in contract address — it collides with DUPLICATE_IDENTITY. See Assets for the import and collision rules.

See also