mirror of https://github.com/OffchainLabs/prysm.git synced 2026-05-02 03:02:54 -04:00

Files

terence tsao 7588e491ab Add overflow check for StartSlot (#7149 )

* Add overflow checks
* More fixes
* Typos
* Merge branch 'master' into fix-overflow
* One more regression test
* Merge branch 'fix-overflow' of github.com:prysmaticlabs/prysm into fix-overflow
* Gazelle
* Merge branch 'master' into fix-overflow
* Nishant's feedback
* Merge refs/heads/master into fix-overflow

2020-09-02 02:52:36 +00:00

accounts

Fixes incorrect output produced by the ListAccounts function (#6976 ) (#7095 )

2020-09-01 13:13:44 -05:00

client

Add overflow check for StartSlot (#7149 )

2020-09-02 02:52:36 +00:00

Begin Dynamic Rescan of Validating Keys (#6963 )

2020-08-31 23:38:20 +00:00

flags

Create Validator Accounts V2 Send Deposit (#7080 )

2020-08-24 19:19:21 +00:00

keymanager

Fixes incorrect output produced by the ListAccounts function (#6976 ) (#7095 )

2020-09-01 13:13:44 -05:00

node

Begin Dynamic Rescan of Validating Keys (#6963 )

2020-08-31 23:38:20 +00:00

rpc

Apply testutils assertions: final cleanup (#7003 )

2020-08-25 15:23:06 +00:00

slashing-protection

Update fastssz: Attempt 2 (#7115 )

2020-08-27 18:13:32 +00:00

testing

Make external slasher protection fail on load if slasher is not reachable (#6704 )

2020-07-27 20:06:49 +00:00

BUILD.bazel

Begin Dynamic Rescan of Validating Keys (#6963 )

2020-08-31 23:38:20 +00:00

main.go

Begin Dynamic Rescan of Validating Keys (#6963 )

2020-08-31 23:38:20 +00:00

README.md

Updated why-combining-sharding-and-casper link in validator/README.md (#3810 )

2019-10-20 19:43:30 -07:00

usage_test.go

Refactor dependencies, make Prysm "go gettable" (#6053 )

2020-05-31 14:44:34 +08:00

usage.go

Integrate Validator RPC Server Into Runtime + Add Gateway (#6994 )

2020-08-13 19:49:57 -07:00

README.md

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.