Saphyre RFQ Settlement

PaladinCode version: not recorded (see the report)

Paladin reviewed Saphyre (Saphyre RFQ Settlement) on 29 Apr 2026: no findings reported.

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

Report hosted on paladinsec.co.

Trustblock does not review code.

Findings6

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

SeverityOpenAcknowledgedFixed
Critical000
High000
Medium000
Low000

Marked INFORMATIONAL by the firm. Not counted as findings.

INFORMATIONALDeflationary or debasing tokens are not supported by settlement accountingAcknowledged

The report gives no description here.

INFORMATIONALFee parameter is relayer-supplied and not signer-committedAcknowledged

The report gives no description here.

INFORMATIONALFee rounding can produce zero effective fee on small notionalsAcknowledged

The report gives no description here.

INFORMATIONALrescueTokens is permissionless and allows public donation sweepingAcknowledged

The report gives no description here.

INFORMATIONALFee cap constant is not centralized with protocol constantsFixed

The report gives no description here.

INFORMATIONALSetfeetreasury does not emit an eventFixed

The report gives no description here.

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.

Part of Saphyre’s security record

Saphyre
Audits1 audit by 1 firmLast audit Apr 2026, by Paladin.
Critical findingsNo open critical findingsIn 1 report.
Open Saphyre’s security record

Security firm

Paladin

201 projects reviewed · 277 reports · latest Apr 2026

See Paladin’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