Cardano Native Asset Fingerprint vs Policy ID vs Asset Name: What's the Difference?
When working with native assets on Cardano, you will encounter three distinct identifiers: the fingerprint, the policy ID, and the asset name. Each serves a different purpose in identifying and tracking tokens. The fingerprint is a human-readable checksum, the policy ID identifies the minting policy, and the asset name is a label assigned by the issuer. None of these identifiers alone is sufficient to uniquely identify an asset in all contexts.
What is a policy ID?
A policy ID is a 28-byte hash (56 hexadecimal characters) derived from the minting policy script that governs how a native asset can be minted or burned. This script defines the rules - for example, whether only the issuer can mint more tokens, or whether a time lock prevents further minting after a certain date. Every native asset on Cardano is created under exactly one policy ID. Two different policies produce two different policy IDs, even if the asset names are identical.
The policy ID is the first part of an asset's on-chain identifier. In tools like Blockfrost or Koios, you will see the asset ID formatted as <policy_id>.<asset_name_hex>. The policy ID is required for any transaction that references the asset.
What is an asset name?
The asset name is a label chosen by the person or entity that mints the token. It is encoded as a hexadecimal string on-chain, but wallets and explorers typically display it in UTF-8 text (for example, MYTOKEN). The asset name can be up to 32 bytes long. It is not globally unique - many different policies can issue tokens with the same name.
Because the asset name alone cannot distinguish one token from another, it must be combined with the policy ID to form the full asset identifier. For example, two different NFT projects might both use the asset name NFT1, but they will have different policy IDs, and therefore different asset identifiers.
What is a fingerprint?
The fingerprint is a 40-character string that begins with asset1 and is derived from a hash of the concatenated policy ID and asset name. It is a human-readable checksum designed to be easier to copy, compare, and share than the full policy ID or the hexadecimal asset identifier.
Fingerprints are used in wallets and explorers as a compact reference. For example, when you see asset1abcdef1234567890abcdef1234567890abcdef in a wallet interface, that is the fingerprint. It is not stored on-chain - it is computed off-chain from the policy ID and asset name. A fingerprint is unique to a specific combination of policy ID and asset name, so it can reliably identify one particular token type.
How They Relate
The three identifiers form a hierarchy:
- Full asset identifier:
<policy_id>.<asset_name_hex>- the complete on-chain token identifier. - Fingerprint:
asset1...- a shorter, checksummed version of the full identifier. - Policy ID: identifies the minting policy (the rules).
- Asset name: the label within that policy.
To uniquely identify a native asset, you need either the full asset identifier or the fingerprint. The policy ID alone is not enough (multiple assets can share the same policy), and the asset name alone is not enough (multiple policies can use the same name).
Practical Usage
- In APIs: Both Blockfrost and Koios accept fingerprints to look up asset details. You can also query by policy ID to get a list of all assets minted under that policy.
- In wallets: When sending tokens, wallets usually let you paste either the fingerprint or the full asset identifier. The wallet converts the fingerprint to the full identifier internally.
- For verification: If you want to check whether two references point to the same token, compare fingerprints (they are easier to match by eye) or compare the full asset identifiers programmatically.
Common Confusions
- Fingerprint is not a policy ID: Some new users assume the
asset1...format is a policy ID. It is not; it is derived from both the policy ID and the asset name. - Asset names are not case-sensitive on-chain: The hex encoding preserves the exact bytes, but many wallets display asset names in uppercase or lowercase depending on how they decode the bytes. Always use the hex representation when comparing asset names programmatically.
- Two tokens can have the same fingerprint: No - by construction, each fingerprint is unique to one policy ID and asset name combination. However, the same fingerprint can refer to different units of the same token (e.g., 100 tokens of the same asset all share the same fingerprint).
When to use each
| Identifier | Best used for |
|---|---|
| Policy ID | Querying all assets from the same minting policy; identifying the minting rules |
| Asset name | Displaying a human-readable label; combining with policy ID for full identification |
| Fingerprint | Quick reference in user interfaces; error-checking when copying asset identifiers |
| Full asset identifier | On-chain transactions; API calls that require the exact token reference |
In practice, you will most often use the fingerprint when sharing a token reference with another person, and the full asset identifier when building transactions or querying chain data. The policy ID is useful for understanding the token's minting rules and for discovering related assets.
Not financial advice. joelube.xyz publishes market data and general information about digital assets. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.