Devashish Dixit

@tomtau By verified, do you mean runtime verification or compile time verification?

> Should be similar to the cronos upgrade: [crypto-org-chain/cronos#578](https://github.com/crypto-org-chain/cronos/pull/578) The main blocker right now is: [cosmos/ibc-go#1653](https://github.com/cosmos/ibc-go/pull/1653) Also, `wasmd` needs to upgrade to `cosmos-sdk v0.46`.

Strange: It shows that all the business logic is covered. But, the code that calls these keeper functions is uncovered? https://codecov.io/gh/crypto-org-chain/chain-main/src/master/x/supply/keeper/keeper.go

Here's the current logic in orchestrator to make the batches more profitable. Once a `MsgSendToEth` transaction is out of the pool and in a batch one of three things must...

@thomas-nguy So we need to maintain `next_send_batch_time` for each token type on relayer? Or create some additional logic in cosmos module to store this time? If we don't want to...

> To avoid to make the relayer stateful, how about instead of using time, using height or nonce? I don't think this makes any difference. If we store any value...

> > > To avoid to make the relayer stateful, how about instead of using time, using height or nonce? > > > > > > I don't think this...

I'm experimenting with a high level indexed db wrapper (futures based) [here](https://github.com/devashishdxt/rexie). Feedback is welcome. 😁

@tony-iqlusion Can we use [`pbjson`](https://docs.rs/pbjson-build/latest/pbjson_build/) for this?

@BurntSushi Are there any plans to merge this PR?