Open Vishwas1 opened 2 years ago
Following are the steps for setting up a 2 node cluster in EVMOS
> git clone https://github.com/tharsis/evmos.git
> cd evmos
> make install
mkdir ~/multi-node
> evmosd testnet init-files --v 2 --output-dir ~/multi-node
--v
- Number of validator nodes
--output-dir
- Directory to store the nodes related info
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
# Node0
> evmosd start --home ~/multi-node/node0/evmosd
# Node1 (In another terminal window)
> evmosd start --home ~/multi-node/node1/evmosd
Unified portal of Evmos: https://evmos.me/
Blog on this: https://evmos.blog/featuring-evmos-me-an-all-in-one-evmos-portal-da0676f32f28
Ethermint: EVM Compatible, Tendermint PoS
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. #9Tendermint's Core BFT POS
consensus engine: Tendermint Core is the consensus system of the Tendermint platform that additionally consists of a generic application interface. #6Features
Why etheremint ?
Tendermint
Ethereum
Etheremint
Tendermint Core would be responsible for
Interoperability
References