-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metadata serialization issue #20
Comments
Did you find an answer ?? am interested by that |
I tried your way and for bonk for example i'd get :
If anyone could indicate me what am doing wrong would be lovely |
Do you have issues with getting the metadata by itself or with But if it is the same issue as mine (which should be, because you are replying in this github issue) for now I'm manually replacing |
Thanks it helped. |
I'm using the
token-metadata
client to fetch metadata from tokens. The strings decoded from the data returned by the chain contain additional0x00
bytes; I don't know if it should.Example:
The result of
metadata.Data.Name
(or other data, like symbol), for example, will always have a length of 32:Results into:
Token name from metadata (32): Ansem's World
If I print the value with a string interpreter to show 0x00 bytes, it shows as:
What do you think is the best way to deal with it? Is this the default behavior for the
NewBorshDecoder
?The text was updated successfully, but these errors were encountered: