tendermint VS ibc-go

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

Upgrade Cosmos-SDK to SDK v0.44 from SDK v0.42 For a full list of updates in Cosmos-SDK v0.44.3 please see its changelog. Noteable highlights include:\n - Authz - Allows granting arbitrary privileges from one account (the granter) to another account (the grantee). \n- New modules:\n - Bech32IBC - Allows auto-routing of send msgs to addresses on other chains, once configured by governance. Allows you to do a bank send on Osmosis to a cosmos1... address, and it is automatically sent to the corresponding Cosmos Hub address over IBC. This is a big step in enabling more seemless IBC UX.\n - TxFees - Enables validators to easily accept txfees in multiple assets, whitelisted by governance, by declaring minimum fees in OSMO. Alternative fee assets are converted to their OSMO value, using the spot price on their primary OSMO base pair pool. This upgrade pre-whitelists all the assets currently supported on the Osmosis frontend with an OSMO basepair pool.\n- Implements Proposal 32 - Clawback of unclaimed Osmo and Ion on airdrop end date. (December 15th, 5PM UTC)\n- Upgrade IBC from a standalone module in the SDK to IBC v2. This improves the utility of Ethereum Bridges and Cosmwasm bridges.\n- Blocking OFAC banned ETH addresses \n- Numerous minor bug fixes, gas fixes, and significant speedups.

2) ibc-go library patch to assist in handling of 'unknown' client states (see here: https://github.com/cosmos/ibc-go/issues/850).

This release will include a few very important items: 1) Increasing the staking APR to 300% 2) ibc-go library patch to assist in handling of 'unknown' client states (see here: https://github.com/cosmos/ibc-go/issues/850). TDLR: hopefully allowing the stuck terra transactions to become 'unstuck'. The proposal for this release was just raise. See: https://www.mintscan.io/sifchain/proposals/29 https://wallet.keplr.app/#/sifchain/governance?detailId=29

The Inter-Blockchain Communication protocol (IBC), code name Stargate, launched February 2021 and (like the name implies) allows all these chains to communicate with each other.

IBC Protocol

Rizon utilizes Tendermint and is powered by Inter Blockchain Communication. Its upcoming products bring a decent value to the market, in particular expanding numerous use-cases for stablecoins, providing decentralized governance and issuance for them.

To become a relayer, it's worth understanding IBC (https://ibcprotocol.org or https://github.com/cosmos/ibc-go ). The IBC Go team just (as in this morning) started a webinar series about deep diving into IBC. Look for the link of today's recording on Discord. The Hermes technical details are here: https://hermes.informal.systems and a Medium article is in the works that details how to easily set up. (I wish I finished it by today.) Maybe, we can publish it next week.

"Regarding the upcoming mainnet upgrade initially scheduled to be performed at the block height of 2,472,800, we would like to inform our partners and community that we would recommend to postpone it to a later date due to the following reasons: - In the past weeks, we have conducted several dry-runs and discovered a potential issue that could affect the performance and efficiency of the upcoming mainnet upgrade; - In addition, there was a significant change in ibc-go last week, so we will need to make changes accordingly on the new mainnet binary. These changes on ibc-go (more details are at ibc-go’s complete changelog https://github.com/cosmos/ibc-go/blob/v1.2.0/CHANGELOG.md) also result in the new release of tendermint from 0.34.12 to 0.34.13 (https://github.com/tendermint/tendermint/releases). The core team is now working hard on updating the binary and resolving the potential issue. We will update you with more information about this upgrade as early as we can. Meanwhile, p​​lease consider changing your vote to No or No with Veto If you have voted for proposal 5 before. Thank you for your support and please feel free to let us know if you have any questions. "