DASID vs DTI: Digital Asset Identifiers Compared

DTI (Digital Token Identifier, ISO 24165) is an international standard that assigns a machine-readable code to digital tokens, distributed ledgers, and their functionally fungible groupings. DASID (Digital Asset System Identification) is a separate, open, human-readable identifier standard, published in 2026 and maintained by Allium, that encodes an asset's type, ticker, classification, and per-chain deployment into one structured string. Both aim to give onchain assets a durable identity, but DTI leans on ISO governance and opaque codes while DASID is designed to be read and reasoned about by people and systems that work with cross-chain reference data.

If you have ever tried to reconcile the "same" token across Ethereum, Solana, and a Layer 2, you already understand the problem both standards attack. A contract address tells you where a token lives on one chain, but it says nothing about what the asset is or how it relates to the same asset elsewhere. Identifiers exist to fix that gap. For the full landscape, start with our definitive guide to digital asset identifiers.

Key takeaways

• DTI (ISO 24165) is a formal international standard that identifies digital tokens and ledgers with a code assigned by a central registration authority.
• DASID is an open, human-readable identifier standard published in 2026 that encodes asset type, ticker, classification, mechanism, and a per-chain deployment suffix in a single string.
• The core difference is legibility and structure: DTI codes are opaque and require a lookup, while a DASID string carries meaning on its face and maps each chain deployment back to one canonical asset.
• DTI is production-grade and referenced in regulatory contexts today. DASID is new, with a v0.1 spec published and a reference registry still in progress.
• Allium issues and maintains the DASID standard. The two identifiers are complementary rather than mutually exclusive.

Why this matters now

Tokenized money and tokenized securities have moved from experiment to infrastructure. Stablecoins settle real payment volume, and asset managers have launched tokenized Treasury products that trade across multiple chains. When a bank, auditor, or regulator wants to track exposure to a single asset, they hit a wall: the asset has one economic identity but many onchain addresses.

Traditional reference-data plumbing was built for securities that exist in one place. CUSIP and ISIN identify an instrument, but neither has a concept of a per-chain deployment. That gap is exactly why ISO created DTI and why newer, onchain-native schemes like DASID have emerged. Institutions bringing capital onchain need a common key before they can reconcile positions, price risk, or file reports. Understanding what these identifiers do, and where each stops, is now part of the operational cost of doing business in onchain finance.

How DTI works

DTI is defined by ISO 24165 and administered by a designated Registration Authority. It follows a familiar model from traditional finance:

• Request or lookup: a token, distributed ledger, or functionally fungible token group is registered with the authority.
• Assignment: the record receives a unique, permanent alphanumeric identifier.
• Attributes: the code itself is opaque, so descriptive metadata (token name, ledger, technical type) is stored in the registry record rather than in the string.
• Resolution: to learn what a DTI represents, you query the registry, much as you would resolve an ISIN to its underlying security.

The strength of this model is governance. DTI carries the weight of ISO standardization, which matters when identifiers need to appear in regulatory reporting and cross-border data exchange.

How DASID works

DASID takes a different design stance. Instead of an opaque code plus a registry lookup, it packs structured meaning into the identifier itself. A DASID is a fixed, hyphen-delimited string of six segments:

• Entity Type (3 chars): NET, TKN, PRT, or ISR (network, token, protocol, issuer).
• Ticker (3-5 chars): the asset's symbol.
• Sequence (3 digits): handles collisions between assets that share a ticker.
• Primary Class (2-4 chars): a hierarchical classification of the asset.
• Mechanism (2 chars): a sub-type describing how the asset works.
• Check Digit (1 digit): a Luhn-derived integrity check.

Multi-chain deployments add a colon-delimited suffix, so a stablecoin deployed on Ethereum reads as something like TKN-USDC-001-ST-RB-3:ETH. That suffix is the key idea: DASID resolves the layer beneath the asset, mapping each per-chain deployment to one canonical identity. You can read the type, ticker, class, and chain without a lookup. Full details live in the DASID standard.

DASID vs DTI: the core differences

Both identifiers give an asset a stable name, and both are useful. The distinction is in design philosophy and what each optimizes for.

Legibility. A DTI code is opaque by design; you cannot infer anything from it without querying the registry. A DASID string is meant to be read by a person or parsed by a system directly, which speeds up debugging, mapping, and reconciliation.

Per-deployment awareness. DTI can identify individual tokens and functionally fungible groups. DASID makes the per-chain deployment a first-class part of the identifier through its colon suffix, so the relationship between "the asset" and "this deployment of the asset" is explicit in the string.

