Brainstorming "cross-chain validation" and reformation of Cosmos-SDK

I am trying to imagine the most generalized concept of cross-chain validation. Below are the generalization of cross-chain validation I’ve got so far. On the table of possible cross-chain validation combination, range of possible targets will define the direction of reformation of Cosmos-SDK for the hub or zones to apply these cases via IBC. This brainstorming is important because, we need to design “validator set projection” IBC protocol to fully comply with generalized cross-chain validation application on IBC. These are some questions we have to answer. • Do we want to allow multi-token staking feature on Cosmos-SDK? • if yes, do we want to allow a staking token not validating its own but only validating other blockchain? • Do we want to allow a token to validate more than 2 blockchains? • Do we want to allow a blockchain to be validated by more than 2 tokens? • Do we want to allow a “pegged token” to be used as a staking token? • Generalization for token ledger • Multi-denom feature basically serve this objective • Target chain’s native token minted on source chain implies that the source chain is securing the original ledger of the tokens •…

Excerpt (1196 of 3086 characters). Read the whole post on the forum ↗

@xhipster I know you had some basic ideas, mind sharing?

Fantastic work to get the conversation started. I’ll think on this and try to respond in more depth.