Tanssi audit reports

Tanssi has 1 public audit report from Pashov Audit Group; dated 13 May 2025; no critical findings reported.

Critical findings
No open critical findings
In 1 report.
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 firm14

Statuses are the security firms’ own

14 findings are still open or acknowledged in the firms’ reports: 4 medium, 10 low (all acknowledged).

Medium
4
Low
10
  • Medium Acknowledged

    _getRewardsAmountPerVault might be using an outdated vault power

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Medium Acknowledged

    Disabling collateral with setCollateralToOracle() blocks reward claims

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Medium Acknowledged

    getOperatorPowerAt uses current prices for past stake calculations

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Medium Acknowledged

    Operator key change might cause loss of access to unclaimed rewards

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    _beforeRegisterOperator allows invalid validator registration

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    adminFeeAmount always round down, resulting in reduced revenue for the admin

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    Middleware treats validators with very low active power as valid

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    Middleware::slash can revert due to VetoSlasher near epoch end

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    Missing validation for stale or invalid price data in Middleware::stakeToPower

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

  • Low Acknowledged

    Pending slashes are not taken into account

    Tanssi security review · Pashov Audit Group · 13 May 2025 · Report ↗

All 14 open and acknowledged findings

Audits1

Newest first

ReportSecurity firmDateScopeCritical findingsFindingsSource
Tanssi security reviewSecurity firm: Pashov Audit GroupDate: Scope: Not recorded; see the reportNone openFindings: 1 high · 6 medium · 17 low
10 fixed · 14 acknowledged
GitHub ↗

Findings24

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium042
Low0107

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.

Tanssi: questions

Is Tanssi audited?

Trustblock holds 1 public audit report for Tanssi, dated 13 May 2025. The latest is by Pashov Audit Group (“Tanssi security review”).

Who audited Tanssi?

Pashov Audit Group wrote the report Trustblock holds for Tanssi.

Are there open findings in Tanssi’s audits?

14 findings are still open or acknowledged in the firms’ reports: 4 medium, 10 low (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="tanssi"
></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