Governance and maturity. DTI is an established ISO standard with a formal Registration Authority. DASID is a new open standard: v0.1 was published in May 2026, the spec is defined, a reference registry is in progress, and a resolution API is planned. Honesty about status matters here. DASID is emerging, not yet an entrenched industry default.

Where they sit alongside older identifiers

Neither DTI nor DASID exists in a vacuum. The lineage runs CUSIP (1968), ISIN (1981), LEI (2012), FIGI (2014), then the onchain-era additions. CUSIP and ISIN identify a security with no concept of a per-chain deployment, which is why they map poorly to tokens that live on several networks at once. For a focused breakdown, see our comparison of a digital asset identifier vs ISIN.

Contract addresses sit at the opposite extreme. They are precise about location on one chain but carry no asset-level meaning and no cross-chain link. If you want to understand that boundary, read digital asset identifier vs contract address. And if you are still forming the mental model, what is a digital asset identifier covers the fundamentals.

Concrete benefits, stated as before and after

Faster reconciliation: before, an operations team manually maps a token's contract address on each chain to a spreadsheet of "same asset" rows. After, a per-deployment-aware identifier links each chain deployment to one canonical key, so the mapping is a lookup rather than a research project.

Clearer risk aggregation: before, a risk desk tracking exposure to a single stablecoin has to know every address it uses. After, one identifier gathers all deployments, so total exposure is a query. This matters when you are assessing whether stablecoins are safe to hold at scale.

Auditable reporting: before, regulatory filings reference raw addresses that mean nothing to a reviewer. After, a legible identifier that a human can parse reduces back-and-forth and shortens review cycles.

Risks and open questions

DASID is new. A standard is only as useful as its adoption, and a 2026 v0.1 spec with a registry still in progress has not yet proven durability at scale. The resolution API is planned, not live, so systems that need programmatic lookups will have to wait or build around the published spec.

DTI has the opposite challenge. It is mature and governed, but its opaque codes and fungible-group model were not designed with per-chain deployment mapping as a primary concern, which is why teams working with heavily multi-chain assets often want a second, more legible layer.

There is also the question of coexistence. In practice, an institution may map assets across several identifiers at once, using DTI where ISO-aligned reporting demands it and a human-readable scheme like DASID for internal reconciliation. Whether the ecosystem consolidates on one scheme or maintains crosswalks between several is an open question. The broader shift toward asset tokenization will likely decide how much pressure builds for a single dominant key.

The infrastructure underneath

Identifiers are only useful when they sit on accountable data. Whichever scheme you use, the value comes from mapping each identifier to reliable, per-deployment ground truth across chains. That is the reference-data problem researchers keep running into, from Yale's work on MEV redistribution to studies of onchain perpetual futures and on-ledger data research. A standard identifier is the label; the standardized data behind it is what makes the label trustworthy. If you are new to the token side of this, what is a stablecoin is a useful primer on the assets these identifiers most often describe.

Frequently asked questions

What is the difference between DASID and DTI?

DTI (ISO 24165) is an international standard that assigns an opaque code to digital tokens and ledgers, resolved through a central registry. DASID is an open, human-readable identifier standard that encodes asset type, ticker, classification, mechanism, and a per-chain deployment suffix directly in the string. DTI optimizes for ISO governance; DASID optimizes for legibility and explicit per-deployment mapping.

Is DASID an official ISO standard like DTI?

No. DTI is defined by ISO 24165 with a designated Registration Authority. DASID is a separate open standard published in 2026 and maintained by Allium. It is not an ISO standard, and as of its v0.1 release the reference registry is still in progress.

Can DASID and DTI be used together?

Yes. They are complementary. An institution can use DTI where ISO-aligned reporting requires it and a human-readable scheme like DASID for internal reconciliation and cross-chain mapping, maintaining crosswalks between the two.

Why do tokens need a special identifier at all?

A token can be deployed across many chains, each with its own contract address, while representing one economic asset. Contract addresses do not link these deployments together, and older securities identifiers like ISIN and CUSIP have no concept of a per-chain deployment. Identifiers like DTI and DASID exist to give the asset one durable, cross-chain identity.

What does a DASID look like?

A DASID is a fixed six-segment string: entity type, ticker, a three-digit sequence, primary class, a two-character mechanism, and a Luhn check digit. Multi-chain deployments add a colon-delimited chain suffix, for example TKN-USDC-001-ST-RB-3:ETH.

Is DASID ready to use in production today?

The DASID specification is published (v0.1, May 2026) and defines the format in full. A reference registry is in progress and a resolution API is planned, so programmatic lookups are not yet live. Teams can build against the published spec while those components mature.