Added ashHUAHUA #4717
Added ashHUAHUA #4717
Conversation
| "base": "factory/chihuahua1hplyuj2hzxd75q8686g9vm3uzrrny9ggvt8aza2csupgdp98vg2sp0e3h0/uhuahua.ash", | ||
| "name": "Burned HUAHUA", | ||
| "display": "ashHUAHUA", | ||
| "symbol": "ashHUAHUA", |
There was a problem hiding this comment.
This symbol has lowercase letters, meaning it derives from HUAHUA in some way. How so? Please define the relationship using the traces property.
There was a problem hiding this comment.
@JeremyParish69
ashHUAHUA is minted when burning HUAHUA token. This is done by Ash DAO's furnace dapp-
https://chihuahua.burn.community/
Just like ashLAb - #4516
There was a problem hiding this comment.
Thanks. I'm still not clear exactly what the purpose is. Can it be redeemed to turn ashHUAHUA back into HUAHUA? Or is it more like a 'receipt' of having burned HUAHUA? Does it earn the user rewards or anything?
I'm trying to figure out whether both of these should be defined as a 'synthetic' version of the original asset, but that would only make sense if it's meant to follow the same price action, which I'm not sure is the case here.
There was a problem hiding this comment.
Thanks. I'm still not clear exactly what the purpose is. Can it be redeemed to turn ashHUAHUA back into HUAHUA? Or is it more like a 'receipt' of having burned HUAHUA? Does it earn the user rewards or anything?
It is a receipt token that signifies that the huahua was burned and cannot be reverted back to HUAHUA.
I'm trying to figure out whether both of these should be defined as a 'synthetic' version of the original asset, but that would only make sense if it's meant to follow the same price action, which I'm not sure is the case here.
They are not meant to relate to each other on a price level. Happy to update the trace property but would love an example to model this one's after if you know of any applicable cases.
There was a problem hiding this comment.
For now I can't think of an appropriate example, so I'm not sure the current usage of traces will work with this. For now I think we can proceed without it.
No description provided.