https://github.com/binocarlos/veth
Run multiple versions of geth locally with Docker
https://github.com/binocarlos/veth
docker ethereum ethereum-blockchain ethereum-client geth
Last synced: 4 months ago
JSON representation
Run multiple versions of geth locally with Docker
- Host: GitHub
- URL: https://github.com/binocarlos/veth
- Owner: binocarlos
- Created: 2017-09-19T10:43:18.000Z (over 7 years ago)
- Default Branch: master
- Last Pushed: 2017-12-19T20:19:34.000Z (over 7 years ago)
- Last Synced: 2025-01-03T02:56:35.454Z (5 months ago)
- Topics: docker, ethereum, ethereum-blockchain, ethereum-client, geth
- Language: Shell
- Homepage:
- Size: 31.3 KB
- Stars: 2
- Watchers: 3
- Forks: 0
- Open Issues: 1
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# veth
veth is a bash script that uses Docker to run multile instances of [geth](https://github.com/ethereum/go-ethereum) locally.
## install
First - [install docker](https://docs.docker.com/engine/installation/), then download and install the script:
```bash
$ cd ~
$ docker run --rm binocarlos/veth:v0.0.8 > veth
$ sudo mv veth /usr/local/bin/veth
$ sudo chmod a+x /usr/local/bin/veth
```
Run all commands from the root of your project - veth keeps state in the `.veth` folder which should be `.gitignored`
#### initialize
Each node has a name that you pass to each of the commands to dictate which node to operate on. If you are working with a single node you can omit the name and it will default to `node1`.
Initialize your nodes:
```bash
$ veth init chain1
$ veth init chain2
```
This will create folders to hold blockchain state: `.veth/{chain1,chain2}`
Each state folder contains:
* `account.txt` - the account id for the miner account
* `password.txt` - the password for the miner account
* state for the geth node
#### list
List the current blockchain folders:
```bash
$ veth list
```
To remove a node's state, delete it's state folder:
```bash
$ rm -f .veth/node2
```
#### start
Start chain1, then start chain2 pointing to chain1:
```bash
$ veth start chain1
$ veth start chain2 chain1
```
If you had a third node - you could point it to either chain1 or chain2:
```bash
$ veth start chain3 chain2
```
#### start remote
If you want to run veth on node A then run veth on node B connected to node A:
On node A:
```bash
$ export VETH_EXPOSE_RPC=1
$ veth init
$ veth cluster
$ veth enode
```
This will print the enode ID for node A - slack it ready for node B.
You also need to slack the IP address of node A.
Then on node B:
```bash
$ export VETH_EXPOSE_RPC=1
$ veth init
$ veth connect 192.168.0.20 69905763c3afd831a58f3368093933a38038f56a453f63b3a11ecf9a66d5b3914682787f96ecc57d067d8bf227633488f225aac6211e8f838cffabc69ccd549e
```
#### logs
To follows logs for a node:
```bash
$ veth logs chain1
```
#### attach
To attach to the console for a node:
```bash
$ veth attach chain1
```
#### exec
To run JS commands directly:
```bash
$ veth exec chain1 'admin.nodeInfo.id'
```
#### stop
To stop a node:
```bash
$ veth stop chain1
```
## multi-node run through
To get a 2 node geth cluster running:
```bash
$ veth init chain1
$ veth init chain2
$ veth start chain1
$ veth start chain2 chain1
$ veth exec chain1 'admin.peers'
$ veth attach chain1
$ veth logs chain1
```
## notes
The networkID = `23422` - you can override this with:
```bash
$ GETH_NETWORK_ID=10050
```