Ismail Khoffi

> c) validator that just uses data availability proofs Question: this was still assuming that there is no state in the LL main chain? Wouldn't validators still verify validity of...

Update on the above: while you could still argue that the LL token app will be treated as an ORU chain in the sense that clients could accept state transition...

I'm very much in favour of this. Also, see: - https://github.com/cosmos/cosmos-sdk/discussions/8328 - https://github.com/cosmos/cosmos-sdk/issues/8455

See also: https://github.com/osmosis-labs/osmosis/blob/0509525b6cafb0c1c5b41c06c6e1dd13c8e7a98b/x/epochs/spec/README.md#L11-L10 (already deployed in production / used in https://app.osmosis.zone/pools

I think Request is very common in the PBFT/Consensus focused literature. See, e.g., http://pmg.csail.mit.edu/papers/osdi99.pdf I think in blockchain-land, the word Transaction is predominantly used for the same thing.

Additionally to defining the exact data structures of different fraud proofs / evidence types, the specification should also stipulate who (which node types) generates them under which circumstances and what...

Please rebase your commits on the current main. You can also open a new PR from a fresh branch and cherry-pick the commits from the old one if that is...

I actually like "Some Bodies". Alternatively: "Not All Bodies"?

This issue definitely requires more context. ref: - https://github.com/celestiaorg/optimint/issues/206 - https://github.com/celestiaorg/optimint/issues/207

related: - https://github.com/celestiaorg/optimint/issues/36 - https://github.com/celestiaorg/optimint/issues/87 The light client also will need to understand how leader selection works btw.