# Tendermint Core -> Landslide Core

## 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.)

{% @mermaid/diagram content="---
title: Native Tendermint
------------------------

flowchart TB
id3\[(Tendermint Core)] --> id4(Mempool) --> id5(Mempool Reactor)
id3\[(Tendermint Core)] --> id6\[(State, StateDB)] --> id7(Consensus Reactor)
id3\[(Tendermint Core)] --> id8(HTTP) --> id9(P2P: Switch, Reactor)
id3\[(Tendermint Core)] --> id10(Block Executor)
id3\[(Tendermint Core)] --> id11\[(BlockDB, BlockStore)]
style id5 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff,stroke-dasharray: 5 5
style id7 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff,stroke-dasharray: 5 5
style id9 fill:#bbf,stroke:#f66,stroke-width:2px,color:#fff,stroke-dasharray: 5 5
" %}

### 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.

{% @mermaid/diagram content="---
title: Landslide Core
---------------------

flowchart TB
id3\[(Landslide Core)] --> id4(Mempool) --> id53
subgraph id53 \[Avalanche Ecosystem]
direction TB
id2(Mempool Reactor)
id7(Avalanche Consensus)
id9(P2P: Switch, Reactor)
end
id3\[(Landslide Core)] --> id6\[(State, StateDB)] --> id7
id3\[(Landslide Core)] --> id8(HTTP) --> id9(P2P: Switch, Reactor)
id3\[(Landslide Core)] --> id10(Block Executor)
id3\[(Landslide Core)] --> id11\[(BlockDB, BlockStore)]
style id2 fill:#f9f,stroke:#333,stroke-width:1px
style id7 fill:#f9f,stroke:#333,stroke-width:1px
style id9 fill:#f9f,stroke:#333,stroke-width:1px" %}

### 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.

<figure><img src="/files/dhSKlKbjDBZ3bEaRkvk2" alt="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."><figcaption><p>Transferring OSMO assets from Cosmos to AVAX via IBC.</p></figcaption></figure>

{% @mermaid/diagram content="flowchart TB
id1(IBC Relayer)-->id3
id1(IBC Relayer)-->id5
id55(AVAX C-chain)-->id5
id56(AVAX X-chain)-->id5
subgraph id3 \[Cosmos Chain: Osmosis]
direction TB
id2(Avalanche Light Client)-->id4(CosmosSDK)-->id91(Tendermint Core)
end
subgraph id5 \[AVAX Subnet]
direction TB
id21(Tendermint Light Client)-->id6(LandslideSDK)-->id9(Landslide Core)
end
style id2 fill:#f9f,stroke:#333,stroke-width:1px
style id6 fill:#f9f,stroke:#333,stroke-width:1px
style id9 fill:#f9f,stroke:#333,stroke-width:1px
style id21 fill:#f94,stroke:#333,stroke-width:1px" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.landslide.network/product-guides/landslide-and-cometbft/tendermint-core-greater-than-landslide-core.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.