One of the goals of this branch has been to integrate Tor for broadcasting attestations and blocks as published by validators. Currently, the changes successfully enable tor integration. A successfull execution of 10 torbased validator on the same beacon node is here Tor-validator-goerli
Checkout branch torpush-diffContext, and build.
Enable and run tor on your machine if not already e.g. sudo apt install tor
Simply start nimbus client with validator following start
All attestations and block would be broadcasted on Tor
Nimbus-eth2 is an extremely efficient consensus layer (eth2) client implementation. While it's optimised for embedded systems and resource-restricted devices -- including Raspberry Pis, its low resource usage also makes it an excellent choice for any server or desktop (where it simply takes up fewer resources).
- Documentation
- Related projects
- Donations
- Branch guide
- Developer resources
- Tooling and utilities
- For researchers
- License
You can find the information you need to run a beacon node and operate as a validator in The Book.
The Quickstart in particular will help you quickly connect to either mainnet or the Prater testnet.
The Nimbus REST api is now available from:
- http://testing.mainnet.beacon-api.nimbus.team/
- http://unstable.mainnet.beacon-api.nimbus.team/
- http://unstable.prater.beacon-api.nimbus.team/
Note that right now these are very much unstable testing instances. They may be unresponsive at times - so please do not rely on them for validating. We may also disable them at any time.
This guide will take you through the basics of how to migrate to Nimbus from another client. See here for advanced options.
- status-im/nimbus-eth1: Nimbus for Ethereum 1
- ethereum/consensus-specs: Consensus specification that this project implements
You can check where the beacon chain fits in the Ethereum ecosystem in our Two-Point-Oh series: https://our.status.im/tag/two-point-oh/
If you'd like to contribute to Nimbus development, our donation address is 0x70E47C843E0F6ab0991A3189c28F2957eb6d3842
stable- latest stable release - this branch is recommended for most userstesting- pre-release branch with features and bugfixes slated for the next stable release - this branch is suitable for use on testnets and for adventurous users that want to live on the edge.unstable- main development branch against which PR's are merged - if you want to contribute to Nimbus, start here.
To get started with developing Nimbus itself, see the developer handbook.
We provide several tools to interact with ETH2 and the data in the beacon chain:
- ncli - command line tool with pretty printers, SSZ decoders, state transition helpers to interact with Eth2 data structures and functions
- ncli_db - command line tool to perform surgery on the Nimbus sqlite database
- multinet - a set of scripts to build and run several Eth2 clients locally
The state transition simulator can quickly run the Beacon chain state transition function in isolation and output JSON snapshots of the state. The simulation runs without networking and blocks are processed without slot time delays.
# build and run the state simulator, then display its help ("-d:release" speeds it
# up substantially, allowing the simulation of longer runs in reasonable time)
make NIMFLAGS="-d:release" state_sim
build/state_sim --helpThe local network simulation will create a full peer-to-peer network of beacon nodes and validators on a single machine, and run the beacon chain in real time. Parameters such as shard, validator counts, and data folders can be set in as environment variables before launching the simulation.
# Clear data files from your last run and start the simulation with a new genesis block:
make VALIDATORS=192 NUM_NODES=6 USER_NODES=1 local-testnet-minimal
# In another terminal, get a shell with the right environment variables set:
./env.sh bash
# In the above example, the network is prepared for 7 beacon nodes but one of
# them is not started by default (`USER_NODES`) - this is useful to test
# catching up to the consensus. The following command will start the missing node.
./tests/simulation/run_node.sh 0 # (or the index (0-based) of the missing node)
# Running a separate node allows you to test sync as well as see what the action
# looks like from a single nodes' perspective.By default, validators will be split in half between beacon node and validator
client processes (50/50), communicating through the
common validator API
(for example with 192 validators and 6 nodes you will roughly end up with 6
beacon node and 6 validator client processes, where each of them will handle 16
validators), but if you don't want to use external validator clients and instead
want to have all the validators handled by the beacon nodes you may use
USE_VC=0 as an additional argument to make local-testnet-minimal.
Alternatively, fire up our experimental Vagrant instance with Nim pre-installed and give us your feedback about the process!
The generic instructions from the Nimbus repo apply here as well.
Specific steps:
# This will generate the Prometheus config on the fly, based on the number of nodes:
make REMOTE_VALIDATORS_COUNT=192 NUM_NODES=6 USER_NODES=0 local-testnet-minimal
# In another terminal tab, after the sim started:
cd tests/simulation/prometheus
prometheusThe dashboard you need to import in Grafana is grafana/beacon_nodes_Grafana_dashboard.json.
Local testnets run for 4 epochs each, to test finalization. That happens only on Jenkins Linux hosts, and their logs are available for download as artifacts, from the job's page. Don't expect these artifacts to be kept more than a day after the corresponding branch is deleted.
Licensed and distributed under either of
- MIT license: LICENSE-MIT or https://opensource.org/licenses/MIT
or
- Apache License, Version 2.0: LICENSE-APACHEv2 or https://www.apache.org/licenses/LICENSE-2.0
at your option. These files may not be copied, modified, or distributed except according to those terms.