Privacy Pools audit reports

Privacy Pools has 2 public audit reports from OXORIO; the latest is OXORIO, 18 May 2025; no critical findings reported.

Critical findings
No open critical findings
Across 2 reports.
Open the latest report
Your label, live
Get the label for your site

Last updated . It holds audits and findings, contracts and incidents up to Nov 2026. Trustblock does not review code.

Open findings across every firm10

Statuses are the security firms’ own

10 findings are still open or acknowledged in the firms’ reports: 1 high, 9 medium (all acknowledged).

High
1
Medium
9
  • High Acknowledged

    No option to withdraw privately in an edge case in PrivacyPool

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Potential nullifier reuse vulnerability in precommitment tracking in EntryPoint

    Privacy Pools smart contracts · OXORIO · 18 May 2025 · Report ↗

  • Medium Acknowledged

    Deposit fee can be unexpected in Entrypoint

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Missing check that processooor is not equal to depositor in PrivacyPool

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Missing minimum amount for withdrawals in PrivacyPool

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Missing validation for postman and owner in Entrypoint

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Only the latest ASP root is used for ASP inclusion proof verification in PrivacyPool

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Potential deanonymization in PrivacyPool

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Shared ASP tree across all pools in Entrypoint

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

  • Medium Acknowledged

    Token decimals not considered in fee calculation in Entrypoint

    Privacy Pools smart contracts · OXORIO · 18 Mar 2025 · Report ↗

Audits2

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Privacy Pools smart contractsSecurity firm: OXORIODate: Scope: Not recorded; see the reportNone openFindings: 1 medium
1 acknowledged
oxor-io.github.io ↗
Privacy Pools smart contractsSecurity firm: OXORIODate: Scope: Not recorded; see the reportNone openFindings: 2 high · 11 medium
4 fixed · 9 acknowledged
oxor-io.github.io ↗

Findings20

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

SeverityOpenAcknowledgedFixed
Critical000
High011
Medium093
Low000

No open finding in these reports.

Contracts

No deployed address is recorded for these audits.

The reports name a repository or files. Open a report to see its scope.

Privacy Pools: questions

Is Privacy Pools audited?

Trustblock holds 2 public audit reports for Privacy Pools, dated 18 Mar 2025 to 18 May 2025. The latest is by OXORIO (“Privacy Pools smart contracts”).

Who audited Privacy Pools?

OXORIO wrote the 2 reports Trustblock holds for Privacy Pools.

Are there open findings in Privacy Pools’s audits?

10 findings are still open or acknowledged in the firms’ reports: 1 high, 9 medium (all acknowledged). No critical finding is reported. Statuses are the security firms’ own.

Show this on your site

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.

Content

Facts

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.

Fixed as
Language

Style

Layout
Theme
Accent
Corners

Format

Size
Date
Embed as
HTML
<head>
<script src="https://widget.trustblock.run/project-widget.min.js" defer></script>
</head>
<body>
<div
data-tb-project-widget
data-tb-project-slug="privacy-pools"
></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