Tracking Issue for future roadmap

Open reecepbcups opened this issue 2 years ago • 0 comments

This is a long term tracking solution to put future wants / needs for long term development.

TODO

[ ] Optimistic Block Commits
[ ] Lowering unbonding time (requires IBC channel upgrades, much testing)
[ ] Babylon chain (Lower unbonding after testing with ictest. If failures, see if we can patch upstream)
[ ] mesh Security Consumer
[ ] https://github.com/CosmosContracts/juno/issues/474
[x] IBC Callbacks for ICA with contracts (IBC v7.3)
[x] WasmClient for Juno<->Polkadot IBC connection
[x] Smart contract begin / end blockers (Half done with x/clock)

Tendermint ideas for <2s blocks:

increase signing window
Only save val signing state if a block sign is missed within the signing window
If a vals state is not in a signing, then it signed. If false, we explicitly tell this. This drastically reduces space. Or just reuse the actual signatures
If the val set changes, we save all bools for every val this once to update it (like a cache) for future new val misses
Improve p2p tendermint connections
UDP vs TCP for P2P? (keep it TCP for block data / mempool, just UDP for actual connections)

Mar 20 '23 19:03 reecepbcups