Prysm

QuantstampFiles named in the report

Quantstamp reviewed Prysm on 13 Oct 2020: 35 findings, 0 critical; 25 marked fixed, 7 acknowledged, 3 open; 1 more marked mitigated.

No open critical findings
Open the reportOpen Prysm’s security record

Report hosted on certificate.quantstamp.com.

Trustblock does not review code.

Findings58

Statuses are the security firm’s own, from its report.

SeverityOpenAcknowledgedFixedMitigated
Critical0000
High0130
Medium0390
Low33131
LowMinimal system requirementsOpen

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.

LowNumber of bad responses is not incremented in the `Goodbye` topicOpen

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`

LowRunning out of disk spaceOpen

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.

Contracts in scope

No deployed address is recorded for this audit.

The report names a repository or files. Open the report to see its scope.

Repository and files the report names (1)

  • contracts/deposit/*

Part of Prysm’s security record

Prysm
Audits1 audit by 1 firmLast audit Oct 2020, by Quantstamp.
Critical findingsNo open critical findingsIn 1 report.
Open Prysm’s security record

Security firm

Quantstamp

240 projects reviewed · 338 reports · latest Nov 2026

See Quantstamp’s audits

Something 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