Larry

> If you want to burn the tokens you would need to create a custom `MsgBurn` that burns the tokens and removes them from circulation using the function from the...

> Yes I think so @larry0x, but we have to ensure it's only executed by the authority allowed to do it, e.g. governance. Hmm what's the problem letting people burn...

I can confirm latest version works with workspace deps

Hey guys, we have the same issue, as we also uses [a radix tree](https://github.com/left-curve/grug/tree/main/crates/jellyfish-merkle) as our Merkle commitment scheme. Our non-membership proof is not compatible with ICS-2, as such we...

I would suggest renaming the current `NonExistenceProof` to `BSTNonExistenceProof` as it's intended for binary search trees, and the new variant we're adding as `RadixNonExistenceProof` to highlight it's designed for a...

I attempted to implement this today, but realized a problem: To verify JMT's exclusion proof, ICS-23 needs to know how an internal node is laid out; that is, if the...

Hi @crodriguezvega, I managed to generate ICS-23 style exclusion proof for our Merkle tree without introducing a mew proof type, taking inspiration from [SeiDB](https://github.com/sei-protocol/sei-db/blob/v0.0.43/sc/memiavl/proof.go#L41-L76)! So the problem is resolved.

Apparently [Quasar has already implemented](https://twitter.com/billyrennekamp/status/1580559972844249088) something similar: https://github.com/quasar-finance/interchain-query-demo

+1 on this, although I want to use this option to prevent precisely the "nicer" way you suggested (I dislike it).

Seems related: https://github.com/rust-lang/rustfmt/issues/3514