Quantstamp reviewed Prysm on 13 Oct 2020: 35 findings, 0 critical; 25 marked fixed, 7 acknowledged, 3 open; 1 more marked mitigated.
Report hosted on certificate.quantstamp.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed | Mitigated |
|---|---|---|---|---|
| Critical | 0 | 0 | 0 | 0 |
| High | 0 | 1 | 3 | 0 |
| Medium | 0 | 3 | 9 | 0 |
| Low | 3 | 3 | 13 | 1 |
Upon start, beacon-node does not check if minimal system requirements are met. Validators may not be aware of system requirements; if many validators face the same issue, the whole network may not perform as expected.
According to the specification _in case of an invalid input, a reader MUST:_ * _From responses: ignore the response, the response MUST be considered bad server behavior._ The number of bad responses is incremented for all topics with the exception of the `Goodbye` topic, whose handlers are in `beacon-chain/sync/rpc_goodbye.go`
When the beacon node removes data in the database (e.g., when pruning garbage state), the corresponding space in disk is not freed, as BoltDB does NOT perform any clean-up.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
240 projects reviewed · 338 reports · latest Nov 2026
See Quantstamp’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us