de-husk / cosm-orc Goto Github PK

Allows people to create more complex gas estimation flows

Once it is ready, cosm-orc will be the first user of cosm-tome

Right now Im always using the first rpc and gRPC endpoint in the lists, which means Im always just selecting the same one.

Some people want to use cosm orc in a non test environment.

• Core cosm-orc API
• Config API

We have a flakey integration test in DAO DAO, because Im just sleeping waiting for a block to process.

If you dont care about gas profiling and storing the resulting code ids and contract addresses in a contract map for easier use then you really just need a really lightweight, non mutable cosmwasm client API.

Key::Mnemonic("blah blah blah") really only works for localnet.

We need a way to securely sign transactions for testnet / mainnet for non integration test use cases.

• Allow users to use their own existing os Keyring password
• Add full Keyring password CRUD support through cosm-orc
• Add ledger support
• Write documentation on proper Keyring usage for both other libraries and applications

Ideally we would pick another API endpoint from the chain registry if the one we selected randomly was down.

Switch the CI to using --all-features for all checks

Extend CosmOrc::store_contracts() to build + optimize a Cargo.toml file instead of relying on pre-built and optimized wasm files in a directory. (Or make a new method if that makes more sense)

It would be cool if you could just configure a chain-id and then cosm-orc could use the https://github.com/cosmos/chain-registry API to populate the other information for you.

Make a POC feature (or maybe a separate crate) that allows for cosmos chain orchestration in rust for testing IBC.