-
Notifications
You must be signed in to change notification settings - Fork 607
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
[Epic] Token Factory Module #1029
Comments
We should add checks that prevent force transferring or burning from module accounts. I think maybe to be maximally safe, just deactivate force transferring altogether, and only allow burning of tokens that are in the triggering account. |
Let's go ahead and reduce the scope such that minting and burning can only happen in the triggering account. |
That way we can ship it faster |
I'm cleaning up the epics and seeing some checkboxes without issues. @sunnya97 @ValarDragon could you update the epic to cross out the completed items and create issues for items that still need work. Thank you! |
Closes / Related to: #1029 ## What is the purpose of the change Re-instate the CoswmWasm message handlers for Mint and FullDenom. Related to osmosis-labs/bindings#25 on the Rust side. ## Brief change log - Uncomment the Mint-related code. - Implemented `Mint` using `TokenFactory`. - Implemented `FullDenom` in terms of `TokenFactory`. ## Testing and Verifying Uncommented and adapted already existing tests. ## Documentation and Release Note - Does this pull request introduce a new feature or user-facing behavior changes? (yes. For the CosmWasm side) - Is a relevant changelog entry added to the `Unreleased` section in `CHANGELOG.md`? (will do) - How is the feature or change documented? (not documented)
Closing this issue to replace with issues with more details and specifics |
The token factory module is a module that will enable new native tokens to be minted on Osmosis, with well prefixed names. This is important for cosmwasm applications on osmosis to thrive.
The text was updated successfully, but these errors were encountered: