-
Notifications
You must be signed in to change notification settings - Fork 33
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
Osmosis testnet was upgraded to Cosmos SDK 0.47 which is incompatible with Tendermint34Client #71
Comments
I assume this error happens because testnest is on SDK 0.47 (Tendermint 0.37) and mainnet is on 0.45 (Tendermint 0.34). In the latest version of CosmJS there is |
@webmaster128 do we need to do something in the config, or won't cosmjs detect it? Maybe the devs can temporarily manage this by using resolutions in your package and including a newer version of cosmjs if we've baked an older version in |
How do you currently create that client? |
ok — so this clearly may be the isssue @webmaster128
can you provide a small snippet of what we should change this too? I think we went a little lower level and are using the client directly cc @Zetazzz |
Hi, Hoang's almost got this PR done: We're working on getting this PR merged, hopefully we'll publish soon |
Yes, confirming that cosmology-tech/telescope#503 is the right solution |
I merged my PR. This should be okay now. |
@cosmology/[email protected] published |
Sorry guys - here was my (well, mostly the Kujira connector dev's) solution to manually instantiate Osmosis with Tendermint37Client
|
Closed with 2 solutions |
@chasevoorhees while cosmology might have published a new version(which comes with it's own challenges) that does not fix this issue in the osmojs package unless someone explicitly regenerates the lib from telescope again. @pyramation is there any active working solution using osmojs? |
we're on it! |
In the meanwhile, do you recommend using package.json resolutions to temporarily resolve all @cosmjs packages to the latest versions? |
@cosmjs/tendermint-rpc - I suddenly started getting an error after broadcastTx->decodeTx
"Error: Invalid string. Length must be a multiple of 4"
I opened an issue with cosmjs and they told me this:
It looks like we need to be able to specify whether we want to use Tendermint34Client or Tendermint37Client when calling getSigningOsmosisClient()
I'm looking into this personally to see if there's an easy fix but wanted to post this as it's a blocking issue for hummingbot's Osmosis connector
The text was updated successfully, but these errors were encountered: