tendermint VS substrate

Tendermint Core / CometBFT — a state machine replication engine (written in Go);

There are good use-cases, but to much focus on cryptocurrencies. Frameworks are not well designed to be used in other use-cases. Best that I have found that doesn't forces you to a specific architecture is Tendermint, but is not even close to state-of-the-art performance and scalability. Everything else is designed around cryptocurrency and smart contracts.

BFT is an algorithm that ensures that the whole network works well even if a few members are acting fraudulently. As long as these fraudulent members are less than 33% of those who have voting power, the network will work fine. Those with voting power are those with something at stake. Cosmos uses a type of BFT consensus engine known as Tendermint. Cosmos uses Tendermint because it provides the best support for building POS blockchains.

Relevant Github ticket showing chains are now scrambling to decide which fork to use: https://github.com/tendermint/tendermint/issues/9972

BlockX is based on Tendermint Core, which relies on a set of validators that are responsible for committing new blocks in the blockchain. These validators participate in the consensus protocol by broadcasting votes which contain cryptographic signatures signed by each validator's private key.

Built with Cosmos and Tendermint.

Haqq is a scalable, high-throughput Proof-of-Stake blockchain that is fully compatible and interoperable with Ethereum. It's built using the Cosmos SDK which runs on top of Tendermint Core consensus engine.Haqq allows for running vanilla Ethereum as a Cosmos application-specific blockchain. This allows developers to have all the desired features of Ethereum, while at the same time, benefit from Tendermint’s PoS implementation. Also, because it is built on top of the Cosmos SDK, it will be able to exchange value with the rest of the Cosmos Ecosystem through the Inter Blockchain Communication Protocol (IBC)Features

Tendermint

Substrate — a framework for building application-specific blockchains (written in Rust);

frame-benchmarking = { version = "4.0.0-dev", default-features = false, optional = true, git = "https://github.com/paritytech/substrate.git", branch = "polkadot-v1.0.0" }

To offer some perspective outside of the typical "all crypto is a scam", Parity is doing some cool stuff with a rust modular blockchain library called Substrate https://github.com/paritytech/substrate.

Rust takes the cake in the blockchain space: Substrate, Cosmos (CosmWasm), and Solana. All of the zero knowledge cryptography libraries used for layer 2 solutions are written in Rust, compiling to Wasm (see arkworks, Risc0). Ethereum's next version of smart contracts will even use a restricted subset of Wasm ("Ewasm") instead of EVM.

Verifying NPoS election solution graph and its score is a memory-intensive operation that needs to be performed within a single block time. Under the current runtime constraints, a solution graph with 22,500 nominators can be verified well within the block production time on Polkadot. There are plans to improve on this and implement multi-block election solution verification, after which, the NPoS system can scale to incorporate more nominators.

Fast-unstake is now available on Kusama. This allows instant unstaking if you have not participated in staking in the last 28 eras. https://github.com/paritytech/substrate/pull/12129

First, any outstanding multisig calls (ones where one signatory has signed, but not the threshold) will not be able to execute. Please either finish your multisig calls before this upgrade, or wait until after it is completed. https://github.com/paritytech/substrate/pull/12072

Github: https://github.com/paritytech/substrate