Nim implementation of the Ethereum Beacon Chain https://nimbus.guide
Go to file
Zahary Karadjov 903cb8a8b5 A LibP2P-based networking stack;
To enable it, comment out the 'withLibp2p' line in nim.cfg

The history was squashed in order to remove an accidentally
commited binary file.

Other changes:

* SSZ was adapted to use the common serialization framework

* gossibsup.subscribe is not using async handlers at the moment
  and this allowed me to simplify it
2019-03-12 13:36:55 +02:00
.vscode vscode: add tasks 2018-12-13 11:14:21 -06:00
beacon_chain A LibP2P-based networking stack; 2019-03-12 13:36:55 +02:00
benchmarks Update BLS to the latest scheme. (#80) 2019-02-05 17:13:29 +01:00
research more 0.4.0 spec updates: renamings, continue Proposal updates, and note several more functions which were verified not to have changed in 0.4.0 (#163) 2019-03-11 09:33:24 -06:00
tests A LibP2P-based networking stack; 2019-03-12 13:36:55 +02:00
.appveyor.yml Update ci configs 2019-01-17 14:38:16 +02:00
.gitignore initial commit 2018-07-20 15:46:03 +02:00
.travis.yml Update ci configs 2019-01-17 14:38:16 +02:00
LICENSE-APACHEv2 initial commit 2018-07-20 15:46:03 +02:00
LICENSE-MIT initial commit 2018-07-20 15:46:03 +02:00
README.md Update README.md 2019-03-08 12:06:21 -06:00
beacon_chain.nim Add the types used in the beacon chain 2018-07-20 20:18:56 +02:00
beacon_chain.nimble A LibP2P-based networking stack; 2019-03-12 13:36:55 +02:00
nim.cfg A LibP2P-based networking stack; 2019-03-12 13:36:55 +02:00

README.md

Ethereum Beacon Chain

Build Status (Travis) Windows build status (Appveyor) License: Apache License: MIT Stability: experimental

Nimbus beacon chain is a research implementation of the beacon chain component of the upcoming Ethereum Serenity upgrade, aka eth2. See the main Nimbus project for the bigger picture.

You can check where the beacon chain fits in the Ethereum research ecosystem in the Status Athenaeum.

Test vectors

The Eth 2.0 test vectors and their generators are available in a dedicated repository.

Building and Testing

The beacon chain components require that you have Nim installed - the easiest way to get started is to head over to the main Nimbus repository and follow the build instructions there. Once you're able to build nimbus:

Then:

# Or wherever you cloned nimbus
cd nimbus

# Prep environment
make
./env.sh bash

# You're now in a shell environment that has the right Nim version available

cd..

git clone https://github.com/status-im/nim-beacon-chain
cd nim-beacon-chain

# Build binaries and run test suite
nimble build
nimble test

This should produce some passing tests.

Beacon node simulation

The beacon node simulation is will create a full peer-to-peer network of beacon nodes and validators, and run the beacon chain in real time. To change network parameters such as shard and validator counts, see start.sh.

# Start beacon chain simulation, resuming from the previous state (if any)
./tests/simulation/start.sh

# Clear data from last run and restart simulation with a new genesis block
rf -rf tests/simulation/data ; ./tests/simulation/start.sh

# Run an extra node - by default the network will launch with 9 nodes, each
# hosting 10 validators. The last 10 validators are lazy bums that hid from the
# startup script, but you can command them back to work in a separate terminal
# with:
./tests/simulation/run_node.sh 9

You can also separate the output from each beacon node in its own panel, using multitail:

USE_MULTITAIL="yes" ./tests/simulation/start.sh

You can find out more about it in the development update.

Alternatively, fire up our experimental Vagrant instance with Nim pre-installed and give us yout feedback about the process!

State transition simulation

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.

cd research
# build and run state simulator, then display its help - -d:release speeds it
# up substantially, allowing the simulation of longer runs in reasonable time
nim c -d:release -r state_sim --help

Convention

Ethereum Foundation uses:

  • snake_case for fields and procedure names
  • MACRO_CASE for constants
  • PascalCase for types

Nim NEP-1 recommends:

  • camelCase for fields and procedure names
  • PascalCase for constants
  • PascalCase for types

To facilitate collaboration and comparison, Nim-beacon-chain uses the Ethereum Foundation convention.

License

Licensed and distributed under either of

or

at your option. This file may not be copied, modified, or distributed except according to those terms.