You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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"
}
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)
The text was updated successfully, but these errors were encountered: