Skip to content
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

Hey, #6

Open
izuyemi opened this issue Dec 8, 2022 · 0 comments
Open

Hey, #6

izuyemi opened this issue Dec 8, 2022 · 0 comments

Comments

@izuyemi
Copy link

izuyemi commented Dec 8, 2022

Hey,

Tried asking on couple of places but no luck, could you please help me, since polygon scan or etherscan are not open sourced I can not check how they work internally?

I have a erc-1155 contract that manages 2 erc-20 tokens, both with 6 decimals. I am trying to set uri, in format "https://some-url/{id}.json".
According to docs, clients should be able to replace {id} with tokenId and that should be standardized.
However, there is no impact on mumbai polyscan, decimals are not shown in transfers (for 10 with decimals 6, it is showing 10000000).
My expectations were if i specify metadata with "decimals": 6, that mumbai polyscan would recognize this, and show values properly.

My question is, are these expectations correct, or is this not possible? Or is this not possible only on mumbai polyscan?

My metadata looks like this:
{
"name": "Test token",
"decimals": 6,
"description": "Test token"
}

Thanks in advance

Originally posted by @skosito in ethereum/EIPs#1155 (comment)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant