Evmos is a scalable, high-throughput Proof-of-Stake EVM blockchain that is fully compatible and interoperable with Ethereum. It's built using the Cosmos SDK which runs on top of the CometBFT consensus engine.

To learn how Evmos works from a high-level perspective, go to the Protocol Overview section of the documentation. You can also check the instructions to Run a Node.

Our documentation is hosted in a separate repository and can be found at docs.evmos.org. Head over there and check it out.

For prerequisites and detailed build instructions please read the Installation instructions. Once the dependencies are installed, run:

make install

Or check out the latest release.

The following chat channels and forums are great spots to ask questions about Evmos:

• Evmos X (Twitter)
• Evmos Discord
• Evmos Forum

Looking for a good place to start contributing? Check out some good first issues.

For additional instructions, standards and style guides, please refer to the Contributing document.

See our open positions on our Careers page.

Starting from April 21st, 2023, the Evmos repository will update its License from GNU Lesser General Public License v3.0 (LGPLv3) to Evmos Non-Commercial License 1.0 (ENCL-1.0). This license applies to all software released from Evmos version 13 or later, except for specific files, as follows, which will continue to be licensed under LGPLv3:

• x/erc20/keeper/proposals.go
• x/erc20/types/utils.go

LGPLv3 will continue to apply to older versions (<v13.0.0) of the Evmos repository. For more information see LICENSE.

The following header including a license identifier in SPDX short form has been added to all ENCL-1.0 files:

// Copyright Tharsis Labs Ltd.(Evmos)
// SPDX-License-Identifier:ENCL-1.0(https://github.com/evmos/evmos/blob/main/LICENSE)

Exempted files contain the following SPDX ID:

// Copyright Tharsis Labs Ltd.(Evmos)
// SPDX-License-Identifier:LGPL-3.0-only

Find below an overview of the Permissions and Limitations of the Evmos Non-Commercial License 1.0. For more information, check out the full ENCL-1.0 FAQ here.