-
Notifications
You must be signed in to change notification settings - Fork 829
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
[FEATURE] Metadata feature for tokenfactory module #932
Comments
Any update on this? Hoping it will be part of mainnet. |
@BrandonWeng okay thanks! when should I expect this update to be reflected here - https://github.com/sei-protocol/sei-cosmwasm? |
We'll either get it this weekend or early next week! |
@BrandonWeng sweet, looking forward to it! |
@hoomp3 apologies for the delay, we're working on the CosmWasm hook and the CLI interface this week. You can use the RPC/GRPC to interface with the metadata on the chain level. |
@BrandonWeng No worries, thanks for letting me know. |
@hoomp3 it should've just been deployed to atlantic-2 during today's upgrade :) |
Problem
There is no way to set any metadata for tokens created using the token factory module with the method found here - https://github.com/sei-protocol/sei-cosmwasm/tree/main/packages/sei-cosmwasm#tokenfactory. The CreateDenom message in sei_cosmwasm only takes a subdenom as an argument.
As a result, querying for the metadata or token info of a custom native token created by the token factory module returns the following:
Solution
Users should be able to specify desired metadata when creating native tokens using the token factory. Users should also be able to specify the intended token decimals in addition to the other token metadata (ex: The smallest token amount of ATOM is 10e-6 so this would be 6. The smallest ETH is 10e-18 so this would be 18). This improves the UX of integrating with native tokens since users will be able to rely on getting the metadata from the chain and allows for different custom native tokens to have different token precision.
The text was updated successfully, but these errors were encountered: