31Third security record

Ethereum, Optimism, Polygon (POS)31third.com

As of 3 Nov 2026, 31Third has 2 audit reports by 1 security firm on Trustblock; the latest is by Quantstamp, dated 4 Apr 2024. Those reports list no open critical findings.

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

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

Audits2

Newest first

AuditSecurity firmDateScopeCritical findingsReport
31Third - Diff - UpdateSecurity firm: QuantstampDate: Scope: Files named in the reportNo open critical findingsOpen · certificate.quantstamp.com
31ThirdSecurity firm: QuantstampDate: Scope: Files named in the reportNo open critical findingsOpen · certificate.quantstamp.com

Findings18

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

SeverityOpenAcknowledgedFixed
Critical000
High001
Medium002
Low258
LowMissing Input Validation31Third · Quantstamp · 1 Mar 2023Open

It is vital to validate inputs to avoid human error, even if they only come from trusted addresses. The following functions do not have a proper validation of input parameters: 1. qs-badge-fixed `BatchTrade.batchTrade()` accepts trades with the same asset in `from` and `to` fields. 2. qs-badge-fixed `ExchangeAdapterRegistry.addAdapter()` should check that `name` is not an empty string. 3. qs-badge-mitigated Fees are calculated with a constant denominator of `10000`, however, the assignment of `maxFeeBasisPoints` does not consider this constant denominator when it is being assigned. This could lead to a scenario where `maxFeeBasisPoints` either meets or exceeds `10000`. 4. qs-badge-fixed `updateFeeRecipient()` and `updateBasisPoints()` do not check that the new value being assigned is actually different than the existing one. This could lead to unnecessary transaction costs.

Open the report
LowUntraceable Contract Events31Third · Quantstamp · 1 Mar 2023Open

Events should be emitted when the contract state changes. The following functions in `BatchTrade` do not emit events: - `updateFeeRecipient()` - `updateBasisPoints()` - `reduceMaxBasisPoints()` - `addFeelessWallet()` - `removeFeelessWallet()` - `receiveFees()`

Open the report

Contracts

No deployed address is recorded for these audits.

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

The repositories and files the reports name

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="31third-1"
></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