README
¶
Prysmatic Labs Validator Client Implementation
This is the main project folder for a validator client implementation of Ethereum written in Go by Prysmatic Labs. A validator client attaches to a running beacon node in order to perform proposer/attester responsibilities for eth.
You can also read our main README and join our active chat room on Discord.
To further understand the responsibilities of an Ethereum validator, we recommend reading the official specification here
Directories
¶
| Path | Synopsis |
|---|---|
|
Package accounts defines a new model for accounts management in Prysm, using best practices for user security, UX, and extensibility via different wallet types including HD wallets, imported (non-HD) wallets, and remote-signing capable configurations.
|
Package accounts defines a new model for accounts management in Prysm, using best practices for user security, UX, and extensibility via different wallet types including HD wallets, imported (non-HD) wallets, and remote-signing capable configurations. |
|
Package client represents a gRPC polling-based implementation of an Ethereum validator client.
|
Package client represents a gRPC polling-based implementation of an Ethereum validator client. |
|
beacon-api/mock
Package mock is a generated GoMock package.
|
Package mock is a generated GoMock package. |
|
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. |
|
local
Package local defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm.
|
Package local defines an implementation of an on-disk, EIP-2335 keystore.json approach towards defining validator accounts in Prysm. |
|
remote-web3signer/v1
Package v1 defines mappings of types as defined by the web3signer official specification for its v1 version i.e.
|
Package v1 defines mappings of types as defined by the web3signer official specification for its v1 version i.e. |
|
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. |
|
Package history defines methods to parse, import, and export slashing protection data from a standard JSON file according to EIP-3076 https://eips.ethereum.org/EIPS/eip-3076.
|
Package history defines methods to parse, import, and export slashing protection data from a standard JSON file according to EIP-3076 https://eips.ethereum.org/EIPS/eip-3076. |
|
Package web is the service to serve the Prysm web UI.
|
Package web is the service to serve the Prysm web UI. |
Click to show internal directories.
Click to hide internal directories.