nimbus-eth2/docker/dist
Zahary Karadjov af3ef5a9b0
Re-enable the ARM packaging
2023-06-27 03:58:10 +03:00
..
base_image dist: build Windows binary with newer compiler (#3548) 2022-03-28 10:03:11 +02:00
binaries Provide a backwards-compatible sym link in the nimbus-eth2 docker file image 2022-12-23 19:28:52 +02:00
Dockerfile.amd64 Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
Dockerfile.amd64-opt add optimized Linux amd64 flavor (#4914) 2023-05-11 13:05:52 +03:00
Dockerfile.arm Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
Dockerfile.arm64 Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
Dockerfile.macos Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
Dockerfile.macos-arm64 Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
Dockerfile.win64 Include auxiliary tools to nightly builds 2022-08-11 17:57:44 +03:00
README-Windows.md.tpl bin dist related docs (#2684) 2021-07-05 12:31:25 +02:00
README.md.tpl Add support for the Ropsten beacon chain (#3648) 2022-05-20 18:26:07 +03:00
entry_point.sh Re-enable the ARM packaging 2023-06-27 03:58:10 +03:00

README.md.tpl

# Binary Nimbus beacon node distribution

This binary distribution of the Nimbus eth2 package is compiled
in a [reproducible way](https://reproducible-builds.org/) from source files
hosted at https://github.com/status-im/nimbus-eth2.

The tarball containing this README uses the following naming scheme:

```bash
nimbus-eth2_<TARGET OS>_<TARGET CPU>_<VERSION>_<GIT COMMIT>.tar.gz
```

For a more complete and up-to-date documentation, please refer to the [Nimbus book](https://status-im.github.io/nimbus-eth2/).

## Reproducing the build

Besides the generic build requirements, you also need [Docker](https://www.docker.com/).

```bash
git clone https://github.com/status-im/nimbus-eth2.git
cd nimbus-eth2
git checkout GIT_COMMIT
make update
make dist
```

## Significant differences from self-built binaries

Binary builds are configured to maximise portability, disabling the use of
advanced CPU features which may result in lower performance on some hardware.

## Running a node

See https://nimbus.guide for full instructions on running a node.

To connect to mainnet with default options:

```bash
./run-mainnet-beacon-node.sh
```

The script will forward all supplied options to the beacon node executable:

```bash
./run-mainnet-beacon-node.sh --log-level=DEBUG --tcp-port=9050
```

To monitor the Eth1 validator deposit contract, you'll need to pair
the Nimbus beacon node with a Web3 provider capable of serving Eth1
event logs. This could be a locally running Eth1 client such as Geth
or a cloud service such as Infura. For more information please see
our setup guides:

https://status-im.github.io/nimbus-eth2/eth1.html

By default, the script will ask you to enter a web3 provider URL interactively,
but this can be bypassed by specifying a websocket `WEB3_URL` environment variable:

```bash
# using a local mainnet instance
WEB3_URL="ws://localhost:8545" ./run-mainnet-beacon-node.sh
```

## Testnet

The `prater` testnet runs on

```bash
# using a local Goerli instance
WEB3_URL="ws://localhost:8545" ./run-prater-node.sh --max-peers=150
```