feat: add vTAO metadata and icons across supported chains

[camfairchild]

What

Adds metadata and icons for vTAO on the ten EVM networks supported by the official TAO.app bridge.

vTAO is an ERC-20 representation of staked TAO. The Bittensor EVM deployment is the native Virtual TAO contract; the other nine deployments are LayerZero OFTs used by the bridge.

Networks and contracts

Network	Chain ID	Contract
Bittensor EVM	964	0x31049849CCdD983D8F401077537438eaF12B12Af
Ethereum	1	0xe9f6D9898f9269B519E1435E6ebafF766c7f46BF
Base	8453	0xe9f6D9898f9269B519E1435E6ebafF766c7f46BF
Arbitrum One	42161	0xa793dcea527a481aC0a2C3a1F37EDbE586146Bce
BNB Smart Chain	56	0x58ea2Bb193B1429Cb90D24195E6ac4Ccb0B27a12
Avalanche C-Chain	43114	0x58ea2Bb193B1429Cb90D24195E6ac4Ccb0B27a12
Polygon	137	0x58ea2Bb193B1429Cb90D24195E6ac4Ccb0B27a12
Optimism	10	0x58ea2Bb193B1429Cb90D24195E6ac4Ccb0B27a12
Gnosis	100	0x58ea2Bb193B1429Cb90D24195E6ac4Ccb0B27a12
Berachain	80094	0x0D4d041d1209bFFD4a843759Ee6d19CD394EEE56

All addresses are EIP-55 checksummed. Each network receives one matching metadata/<caip19AssetId>.json and icons/<caip19AssetId>.svg pair. contract-map.json is intentionally not included, matching recent asset PRs.

Metadata verification

name(), symbol(), and decimals() were read directly from each contract through its mainnet RPC:

• Bittensor EVM: Virtual TAO, vTAO, 18 decimals
• All nine LayerZero OFTs: vTAO, vTAO, 18 decimals

Deployed bytecode was confirmed present on every listed chain. The nine OFT deployments are byte-identical to each other: eth_getCode returns the same 12,539 bytes with the same SHA-256 digest on every one, which is consistent with a single OFT implementation deployed across all nine networks.

Polygon was additionally cross-checked against three independent providers (polygon-bor-rpc.publicnode.com, polygon.drpc.org, 1rpc.io/matic), all reporting chain ID 137 and returning identical bytecode and metadata.

The official TAO.app bridge publishes and uses these network/address mappings. The native contract source and official logo artwork are maintained in the public latent-to/vtao repository.

Icon

The same official vTAO vector mark is used on all ten chains. It is based on the offsite variant from the vTAO repository, with the v badge positioned fully inside the main ring.

To follow STYLEGUIDE.md, the submitted SVGs:

• use a square artboard and full-bleed dark background;
• keep the complete mark inside the 80% safe area with 10% padding;
• remain legible in circular crops and in light/dark themes;
• contain pure vector geometry only—no embedded raster images, nested SVGs, filters, style blocks, classes, or external resources.

Checks

• node cli-update-asset.js verify --caip <asset-id> for all 10 assets — passes
• npm test — 702/702 passing
• All 10 SVGs are well-formed XML and contain no style-guide-prohibited elements
• All metadata logo paths resolve to files included in this PR
• git diff --check — passes

---

Note

Low Risk
Static metadata and icon assets only; no runtime, auth, or contract-mapping changes.

Overview
Adds vTAO (staked TAO / bridge ERC-20) to the asset catalog on ten networks aligned with the TAO.app bridge: Bittensor EVM (964), Ethereum, Base, Arbitrum, BSC, Avalanche, Polygon, Optimism, Gnosis, and Berachain.

Each chain gets a paired metadata/eip155:<chainId>/erc20:<address>.json entry (18 decimals, erc20: true, local logo path) and a matching SVG under icons/. The Bittensor native deployment uses on-chain name Virtual TAO; the nine LayerZero OFT deployments use vTAO. All chains share the same official vector mark. contract-map.json is not updated, consistent with recent asset-only PRs.

^{Reviewed by Cursor Bugbot for commit fb0bfe0. Bugbot is set up for automated code reviews on this repo. Configure here.}