Open Standard v0.1 Published May 2026

The Digital Asset
System Identifier

DASID is an open identifier standard for digital assets — networks, tokens, protocols, and issuers. It provides structured, human-readable identifiers for the onchain finance ecosystem, designed to meet the reference data requirements of financial institutions. It follows the lineage of CUSIP, ISIN, and LEI: every era of market infrastructure sets its identifier standard first.

View Specification See Examples →

Example Identifier

NET-ETH-001-L1-CS-4

NET Entity type — Network

ETH Canonical ticker

001 Sequence — collision handling

L1 Primary class — Layer 1

CS Mechanism — Consensus

4 Check digit (Luhn-style)

§1 — Specification

Identifier Structure

A DASID identifier is a fixed-structure, hyphen-delimited string composed of six segments. Each segment carries a distinct layer of classification, from entity type at the broadest level to a check digit for validation.

Segment 1 — Entity Type

NET · TKN · PRT · ISR

3 characters. Establishes the top-level classification. Required for all identifiers.

Segment 2 — Ticker

3–5 characters

The entity's canonical ticker symbol. Used with the sequence number to form a unique key.

Segment 3 — Sequence

3 digits (001–999)

Handles collision when a ticker maps to multiple distinct entities. Uniswap V3 and V4 share a ticker but carry different sequences.

Segment 4 — Primary Class

2–4 characters

Hierarchical classification assigned per entity type. L1/L2 for networks; ST/RWA for tokens; DEX/LND for protocols.

Segment 5 — Mechanism

2 characters

Distinguishes sub-types within a class — e.g., separating Hyperliquid's Layer 1 consensus metrics from its perpetuals open interest.

Segment 6 — Check Digit

1 digit

Luhn algorithm-derived validation digit, inspired by CUSIP. Enables error detection in system integrations.

Network Deployment Suffix

A token's core DASID identifier is chain-agnostic. Per-network deployments are expressed as a colon-delimited suffix appended to the base identifier, preserving the canonical identity of the asset across all chains where it is issued or bridged.

Table 1.1 — Multi-Chain Deployment Notation

Identifier	Chain	Description
TKN-USDC-001-ST-RB-3:ETH	Ethereum	Circle-issued USDC on Ethereum mainnet — canonical deployment.
TKN-USDC-001-ST-RB-3:ARB	Arbitrum	USDC on Arbitrum — same base identifier, network-suffixed.
TKN-USDC-001-ST-RB-3:SOL	Solana	USDC on Solana — issued directly by Circle, canonical deployment.
TKN-USDC-001-ST-RB-3:BASE	Base	USDC on Base — canonical deployment on Coinbase's L2.

§2 — Entity Types

Four First-Class Entities

Every DASID identifier begins with one of four entity type prefixes. The entity type is the primary classification root — a network and a token sharing the same ticker are unambiguously different entities and will never share an identifier.

NET

Network

Layer 1, Layer 2, Layer 3, and data availability networks. Ethereum, Solana, Arbitrum, Celestia.

TKN

Token

Native gas tokens, stablecoins, real-world assets, governance tokens, and LP positions.

PRT

Protocol

Onchain financial protocols: DEXs, lending markets, perpetuals, bridges, and staking.

ISR

Issuer

Asset issuers and real-world counterparties: Circle, Tether, BlackRock, Ondo, Paxos.

Primary Class Codes

Class codes are hierarchical and assigned per entity type. A network's class code describes its architecture; a token's class code describes its economic function.

Table 2.1 — Network Class Codes

Code	Class	Definition
L1	Layer 1	Base-layer settlement network with its own consensus mechanism. Examples: Ethereum, Solana, Bitcoin, Avalanche C-Chain.
L2	Layer 2	Execution layer that settles finality to an L1. Examples: Arbitrum One, Optimism, Base, zkSync Era.
L3	Layer 3	Application-specific chain that settles to an L2. Examples: Xai, Degen Chain.
DA	Data Availability	Networks specialized for data availability and blob storage. Examples: Celestia, EigenDA, Avail.

Table 2.2 — Token Class Codes

