Support both osmosis and CW tokenfactory msg standards #788
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This adds support for the
/cosmwasm.tokenfactory
msg type URLs tocw-tokenfactory-issuer
, now supporting both/cosmwasm.
and/osmosis.
. The feature flagosmosis_tokenfactory
orcosmwasm_tokenfactory
control which version of the contract gets built.It also removes dependency on the
token_bindings
package which usesCosmosMsg::Custom(TokenFactoryMsg)
because we now use stargate (CosmosMsg::Stargate
) messages instead, which are supported on all chains since msgs are protobuf encoded. This is critical to supporting both token thecosmwasm.
andosmosis.
tokenfactory standards.