Landslide
Ask or search…
K

Tendermint Core -> Landslide Core

What Tendermint looks like in AVAX.

Details

LandslideCore is a customized version of the Tendermint blockchain software, designed to operate using the Avalanche consensus algorithm rather than the default Tendermint consensus mechanism.
Notice this forked version of Tendermint removes the original Tendermint consensus algorithm and replaces it with the Avalanche consensus, which is faster, more efficient, and more scalable than the original algorithm.
In addition, the following modules are removed from Tendermint Core: Mempool reactor, and the Consensus Reactor. The P2P networking layer and the HTTP servers are augmented to use the those in Avalanche.
With LandslideCore, developers can leverage the powerful features of the Avalanche network, while still using a familiar blockchain software platform. The result is a blockchain software that provides faster finality times, better throughput, and greater scalability, making it an ideal platform for developing high-performance decentralized applications.

Native Tendermint

Below is a diagram of native Tendermint, (e.g. what Tendermint looks like currently.)

Landslide Core

Notice this forked version of Tendermint removes the original Tendermint consensus algorithm and replaces it with the Avalanche consensus, which is faster, more efficient, and more scalable than the original algorithm.
In addition, the following modules are removed from Tendermint Core: Mempool reactor, and the Consensus Reactor. The P2P networking layer and the HTTP servers are augmented to use the those in Avalanche.
With LandslideCore, developers can leverage the powerful features of the Avalanche network, while still using a familiar blockchain software platform. The result is a blockchain software that provides faster finality times, better throughput, and greater scalability, making it an ideal platform for developing high-performance decentralized applications.

Connecting Landslide Core to IBC

Here we imagine Cosmos and Avalanche as two groups of computers. They want to talk to each other, but they speak different languages. So they use a special helper called IBC to translate for them. Avalanche has a few helpers, called modules and subnets, that help them talk to Cosmos. One module talks to another module in Avalanche, and another module talks to a subnet, which confirms state on the P-Chain. They are able to understand each other thanks to IBC.
Here we see Cosmos and Avalanche as two groups of ecosystems. They want to talk to each other, but they speak different languages. So they use a special helper called IBC to translate for them. Avalanche has a few helpers, called modules and subnets, that help them talk to Cosmos. One module talks to another module in Avalanche, and another module talks to a subnet, which confirms state on the P-Chain. They are able to understand each other thanks to IBC.
Transferring OSMO assets from Cosmos to AVAX via IBC.