Code	Class	Definition
NG	Native Gas	The native asset of a network, used to pay transaction fees and participate in consensus. Examples: ETH, SOL, BNB, AVAX.
ST	Stablecoin	Tokens designed to maintain parity with a reference value, typically USD. Examples: USDC, USDT, USDe, DAI, PYUSD.
RWA	Real-World Asset	Tokens representing off-chain assets: treasuries, equities, commodities, and credit instruments. Examples: BUIDL, PAXG, ONDO.
GOV	Governance	Tokens conferring voting rights over a protocol, DAO, or onchain organization.
LP	Liquidity Position	Tokens representing a share of a liquidity pool, vault, or yield-bearing position.

Table 2.3 — Protocol Class Codes

Code	Class	Definition
DEX	Decentralized Exchange	Onchain spot trading protocol. Examples: Uniswap, Curve, Orca, Aerodrome.
LND	Lending	Onchain lending and borrowing protocol. Examples: Aave, Compound, Morpho, Kamino.
PERP	Perpetuals	Protocol offering perpetual futures or leveraged derivatives. Examples: Hyperliquid, GMX, dYdX, Drift.
BRG	Bridge	Cross-chain asset transfer protocol. Examples: Across, LayerZero, Wormhole, Stargate.
STK	Staking / Restaking	Liquid staking or restaking protocol. Examples: Lido, EigenLayer, Jito, Rocket Pool.

§3 — Registry Examples

Identifiers in Practice

DASID handles the full complexity of the onchain asset universe — assets deployed across multiple chains, protocols with multiple entity types, and the distinction between canonical issuance and bridged variants.

Ethereum Network

NET-ETH-001-L1-CS-4

Layer 1, proof-of-stake consensus. Sequence 001 — no ticker collision at this entity type.

ETH Token

TKN-ETH-001-NG-CS-7

Native gas token of Ethereum. Entity type prefix resolves ticker collision with NET-ETH.

USDC — Multi-Chain

TKN-USDC-001-ST-RB-3

Circle-issued regulated stablecoin, fiat reserve-backed. Per-network deployment via suffix.

:ETH:ARB:SOL:BASE

USDe — Ethena

TKN-USDE-001-ST-SD-8

Synthetic dollar, delta-neutral strategy-backed. Mechanism code SD distinguishes from fiat-backed stablecoins.

BUIDL — BlackRock

TKN-BUIDL-001-RW-FI-2

Tokenized money market fund, US Treasury exposure. RWA class, fund instrument mechanism.

PAXG — Paxos

TKN-PAXG-001-RW-CM-5

Tokenized gold, physically backed. RWA class, commodity mechanism.

Uniswap V3 vs V4

PRT-UNIV3-001-DEX-AM-6

PRT-UNIV4-001-DEX-AM-1

Protocol versions carry separate identifiers. Version is encoded in the ticker, not the sequence.

Hyperliquid — Dual Entity

NET-HYPER-001-L1-CS-9

PRT-HYPER-002-PERP-OB-3

The same ticker maps to two distinct entities. Sequence 001 is the L1 network; sequence 002 is the perpetuals protocol.

§4 — Design Rationale

How the Standard is Built

The DASID scheme is designed to be readable by humans, parseable by machines, and stable across protocol upgrades, network forks, and multi-chain asset deployments.

§4.1

Entity-First Hierarchy

The entity type prefix is the root of every identifier. A network and a token sharing the same ticker are unambiguously different entities — never conflated by a shared identifier string.

§4.2

Collision-Safe Sequencing

Three-digit sequence numbers handle tickers that map to multiple entities within the same entity type. This gives every entity a permanent, stable identifier even as the asset universe expands.

§4.3

Chain-Agnostic Core

A token's DASID is defined independently of any chain. Per-network deployments use a colon-delimited suffix, keeping the canonical identity stable while tracking every chain instance.

§4.4

Issuer-Perspective Canonicality

Canonical vs. variant is defined from the issuer's perspective. Circle's USDC is the canonical issuance. A bridge-wrapped USDC is a variant — regardless of its trading volume or market share.

§4.5

Mechanism-Aware Classification

Mechanism codes let a single entity carry different analytical planes. Hyperliquid's L1 staking metrics and its perpetuals open interest are kept separate — the mechanism code prevents measurement mixing.

§4.6

TradFi-Legible Structure

