tendermint VS substrate-open-working-groups

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

Polkadot Developer Community - Official community forum to discuss Substrate, PolkadotJS, and building cross-chain dApps.

And of course you can always develop your own blockchain with Substrate to support it.

A great framework for building your own blockchain, and use numerous off-the-shelf modules, with Substrate - https://substrate.dev/

If you're interested in developing yourself, check out substrate.dev.

Assuming you are working through the substrate.dev tutorials I have just had this same problem as worked around it by reverting the node template to the `polkadot-v0.9.25` tag.

Well. Polkadot created substrate (substrate.dev) which is a framework for building a blockchain, with a lot of general components to make it easy to "plug-and-play" your customizable blockchain. I tried using their "Getting Started" guide to spin up "my own blockchain", it was done within an hour or so.

Check out https://substrate.dev/ !

Substrate is not a chain; it's the default address style, named after the Substrate development framework which virtually all (if not all) parachains are currently built with. https://substrate.dev/

Do contact the Substrate project (basis of the Polkadot/Kusama project), which is based in Berlin. You can contact them on their channel (see their website on http://substrate.dev), they're friendly and many of them are native German speakers.