
One Network. Infinite Chains. Tomorrow.

The state machine replication engine for the interchain. CometBFT is a fork and successor of Tendermint Core.

One Network. Infinite Chains. Tomorrow.

☑️mempool - experimental feature to limit the number of peers to gossip transactions to ☑️nop mempool ☑️p2p performance optimisations ( together with Osmosis) ☑️Improvements to the performance of blocksync (together with Osmosis! ) ☑️BLS12-381 curve ☑️PBTS ☑️Support for pebbledb ☑️Remove persistence of genesis file in the DB ☑️Forcing compaction on pruning to reduce the storage footprint ☑️Background pruning to not block consensus ☑️DataCompanion API (gRPC endpoints to manage what is stored on Comet nodes) ☑️Support for a different key format in the DB

CometBFT v1.0.0 is out 🚀! This release marks a major milestone in the lifecycle of CometBFT. Building on the solid foundation of the previous version, it introduces additional features and improved performance. Below are only some of the highlights, more details coming up in a blog post! You can also check out the Changelog github.com/cometbft/cometbft… and upgrading guide github.com/cometbft/cometbft… for migrating to v1 from v0.38! Thank you all for your valuable feedback, support and especially @osmosis for their contributions to this release! Also kudos to the core team at @informalinc ♥️ Fantastic work everyone!

The CometBFT team @informalinc has finished merging the DOG 🐾 protocol feature and it is now available in `main` branch. Read more below 👇
Announcing DOG protocol, an improvement to the @cometBFT mempool gossip sub-system. The Dynamic Optimal Graph (DOG) protocol slashes bandwidth use, improves performance, and speeds up transaction confirmations. 🧵

🧐
Lots of interesting things going on in the @cometbft codebase. DOG Mempool Gossip: github.com/cometbft/cometbft… QUIC: github.com/cometbft/cometbft… Shoutout to the team working on comet for all the hard work!! 🚀🚀🚢🚢

Join the Interchain stack experts at Cosmoverse this year.
1/ On day 3 of #Cosmoverse2024, Oct 23, get hands-on experience building with the Interchain Stack. Join workshops with ICF devs and steward teams in the Al Maasa Room. Only 40 slots per workshop - Check this thread for more details + how you can register now ⬇️

good reminder if you're building on @cometbft or operating Hermes IBC relayer, please read ⤵️
1/ Liveness is an important concept in the Interchain Stack, affecting operational reliability, scalability, and performance. Yet, the inherent challenges of decentralized blockchain development make it challenging to provide liveness guarantees at the protocol level today.

10/10 We hope you've found this thread helpful. Make sure you follow @cometbft for future announcements. Like & Repost the quote below, thanks for your support!
1/10 🧵 In the past we wrote about responsiveness in consensus algorithms and why it's a critical property. Despite its popularity, questions persist about the responsiveness of the Tendermint consensus algorithm. For everyone in doubt 👇

9/10 In summary, Tendermint is classified as optimistically responsive, meaning it performs well under favorable conditions, but its speed is limited when faced with faulty leaders or network asynchrony (a standard assumption). Full article ⬇️ informal.systems/blog/tender…

8/10 Comet's implementation of Tendermint and its design facilitates quick decision-making when the network is stable and incorporates mechanisms to handle delays gracefully. This dual focus ensures both efficiency and resilience.

7/10 Tendermint and CometBFT are widely used in the Cosmos ecosystem, but have also found adoption in various other architectures like @AstriaOrg, @CelestiaOrg and @0xPolygon powering various blockchain applications.

6/10 Decision-making may slow down in non-optimistic cases, such as faulty leaders or network issues due to the need for timeouts and leader changes. This is standard for algorithms designed for the leader-based partially synchronous model such as Tendermint or HotStuff.

5/10 🔄 Tendermint's Responsiveness works optimistically. It’s responsive when conditions are ideal, i.e., optimistic conditions.

4/10 Most BFT algorithms, like Tendermint and HotStuff, are leader-based and partially synchronous. Decisions are made quickly if the network behaves well and the leader is honest. However, faulty leaders or network delays can complicate things.

3/10 Responsive vs. Non-Responsive protocols In responsive protocols, consensus latency aligns with actual network delays. In contrast, non-responsive protocols depend on time bounds set for worst-case scenarios, potentially slowing down the process.

2/10 What does responsiveness mean? Responsiveness ensures that consensus speed (i.e., block building latency) depends on actual network delays rather than conservative time bounds, directly impacting the performance of distributed systems like blockchains.