Simon Warta

Offset 21 is indeed in the middle of the string "SMWTezTlSLyKKAui": ``` $ echo 0a1c10e1bfb1ccce99c9e3151a10534d5754657a546c534c794b4b417569220f1890d5a5ec05210000000000889340 | xxd -r -p | protoc --decode_raw 1 { 2: 1569263457672126433 3: "SMWTezTlSLyKKAui" } 4...

Very nice! How do you feel about using ID+Name for better human consumption, i.e. something like `#/definitions/1-MyType`?

As far as I know, embedding Wasm as a string is the only way to be able to use the same package for browsers, bundlers and Node.js.

I think yes, but especially for timing I wonder what is the motivation for the upgrade? Is there anything we need urgently and don't have in yarn 3?

okay let's aim for this in the next breaking release. I think we can do a patch release or two without removing Node.js 16. Then we go for it

Our motivation is the other way round: we have `cosmwasm-vm` published and want to rename to `cosmwasm_vm` on order to have the same spelling on crates.io and in the imports.

Right before the release, Cosmos SDK 0.46 switched back from Tendermint 0.35 to 0.34. So at least you only need to worry about one Tendermint version for the two SDK...

2.4MB is more than what most chains can accept. A typical limit of the Wasm file is 800 KB. You can probably get the contract much smaller by using the...

The error > unable to resolve type URL /cosmwasm.wasm.v1.MsgStoreCode: tx parse error sounds like the network has no CosmWasm support. Could you ask the maintainers of the network about it?

This is expected. You need to add a multiplier to the result of simulate. 1.3 (i.e. +30%) used to be a good choice for a long time. Due to some...