P2P.org has 5 public audit reports from MixBytes; the latest is MixBytes, 21 May 2026; 2 critical findings, all marked fixed by the firms.
Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.
Statuses are the security firms’ own
13 findings are still open or acknowledged in the firms’ reports: 2 high, 4 medium, 7 low (all acknowledged).
referrer and service can receive less rewards than expected in some cases
P2P · MixBytes · 2 Jul 2024 · Report ↗
s_clientOnlyClRewards can potentially exceed the amountInGwei value from Oracle , leading to DoS of withdraw and recoverEther
P2P · MixBytes · 2 Jul 2024 · Report ↗
Signature Replay Allows Unauthorized Use of Permits
P2P.org · MixBytes · 24 Jan 2025 · Report ↗
A user can call the voluntaryExit function with invalid/non-existent validator pubkeys
P2P · MixBytes · 2 Jul 2024 · Report ↗
Poisoned feeDistributor can lock or steal service rewards
P2P · MixBytes · 2 Jul 2024 · Report ↗
voluntaryExit shouldn't be public
P2P · MixBytes · 2 Jul 2024 · Report ↗
Duplicate Pubkeys In A Batch Can Top Up The Same Validator
P2P.org · MixBytes · 21 May 2026 · Report ↗
Custom require errors are supported by Solidity since version 0.8.26
P2P.org · MixBytes · 19 Mar 2026 · Report ↗
Mitigating error risks in setting SsvToken exchange rate
P2P.org · MixBytes · 19 Mar 2026 · Report ↗
Centralization Risks
P2P.org · MixBytes · 24 Jan 2025 · Report ↗
Newest first
| Report | Security firm | Date | Scope | Critical findings | Findings | Source |
|---|---|---|---|---|---|---|
| P2P.org | Security firm: MixBytes | Date: | Scope: —Not recorded; see the report | None open | Findings: 6 low 5 fixed · 1 acknowledged | GitHub ↗ |
| P2P.org | Security firm: MixBytes | Date: | Scope: —Not recorded; see the report | None open | Findings: 1 high · 1 medium · 14 low 14 fixed · 2 acknowledged | GitHub ↗ |
| P2P.org | Security firm: MixBytes | Date: | Scope: —Not recorded; see the report | None open | Findings: 1 high · 5 medium · 3 low 9 fixed | GitHub ↗ |
| P2P.org | Security firm: MixBytes | Date: | Scope: —Not recorded; see the report | None open | Findings: 1 high · 4 medium · 5 low 7 fixed · 3 acknowledged | GitHub ↗ |
| P2P | Security firm: MixBytes | Date: | Scope: —Not recorded; see the report | 2 critical findings, fixed | Findings: 2 critical · 6 high · 14 medium · 9 low 24 fixed · 7 acknowledged | GitHub ↗ |
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 2 |
| High | 0 | 2 | 7 |
| Medium | 0 | 4 | 20 |
| Low | 0 | 7 | 30 |
The reports name a repository or files. Open a report to see its scope.
Trustblock holds 5 public audit reports for P2P.org, dated 2 Jul 2024 to 21 May 2026. The latest is by MixBytes (“P2P.org”).
MixBytes wrote the 5 reports Trustblock holds for P2P.org.
13 findings are still open or acknowledged in the firms’ reports: 2 high, 4 medium, 7 low (all acknowledged). Of 2 critical findings: all marked fixed by the firms. Statuses are the security firms’ own.
Is this your project? Show this record on your own website. The label states what the record holds, links to this page and updates by itself. It is free and needs no sign-in.
Automatic: the three strongest facts of this project’s own record (its last audit and two more), highlighted. They update with the record. Picking a fact turns Automatic off.
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="p2porg"></div></body>
Paste the code where the label should appear. It uses no API credit and updates by itself.
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