Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking Issue for future roadmap #611

Open
7 of 12 tasks
Reecepbcups opened this issue Mar 20, 2023 · 0 comments
Open
7 of 12 tasks

Tracking Issue for future roadmap #611

Reecepbcups opened this issue Mar 20, 2023 · 0 comments
Labels
tracking issue This is used to track a more complicated piece of work that might have multiple dependencies

Comments

@Reecepbcups
Copy link
Contributor

Reecepbcups commented Mar 20, 2023

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
  • Improve nakamoto coefficient #474
  • IBC Callbacks for ICA with contracts (IBC v7.3)
  • WasmClient for Juno<->Polkadot IBC connection
  • Smart contract begin / end blockers (Half done with x/clock)

Faster Faster block times

Migrate Core-1 Vesting

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)
@Reecepbcups Reecepbcups added the tracking issue This is used to track a more complicated piece of work that might have multiple dependencies label Mar 20, 2023
@Reecepbcups Reecepbcups changed the title Tracking Issue for future roadmap (V15,16,17) Tracking Issue for future roadmap (v16,17,18) Apr 9, 2023
@Reecepbcups Reecepbcups changed the title Tracking Issue for future roadmap (v16,17,18) Tracking Issue for future roadmap (17,18) Apr 25, 2023
@Reecepbcups Reecepbcups changed the title Tracking Issue for future roadmap (17,18) Tracking Issue for future roadmap Jul 7, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
tracking issue This is used to track a more complicated piece of work that might have multiple dependencies
Projects
None yet
Development

No branches or pull requests

2 participants
@Reecepbcups and others