-
Notifications
You must be signed in to change notification settings - Fork 344
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
Terra MsgExecuteContract #902
Comments
Unfortunately no. Terra decided to make all kinds of incompatible changes to CosmWasm (especially x/wasm) interfaces that are impossible to support for us. There might be cases where things work by accident, but it would be a frustrating experience overall. Also note Terra upgraded to Cosmos SDK 0.44 which CosmJS does not yet support but will probably do soonish. |
Well, okay, one thing that could potentially work is 1. CosmJS support for SDK 0.44 and then 2. a Terra specific fork of @cosmjs/cosmwasm-stargate with all proto types generated from the Terra type definitions instead of using cosmjs-types. It would require significat talent and time but it can probably be done. |
This is my transaction data via keplr but I get this error : Log: unable to resolve type URL /cosmwasm.wasm.v1.MsgExecuteContract: tx parse error How can I fix this error? |
Closing this, for Terra we just use Terra.js |
I believe I should be able to use this library for constructing Terra compatible transactions instead of Terra.js or Anchor.js, is that correct?
If so, I need a little help creating a simple token transfer message, not too sure where things are going wrong when trying to transfer aUST tokens... Normal
UST
orLUNA
transfers work great via thewriter.sendTokens
method, I guess I'm not fully understanding the WASM interaction.The error I get back is
Unregistered type url: /cosmwasm.wasm.v1.MsgExecuteContract
, I believe this is because after poking around Terra a little I find that in their Codec file they registerwas/MsgExecuteContract
, am I on the right track?The text was updated successfully, but these errors were encountered: