<p>On the blockchain, the token name was never actually a string and was always bytes. Usually they are ASCII encoded, but they may also be UTF8, UTF-16 or even some other encoding.</p>

CC BY-SA 4.0
2022-10-16T21:33:55.420Z
2022-10-16T21:33:55.420Z
Erik de Castro Lopo
<p>I have seen recently that CIP25 was updated to include version 2. The main change in this is that the token name is now a <code>bytes</code> type whereas before it was a string.</p>
<p>My question is, what type actually is this? Is it a JavaScript Buffer, a byte array, a hex encoded string, or something else?</p>

<native-assets><token><cip>
CIP25 Metadata standard version 2 token name
# CIP25 Metadata standard version 2 token name

(Asked by: username_0 on 2022-10-15)

I have seen recently that CIP25 was updated to include version 2. The main change in this is that the token name is now a `bytes` type whereas before it was a string.

My question is, what type actually is this? Is it a JavaScript Buffer, a byte array, a hex encoded string, or something else?

**Tags:** native-assets, token, cip

---

## 1 answers

### Answer by username_1 on 2022-10-16. Score: 1

On the blockchain, the token name was never actually a string and was always bytes. Usually they are ASCII encoded, but they may also be UTF8, UTF-16 or even some other encoding.


---

