mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2025-01-12 04:30:04 +00:00
acf201428e
* Use new proposal protection format * Update comments * Split and merge with new db * fix tests * fix test * optimize domain * fix validation * fix validation * check import error * fix e2e * fix old propose tests add ign block test * constant secret key * static test for signing * test domain * fix testsplit * gaz * gaz * tidy * raul feedback * fix tests * tidy * added info log for the migration * gaz * Update validator/client/propose_protect.go Co-authored-by: Nishant Das <nishdas93@gmail.com> * nishant feedback * import fix * fix * remove propose protection flag * fix block sign test Co-authored-by: Nishant Das <nishdas93@gmail.com> Co-authored-by: prylabs-bulldozer[bot] <58059840+prylabs-bulldozer[bot]@users.noreply.github.com> |
||
---|---|---|
.. | ||
accounts/v2 | ||
client | ||
db | ||
flags | ||
keymanager/v2 | ||
node | ||
rpc | ||
slashing-protection | ||
testing | ||
web | ||
BUILD.bazel | ||
main.go | ||
README.md | ||
usage_test.go | ||
usage.go |
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.