README
¶
Prysmatic Labs Validator Client Implementation
This is the main project folder for a validator client implementation of Ethereum Serenity in Golang by Prysmatic Labs. A validator client attaches to a running beacon node in order to perform proposer/attester responsibilities and manage the lifecycle of a particular shard upon being assigned to one.
Before you begin, check out our main README and join our active chat room on Discord or Gitter below:
Also, read the latest sharding + casper design spec, this design spec serves as a source of truth for the beacon chain implementation we follow at prysmatic labs. Check out the FAQs. Refer this page on why we are combining sharding and casper together.
Documentation
¶
Overview ¶
This code was adapted from https://github.com/ethereum/go-ethereum/blob/master/cmd/geth/usage.go
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
Package client represents the functionality to act as a validator.
|
Package client represents the functionality to act as a validator. |
|
iface
Package iface exists to prevent circular dependencies when implementing the database interface.
|
Package iface exists to prevent circular dependencies when implementing the database interface. |
|
Package internal is a generated GoMock package.
|
Package internal is a generated GoMock package. |
|
Package node defines a validator client which connects to a full beacon node as part of the Ethereum Serenity specification.
|
Package node defines a validator client which connects to a full beacon node as part of the Ethereum Serenity specification. |