<p>A token is uniquely identified as <code>ploicyId</code> + <code>tokenName</code></p>
<p>the policy id is the hash of the rules imposed on minting and burning of the token.</p>
<p>the token name is the arbitrary name of the token ( there could be multiple tokens with the same rules ).</p>
<p>so it can very well happen that there are two tokens with the same name but different rules for minting/burning.</p>
<h2>A token is NOT uniquely identified by the asset fingerprint</h2>
<p>this is explained in the <a href="https://github.com/cardano-foundation/CIPs/tree/master/CIP-0014#design-choices" rel="nofollow noreferrer">CIP itself</a></p>
<p>TLDR: even if <em>extremly unlikely</em>, it is possible for two different tokens to have the same asset fingerprint. The scope of the fingerprint is to have a quick way to distinguish between tokens but the final check should always be <code>policyId</code> + <code>tokenName</code>.</p>

CC BY-SA 4.0
2023-05-29T09:05:53.173Z
2023-06-06T14:51:29.727Z
2023-06-06T14:51:29.727Z
Michele Nuzzi
<p>Yes it is technically possible. If you do this you will end up with a fungible token (FT) as opposed to a non-fungible token (NFT).</p>
<p>As the most obvious example, all the Lovelace (Ada) in your wallet have the same policy id and token name.</p>
<p>The uniqueness of a token name within a policy id is the responsibility of whoever controls the minting process.</p>

CC BY-SA 4.0
2023-05-28T11:55:10.723Z
2023-05-28T11:55:10.723Z
grim_i_am
<p>Yes, there can be more than one token with the same name, but there cannot be more than one token with the same token fingerprint. Pretty sure the fingerprint is just the bech32 encoding of <code>(name, tokenId)</code>.</p>

CC BY-SA 4.0
2023-05-26T05:23:03.967Z
2023-05-26T05:23:03.967Z
Erik de Castro Lopo
<p>I just want to clarify about this statement 'An asset is uniquely identified by an asset ID, which is a pair of both the policy ID and asset name.'</p>
<p>I'm guessing there can be duplicately named tokens where the asset name is the same, as long as the policy ID is different?</p>

<token>
Can there be duplicately named tokens?
# Can there be duplicately named tokens?

(Asked by: username_0 on 2023-05-26)

I just want to clarify about this statement 'An asset is uniquely identified by an asset ID, which is a pair of both the policy ID and asset name.'

I'm guessing there can be duplicately named tokens where the asset name is the same, as long as the policy ID is different?

**Tags:** token

---

## 3 answers

### Answer by username_1 on 2023-05-29. Score: 1 | Accepted answer

A token is uniquely identified as `ploicyId` + `tokenName`

the policy id is the hash of the rules imposed on minting and burning of the token.

the token name is the arbitrary name of the token ( there could be multiple tokens with the same rules ).

so it can very well happen that there are two tokens with the same name but different rules for minting/burning.

## A token is NOT uniquely identified by the asset fingerprint

this is explained in the [CIP itself](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0014#design-choices)

TLDR: even if *extremly unlikely*, it is possible for two different tokens to have the same asset fingerprint. The scope of the fingerprint is to have a quick way to distinguish between tokens but the final check should always be `policyId` + `tokenName`.


---

### Answer by username_2 on 2023-05-28. Score: 0

Yes it is technically possible. If you do this you will end up with a fungible token (FT) as opposed to a non-fungible token (NFT).

As the most obvious example, all the Lovelace (Ada) in your wallet have the same policy id and token name.

The uniqueness of a token name within a policy id is the responsibility of whoever controls the minting process.


---

### Answer by username_3 on 2023-05-26. Score: 0

Yes, there can be more than one token with the same name, but there cannot be more than one token with the same token fingerprint. Pretty sure the fingerprint is just the bech32 encoding of `(name, tokenId)`.


---

