mirror of
https://gitlab.com/pulsechaincom/prysm-pulse.git
synced 2025-01-12 04:30:04 +00:00
06db5f6471
* Look into what makes the validator client slow * Comment * Refactor status function to be cleaner * Use timings from params * Improve coverage * Remove unneeded lock in chainstart * Reorganize validator logging * Merge branch 'master' of https://github.com/prysmaticlabs/prysm into optimize-validator * cleanup * Fix bug * Undo depositbypukey changes * Merge branch 'master' of https://github.com/prysmaticlabs/prysm into optimize-validator * Fix deposit cache * Fix multiple status test * Merge branch 'master' of https://github.com/prysmaticlabs/prysm into optimize-validator * Remove logs * Remove unused import * Add comment * comment * Remove comments * Merge branch 'master' into optimize-validator * Undo time change for activation * Merge branch 'optimize-validator' of https://github.com/0xKiwi/Prysm into optimize-validator * Fix check for sync * Change value back to half slot * comment * Rephrase logs * Merge branch 'master' into optimize-validator |
||
---|---|---|
.. | ||
accounts | ||
client | ||
db | ||
flags | ||
internal | ||
keymanager | ||
node | ||
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.