Wayfinder security record
As of 3 Nov 2026, Wayfinder has 2 audit reports by 1 security firm on Trustblock; the latest is by Quantstamp, dated 21 Mar 2025. Those reports list no open critical findings.
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
| Audit | Security firm | Date | Scope | Critical findings | Report |
|---|---|---|---|---|---|
| Wayfinder Prompt Claims | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
| Wayfinder | Security firm: Quantstamp | Date: | Scope: Files named in the report | No open critical findings | Open · certificate.quantstamp.com |
Findings7
Statuses are the security firm’s own, from each report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 1 | 1 | 5 |
Low`lockDuration` Can Be Extended Beyond the `MAX_LOCK_DURATION`Wayfinder · Quantstamp · 29 May 2024Fixed
In `handleInvokeEchelon()`, the lock duration check (shown below) may be inaccurate if the `MAX_LOCK_TIMESTAMP` is set to some time far in the future. ``` if ( lockDuration != type(uint256).max && lockDuration > MAX_LOCK_DURATION && lockDuration + block.timestamp > MAX_LOCK_TIMESTAMP ) { revert("Lock duration must be less than 1095 days"); } ``` In particular, the last two conditions `lockDuration > MAX_LOCK_DURATION && lockDuration + block.timestamp > MAX_LOCK_TIMESTAMP` implies that `lockDuration` can be larger than `MAX_LOCK_DURATION` as long as `lockDuration + block.timestamp` is less than `MAX_LOCK_TIMESTAMP`. This means as long as `MAX_LOCK_TIMESTAMP` is far into the future, say `10 years` ahead, then having a `lockDuration` of `5 years` will still pass this check, contradicting the revert statement `revert("Lock duration must be less than 1095 days");` A similar issue exists in `extendDeposit()`.
Open the reportLowFunction Visibility OptimizationWayfinder · Quantstamp · 29 May 2024Fixed
The `handleInvokeEchelon()` function is marked as `public`, but it is only intended to be called by the `primeToken` contract.
Open the reportLowLack of SafeERC20 UsageWayfinder · Quantstamp · 29 May 2024Fixed
The `withdrawDeposits()` function directly transfers `PRIME` tokens using `primeToken.transfer()`, which does not provide any safety checks and could lead to unexpected behavior if the token contract is not compliant with the ERC20 standard.
Open the reportLowPotential Denial of Service and Gas OptimizationWayfinder · Quantstamp · 29 May 2024Fixed
The `withdrawDeposits()` function transfers `PRIME` tokens within a loop, which could lead to high gas consumption and potentially cause a denial of service if there are a large number of deposits to withdraw.
Open the reportLowUnnecessary ImportWayfinder · Quantstamp · 29 May 2024Fixed
The contract imports `Ownable2Step` and `Ownable` from OpenZeppelin, but they are not being used in the contract.
Open the reportContracts
No deployed address is recorded for these audits.
The reports name a repository or files. Open a report to see its scope.
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
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.
Style
Format
<head><script src="https://widget.trustblock.run/project-widget.min.js" defer></script></head><body><divdata-tb-project-widgetdata-tb-project-slug="wayfinder"></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