The format is modeled on CUSIP and ISIN — fixed-width, hyphen-delimited segments with a check digit. Institutional systems can ingest and validate DASID identifiers without bespoke parsing logic.

§5 — Historical Precedent

Every Market Era Sets Its Identifier First

Financial markets have built the same infrastructure stack three times: on paper, on electronics, and now onchain. In each era, the identifier standard was established before adoption scaled, and the clearing, custody, and data systems that followed were built around it. DASID applies that precedent to onchain finance.

Table 5.1 — The Identifier Lineage

Standard	Introduced	Precedent
CUSIP	1968	Developed during the 1960s paper crisis, before the Depository Trust Company existed. Became mandatory on every US security and remains embedded in clearing infrastructure six decades later. The infrastructure followed the identifier.
ISIN	1981	ISO 6166 extended securities identification across borders. Later mandated for derivatives reporting across more than 100 jurisdictions, converting a convention into regulatory lock-in.
LEI	2012	The Legal Entity Identifier emerged from the global financial crisis, when regulators could not trace counterparty exposure because no universal entity identifier existed. A regulatory mandate made it universal.
FIGI	2014	The Financial Instrument Global Identifier was opened as a standard to cover instruments beyond the reach of legacy identifiers, recognizing that each new asset surface requires its own identification layer.
DASID	2026	The identifier layer for onchain assets: networks, tokens, protocols, and issuers. Defined while tokenized markets are still forming, on the same clock every prior standard kept.

§5.1

Standards Precede Adoption

CUSIP was assigned before settlement was automated. The FIX protocol was written in 1992, before electronic trading dominated. In every era the standard was set during the formative period and locked in by the time adoption was obvious. Identifier standards are established early or inherited from someone who established them early.

§5.2

The Onchain Seat Is Vacant

No universal identifier exists for onchain assets today. CUSIP and ISIN identify a security with no concept of a per-chain deployment. A token issued across eight networks has no canonical cross-chain key. Tokenized securities and stablecoins are now entering clearing and custody systems that require exactly that reference record.

§5.3

Regulation Cements Standards

ISIN became universal through derivatives reporting mandates. LEI became universal through post-crisis counterparty rules. In 2026, stablecoin legislation and accounting disclosure requirements are creating the equivalent reference data obligations for onchain assets. DASID is structured to serve them.

Two Layers, One Canonical Record

Legacy identifiers stop at the security. DASID resolves the layer beneath it: per-deployment ground truth (chain, contract, pool) mapped to one canonical asset identity through the network deployment suffix defined in §1. Institutions get the granular record and the consolidated view from the same identifier, which is the reference data requirement tokenized markets add on top of everything CUSIP already solved.

§6 — Licensing

Registry Access and Licensing

The DASID specification is open. Registry access and commercial API use are governed by a tiered licensing model, consistent with established financial data standards.

Tier 1

Open Reference

The identifier specification and reference examples are freely available. Suitable for research, academic, and non-commercial use.

Full specification access
Registry examples
Non-commercial use
Attribution required

Access Specification

Tier 2

Commercial Registry

Licensed access to the full DASID registry for use in commercial applications, data products, and financial systems.

Full registry dataset
Canonical address mappings
Commercial use rights
Registry update feed

Inquire About Licensing

Tier 3

API + Enterprise

Programmatic registry access via the Allium Market Data API. For custody systems, reference data infrastructure, and institutional data providers.

Real-time resolution API
Address-to-DASID lookup
Ticker normalization
SLA-backed delivery

Contact Enterprise Team

§7 — Standard Status

Development Roadmap

DASID v0.1 is under active development. The identifier scheme is defined; the reference registry and resolution tooling are in progress.

Published

Specification v0.1

The six-segment DASID structure is defined and validated against real-world assets across networks, tokens, and protocols.

In Progress

Reference Registry

Initial registry seeded with anchor assets — major networks, stablecoins, RWA instruments, and DeFi protocols.

In Progress

Taxonomy Working Group

Multiple candidate taxonomies under evaluation. Initial scope: stablecoins and tokenized real-world assets.

Planned

Resolution API

Programmatic mapping between contract addresses, exchange tickers, and DASID identifiers, integrated into the Allium Market Data API.

The Digital AssetSystem Identifier