# Evmos vs Polygon

**Polygon PoS** (formerly **Matic**) is built on a fork of **Tendermint** called **Peppermint**.
Their reasons for forking **Tendermint** are somewhat dubious and their fork is very much out-of-date with upstream **Tendermint**.

**Evmos** is built on upstream **Tendermint**.
They were able to solve some of the same problems that were the impetus for forking **Peppermint** like Ethereum-compatible keys without making any changes to **Tendermint** itself.
**Evmos** is also **IBC**-capable (Inter-Blockchain Communication Protocol), whereas Polygon PoS presently is not.

Evmos is a better architecture that can better leverage upstream work on Tendermint/Cosmos SDK while delivering the same benefits as Polygon PoS.

## Comparison table

| Param | Evmos | Matic |
|--------------------|----------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| **Layer** | Layer 1 | Layer 2 (possible to make Layer 1 but difficult to achieve) |
| **Consensus core** | Tendermint | Fork of **Tendermint** called **Peppermint** |
| **Node engine** | Cosmos SDK | There are twe blockchain networks Heimdall + BOR which are works independently and has some synchronization between. |
| **Documentation** | Every Tendermint and Cosmos SDK documentation are acceptable + Evmos documentation which are sufficiently detailed | Partially applicable to Tendermint and Cosmos SDK. There is also Polygon(Matic) documentation which is not detailed enough |
| **Tooling** | Any Tendermint and Cosmos SDK tools are applicable. There is also some Evmos tools. | Partially Tendermint and Cosmos SDK tools are applicable. There is also some BOR and Heimdall tools. |
| **Upgradability** | [**x/upgrade**](https://docs.cosmos.network/v0.47/modules/upgrade) Cosmos SDK module | In order to upgrade matic network it require to upgrade one of internal networks Heimdall or BOR either both. By default it is not supported [**x/upgrade**](https://docs.cosmos.network/v0.47/modules/upgrade) Cosmos module but it seems there is an opportunity to connect it. Seems it has some upgrade process but need to investigate |
| **Bridge** | Gravity IBC bridge. Any another bridges which are using IBC. <br/>Any another bridge which are EVM/Cosmos-compatible | **matic-bridge**, any another bridge which are EVM-compatible |