Research on ethermint/EVMOS

Vishwas1 commented 2 years ago

Ethermint: EVM Compatible, Tendermint PoS

the perfect fusion between Ethereum and Cosmos

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

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

Ethermint is a proof-of-stake blockchain, built on the Cosmos SDK, that is EVM (Ethereum Virtual Machine) compatible.
Basically, with Ethermint, developers can run a Tendermint PoS equivalent of Ethereum, and benefit from all the advantages of Ethereum, such as Solidity smart-contracts and development tools.
Because it is built using the Cosmos SDK, Ethermint is also compatible and connected with other blockchains in the Cosmos ecosystem through the Inter Blockchain Community Protocol (IBC).

Components of Ethermint

Ethereum Virtual Machine: EVM is the leading standard for smart-contract development. With EVM compatibility, developers can build the same way that they would do on Ethereum, and benefit from the same tools and applications.
Cosmos SDK: The Cosmos SDK is an open-source framework for building multi-asset public PoS blockchains interoperable with the Cosmos ecosystem and notably the Cosmos Hub. #9
Tendermint's Core BFT POS consensus engine: Tendermint Core is the consensus system of the Tendermint platform that additionally consists of a generic application interface. #6

Features

full Web3 compatibility
fully compatible with Ethereum’s Web3 interface and the existing tooling around Ethereum clients via RPC
Built on Tendermint, it is faster and cheaper to execute smart contract s
unlimited horizontal scalability:
- By itself, Ethermint can process around 200 TPS (transactions per second).
- But with the Cosmos Hub, you can increase that number significantly.
- it is possible to create a second, third, etc. Ethermint zone, increasing the TPS with every Ethermint zone that is added.
- This method of achieving horizontal scalability is unique to the Cosmos network. And it’s infinitely scalable.
Instant transaction finality: where blocks are finalized in around 1 second on average
offer built-in interoperability functionalities with other Cosmos and BFT chains by using IBC
Developers can also benefit from using a bridge network (like Chainbridge, or a Peg Zone) to enable interoperability between mainnet Ethereum and Ethermint.

Why etheremint ?

even though there are many new smart contract platforms and multi-blockchain ecosystems like Cosmos. Ethereum still has one of the largest community bases of users and developers within the blockchain environment.
Ethereum requires improvement in scalability, gas price, and the ability to customize a project’s desired functionality. Through leveraging Tendermint, Ethermint can provide lower gas prices and a more accessible framework for customization.
Through the EVM as a Cosmos SDK module, Ethermint can support any smart contracts, DApps or DAOs deployed on Ethereum.

The sum of these features allows developers to leverage existing Ethereum ecosystem tooling and software to seamlessly deploy smart contracts which interact with the rest of the Cosmos ecosystem!

Tendermint

Ethereum

Etheremint

Tendermint Core would be responsible for

- Sharing blocks and transactions between nodes
- Establishing a canonical/immutable order of transactions (the blockchain)

The EVM module (x/evm) packaged inside Ethermint can be used separately as its own standalone module.

Interoperability

Ethermint will also offer built-in interoperability functionalities with other Cosmos and BFT chains by using IBC.
Developers can also benefit from using a bridge network (like Chainbridge, or a Peg Zone) to enable interoperability between mainnet Ethereum and Ethermint.

References

arnabghose997 commented 2 years ago

Following are the steps for setting up a 2 node cluster in EVMOS

Step 1 - Clone the EVMOS repo from github:

> git clone https://github.com/tharsis/evmos.git
> cd evmos
> make install

Step 2 - Create a directory which have the folders for our nodes: mkdir ~/multi-node
Step 3 - Run the following command to initialize the 2 nodes

> evmosd testnet init-files --v 2 --output-dir ~/multi-node

--v- Number of validator nodes

--output-dir - Directory to store the nodes related info

Step 4 - The directory structure inside the directory multi-node will looks something like following:

├── gentxs
│   ├── node0.json
│   └── node1.json
├── node0
│   └── evmosd
│       ├── config
│       │   ├── app.toml
│       │   ├── config.toml
│       │   ├── genesis.json
│       │   ├── node_key.json
│       │   └── priv_validator_key.json
│       ├── data
│       │   └── priv_validator_state.json
│       └── key_seed.json
└── node1
    └── evmosd
        ├── config
        │   ├── app.toml
        │   ├── config.toml
        │   ├── genesis.json
        │   ├── node_key.json
        │   └── priv_validator_key.json
        ├── data
        │   └── priv_validator_state.json
        └── key_seed.json

We now have to make port changes for some parameters, because at this moment, both nodes have same port configuration for the most params

The following parameters of node1/evmosd/config/app.toml should have the values set as follows:

address = "tcp://0.0.0.0:2317" (Under [api])
address = "0.0.0.0:10090" (Under [grpc])
address = "0.0.0.0:9191" (Under [grpc-web])
address = "0.0.0.0:8555" (Under [json-rpc])
address = "0.0.0.0:8556" (Under [json-rpc])

The following parameters of node1/evmosd/config/config.toml should have the values set as follows:

proxy_app = "tcp://127.0.0.1:36658”
laddr = "tcp://0.0.0.0:36657" (Under [rpc])
laddr = "tcp://0.0.0.0:34323" (Under [p2p])
persistent_peers = "<node-id>@0.0.0.0:34223" (Under [p2p], leave the <node-id> as it is and change the IP address to 0.0.0.0 and port to 34223 which is actually the port of node0's listen address (defined below)

The following parameters of node0/evmosd/config/config.toml should have the values set as follows:

laddr = "tcp://0.0.0.0:34223" (Under [p2p])
persistent_peers = "<node-id>@0.0.0.0:34323" (Under [p2p], leave the <node-id> as it is and change the IP address to 0.0.0.0 and port to 34323 which is actually the port of node1's listen address (defined above)

Save the files and exit

Step 5 - Run both nodes

# Node0
> evmosd start --home ~/multi-node/node0/evmosd

# Node1 (In another terminal window)
> evmosd start --home ~/multi-node/node1/evmosd

Vishwas1 commented 2 years ago

arnabghose997 commented 2 years ago

Unified portal of Evmos: https://evmos.me/

Blog on this: https://evmos.blog/featuring-evmos-me-an-all-in-one-evmos-portal-da0676f32f28

hypersign-protocol / whitepaper