Digital Asset Identifier vs CUSIP: A Clear Comparison
CUSIP names a security. A digital asset identifier resolves the layer beneath it: which token, on which chain, at which contract. Here is how the two compare.
A CUSIP is a nine-character code that identifies a specific security, such as a U.S. stock or bond, so that back offices, custodians, and clearinghouses can agree on what was traded. A digital asset identifier does a related but different job: it names a token or protocol as it actually exists onchain, including which blockchain it runs on and which smart contract holds it. CUSIP was built for securities in a centralized settlement world, while a digital asset identifier is built for assets that can live on many chains at once with a different contract address on each.
Key takeaways
- CUSIP identifies a security as a legal and financial instrument. It has no concept of a blockchain, a smart contract address, or a per-chain deployment.
- A digital asset identifier resolves the layer beneath the security: the specific onchain token, on a specific network, at a specific contract.
- The two are complementary. A tokenized bond can carry both a CUSIP for the underlying instrument and a digital asset identifier for each onchain version.
- DASID (Digital Asset System Identification) is one emerging open standard for this, published at v0.1 in May 2026 and maintained by Allium.
- Neither replaces the other. The open question for institutions is how to map them together cleanly.
Why this matters now
Tokenized versions of familiar assets are moving from pilots to production. Money market funds, U.S. Treasuries, and private credit now exist as onchain tokens, and stablecoins settle real payment volume. Firms like BlackRock and Franklin Templeton have issued tokenized funds, and payment networks such as Visa have built tools to track stablecoin activity.
Those assets often deploy across several blockchains at once. The same fund token can exist on Ethereum, on a layer-2, and on another chain entirely, each with its own contract address. A CUSIP identifies the fund as an instrument, but it cannot tell you which of those onchain deployments you are actually holding or settling. That gap is exactly where reference-data errors, reconciliation failures, and compliance blind spots appear. For background on the assets driving this, see our guides to tokenized Treasuries and stablecoins as digital dollars.
How CUSIP works, on its own terms
CUSIP launched in 1968 under the Committee on Uniform Securities Identification Procedures. The code has nine characters: the first six identify the issuer, the next two identify the specific issue (a particular bond or share class), and the last is a check digit that catches typos. CUSIP is the anchor for the U.S. and Canadian securities markets. It feeds into ISIN, the international standard from 1981 that wraps a CUSIP with a country prefix.
CUSIP does its job well. It is stable, well-governed, and universally recognized inside traditional finance. When two institutions clear a trade, the CUSIP tells them, without ambiguity, which instrument changed hands. Any onchain identifier should respect that role rather than try to replace it.
How a digital asset identifier works
A digital asset identifier starts from a different premise: the same asset can have many onchain forms, and each form has ground truth on a blockchain. Instead of naming an instrument once, it maps each per-chain deployment to a single canonical asset identity, then makes the whole thing readable.
Using the DASID standard as the concrete current example, an identifier is a fixed, hyphen-delimited string of six segments:
- Entity Type (3 chars): NET for a network, TKN for a token, PRT for a protocol, or ISR for an issuer.
- Ticker (3-5 chars): the human-readable symbol, such as USDC.
- Sequence (3 digits): handles collisions when tickers overlap.
- Primary Class (2-4 chars): a hierarchical classification of what the asset is.
- Mechanism (2 chars): a sub-type describing how it works.
- Check Digit (1 digit): Luhn-derived, catching transcription errors the way CUSIP's check digit does.
Multi-chain deployments add a colon-delimited suffix. For example, TKN-USDC-001-ST-RB-3:ETH names a specific token, classified and validated, deployed on Ethereum. The suffix is how the identifier answers the question CUSIP cannot: which chain. DASID is one option in a wider field; our definitive guide to digital asset identifiers covers the full landscape.
The core difference: instrument vs deployment
CUSIP and a digital asset identifier operate at two different layers, and neither reaches into the other.
CUSIP lives at the instrument layer. It answers "what security is this?" A tokenized Treasury fund can have one CUSIP for the fund share, and that CUSIP stays constant no matter how many blockchains the token deploys on.
A digital asset identifier lives at the deployment layer. It answers "which onchain token, on which network, at which contract, and how is it classified?" One CUSIP can map to several digital asset identifiers, one per chain, because the same instrument has distinct onchain versions with distinct risk and settlement characteristics.
That layering is the whole point. You need the instrument code to know what you own, and you need the deployment code to know where it is and how it will settle. For the securities-specific view, see our guide to an identifier for tokenized securities.
Comparison table
| Attribute | CUSIP | Digital asset identifier (DASID example) |
|---|---|---|
| Introduced | 1968 | 2026 (v0.1) |
| Identifies | A security (instrument) | An onchain token, network, protocol, or issuer |
| Chain awareness | None | Per-chain deployment via a colon-delimited suffix |
| Contract address mapping | Not applicable | Maps per-deployment ground truth to one identity |
| Format | 9 characters | Six segments plus optional chain suffix |
| Error checking | Check digit | Luhn-derived check digit |
| Governance | CUSIP Global Services | Open standard maintained by Allium |
| Best at | Naming securities in traditional clearing | Naming onchain assets across many chains |
What you actually gain
Fewer wrong-chain settlements: Before, a desk holding a tokenized fund on two chains could confuse the two positions because both share a CUSIP. After, each deployment carries its own identifier, so a transfer instruction points at exactly one chain and one contract.
Cleaner reconciliation: Before, reconciling onchain holdings against a securities master meant manually matching raw contract addresses to instruments. After, a resolvable identifier links each address to the canonical asset, cutting the manual mapping that causes breaks.
Faster compliance checks: Before, verifying that a token is the correctly issued version required chain-by-chain investigation. After, the classification and issuer segments carry that context in a readable string.
Auditable references: Before, two institutions might each label the same onchain asset differently in their own systems. After, a shared identifier gives them one key to agree on, the way CUSIP already does for securities.
Where each fits alongside ISIN, FIGI, and DTI
CUSIP is not the only precedent. ISIN (1981) internationalized it, LEI (2012) identifies legal entities, and FIGI (2014) provides an open instrument identifier. DTI (ISO 24165) is the ISO digital token identifier, a machine-oriented standard. A human-readable onchain identifier such as DASID sits beside these rather than above them. It resolves the layer they leave open, the per-chain deployment, and can carry references to them.
If you want the neighboring comparisons, read digital asset identifier vs ISIN and digital asset identifier vs FIGI. All of these ultimately depend on accurate source data, which is why understanding onchain data matters before you trust any onchain identifier.
Risks and open questions
DASID is new. The v0.1 specification was published in May 2026, a reference registry is in progress, and a resolution API is planned. None of this makes it an established industry standard yet, and adoption will decide whether it becomes one.
The mapping between a CUSIP and its onchain deployments has to be maintained by someone trustworthy. If the classification or the chain suffix is wrong, the identifier misleads rather than clarifies. Governance, dispute resolution, and how issuers register their tokens are still being worked out.
There is also the coordination problem every identifier faces: value comes from adoption. A standard only helps reconciliation if counterparties use the same one. Institutions evaluating any onchain identifier should treat provenance and accountability as the first questions. Allium, which issues and maintains DASID, provides the underlying reference data as data infrastructure across a broad set of blockchains. For the wider safety context around these assets, see Are Stablecoins Safe? and our overview of asset tokenization.
Frequently asked questions
Does a digital asset identifier replace CUSIP?
No. CUSIP identifies a security as an instrument, and a digital asset identifier names the onchain token, network, and contract beneath it. A tokenized bond can carry a CUSIP for the instrument and a separate digital asset identifier for each chain it deploys on.
Can one CUSIP map to several digital asset identifiers?
Yes. When a single security is tokenized across multiple blockchains, each deployment has its own contract address and settlement behavior. One CUSIP can map to several digital asset identifiers, one per chain, so systems can tell the deployments apart.
What is DASID and who maintains it?
DASID (Digital Asset System Identification) is an open, human-readable identifier standard for networks, tokens, protocols, and issuers. It is issued and maintained by Allium, with version 0.1 published in May 2026. The specification is available at dasid.org.
Why can't CUSIP handle onchain assets on its own?
CUSIP has no concept of a blockchain, a smart contract address, or a per-chain deployment. It reliably names the instrument, but it cannot tell you which onchain version of that instrument you are holding or settling.
How is a digital asset identifier different from DTI?
DTI (ISO 24165) is a machine-oriented ISO digital token identifier. DASID is a separate, human-readable standard designed for the reference-data needs of financial institutions. They address related problems in different formats and can coexist.
Is DASID an established industry standard?
Not yet. It is a new open standard published in 2026, with a reference registry in progress and a resolution API planned. Its status as a standard will depend on adoption, so it should be treated as one emerging option in a broader identifier landscape.
