The highest tagged major version is
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 ¶
Package main defines a validator client, a critical actor in eth2 which manages a keystore of private keys, connects to a beacon node to receive assignments, and submits blocks/attestations as needed.
This code was adapted from https://github.com/ethereum/go-ethereum/blob/master/cmd/geth/usage.go
Source Files
Directories
¶
| Path | Synopsis |
|---|---|
|
accounts
|
|
|
v1
Package accounts defines tools to manage an encrypted validator keystore.
|
Package accounts defines tools to manage an encrypted validator keystore. |
|
v2
Package v2 defines a new model for accounts management in Prysm, using best practices for user security, UX, and extensibility via different wallet types including derived, HD wallets and remote-signing capable configurations.
|
Package v2 defines a new model for accounts management in Prysm, using best practices for user security, UX, and extensibility via different wallet types including derived, HD wallets and remote-signing capable configurations. |
|
Package client represents a gRPC polling-based implementation of an eth2 validator client.
|
Package client represents a gRPC polling-based implementation of an eth2 validator client. |
|
iface
Package iface defines an interface for the validator database.
|
Package iface defines an interface for the validator database. |
|
kv
Package kv defines a persistent backend for the validator service.
|
Package kv defines a persistent backend for the validator service. |
|
Package flags contains all configuration runtime flags for the validator service.
|
Package flags contains all configuration runtime flags for the validator service. |
|
keymanager
|
|
|
v2/direct
Package direct defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm.
|
Package direct defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm. |
|
v2/remote
Package remote defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm.
|
Package remote defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm. |
|
Package node is the main process which handles the lifecycle of the runtime services in a validator client process, gracefully shutting everything down upon close.
|
Package node is the main process which handles the lifecycle of the runtime services in a validator client process, gracefully shutting everything down upon close. |