-
Notifications
You must be signed in to change notification settings - Fork 2
Description
We had our token metadata in the SIP-010 format as follows:
{
"title": "Asset Metadata",
"type": "object",
"properties": {
"name": {
"type": "string",
"description": "Identifies the asset to which this token represents"
},
"description": {
"type": "string",
"description": "Describes the asset to which this token represents"
},
"image": {
"type": "string",
"description": "A URI pointing to a resource with mime type image/* representing the asset to which this token represents. Consider making any images at a width between 320 and 1080 pixels and aspect ratio between 1.91:1 and 4:5 inclusive."
}
}
}
We then updated it to check if we just had the wrong JSON schema, and followed the wrapped USD token information and schema:
stsw json: https://app.stackswap.org/token/stsw.json
{
“name”: “StackSwap”,
“symbol”: “STSW”,
“description”: “StackSwap Project”,
“image”: “https://app.stackswap.org/icon/stsw.svg”
}
xusd json link : https://wrapped.com/xusd.json
{
“name”: “Wrapped USD”,
“symbol”: “xUSD”,
“description”: “Wrapped USD on Stacks (xUSD) is a 1:1 equivalent of stable-backed USD on the Stacks network.“,
“image”: “https://wrapped.com/images/xusd.png”
}
xusd hiro link : https://api.hiro.so/metadata/v1/ft/SP2TZK01NKDC89J6TA56SA47SDF7RTHYEQ79AAB9A.Wrapped-USD
{“name”:“Wrapped USD”,“symbol”:“xUSD”,“decimals”:8,“total_supply”:“31881338771272”,“token_uri”:“https://wrapped.com/xusd.json”,“description”:“Wrapped USD on Stacks (xUSD) is a 1:1 equivalent of stable-backed USD on the Stacks network.“,”image_uri”:“https://wrapped.com/images/xusd.png”,“image_canonical_uri”:“https://wrapped.com/images/xusd.png”,“tx_id”:“0xfe7848716ba423dfaf664a975771f75763720b0be8a0759a56b2d80a45692ca7”,“sender_address”:“SP2TZK01NKDC89J6TA56SA47SDF7RTHYEQ79AAB9A”,“metadata”:{“sip”:16,“name”:“Wrapped USD”,“description”:“Wrapped USD on Stacks (xUSD) is a 1:1 equivalent of stable-backed USD on the Stacks network.“,”image”:“https://wrapped.com/images/xusd.png”,“cached_image”:“https://wrapped.com/images/xusd.png”}}
We ran the contract call to update the metadata as follows:
However, we are still left with the same information on the Hiro side:
stsw hiro: https://api.hiro.so/metadata/v1/ft/SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275.stsw-token-v4a
{“name”:“STACKSWAP”,“symbol”:“STSW”,“decimals”:6,“total_supply”:“1000000000000000”,“token_uri”:“https://app.stackswap.org/token/stsw.json”,“tx_id”:“0x3edffbd025ca2c29cfde8c583c0e0babacd4aa21075d10307d37c64ae78d579e”,“sender_address”:“SP1Z92MPDQEWZXW36VX71Q25HKF5K2EPCJ304F275”}
Is there anything we are missing on how to carry this out correctly? We have also previously included both json scheme in the SIP-010 versions and the SIP-019 example in the documentation to cover all bases, but so far this hasn't worked. This is also important for us on the end of helping users quickly and easily create their tokens on the Stackswap Token Launchpad, so we have a few users, entrepreneurs, and project leaders keeping up with this issue so they may see their tokens show up correctly on the Hiro Wallet extension.
Thank you for your work on SIP-019 @rafaelcr ! Hope we can find a solution here.