Skip to content

Audits

Independent security reviews of the Nexwest protocol, the scope of each engagement, and the status of remediated findings.

Updated Nov 4, 2026Everyone1 min read
On this page

Nexwest has been reviewed by independent security firms across the consensus client, the execution engine, and the bridge contracts. Audit reports are published in full; findings are tracked to remediation.

Engagements

FirmScopeDateStatus
Trail of BitsExecution engine, margin, liquidationQ2 2026Complete
ZellicConsensus client and networkingQ3 2026Complete
OtterSecBridge and EVM precompilesQ3 2026Complete
SpearbitPortfolio margin and vaultsQ4 2026In progress

What was reviewed

  • Order matching and price-time priority.
  • Margin, funding, and liquidation formulas.
  • Cross-margin and portfolio-margin accounting.
  • Vault share issuance, profit share, and withdrawal queues.
  • EVM precompiles and the CoreWriter system contract.
  • Validator key management and slashing conditions.

Audits are not a guarantee

An audit reduces risk; it does not eliminate it. Read the scope and the open findings before depositing capital. The protocol is upgradable through governance, so code reviewed today can change tomorrow.

Findings

All critical and high findings from completed engagements have been remediated and verified. Medium findings are either fixed or documented as accepted risk. The public tracker lists:

  • the finding,
  • the severity,
  • the affected component,
  • the remediation commit,
  • the verification status.

Bug bounty

Security researchers can report issues through the bug bounty program. Do not disclose a vulnerability publicly before a fix is deployed.

Was this page helpful?