Skip to content
Quantix Security Labs

Security Assessments

Technical security assessments of protocols covered by Quantix Protocol Research. Each one documents the architecture and trust assumptions, the threat model, every finding with its exploit scenario and fix, and the remediation state at a stated commit. Completed assessments are published as Technical Security Assessment documents you can download. They are Quantix research assessments, not client engagements or certifications.
Illustration: a technical assessment report with a severity distribution and findings table, beside the in-scope contracts inside a brass scope frame.
Assessments
12
Published documents
9
Findings documented
90
Ecosystems covered
10
Overall remediation
87%

Catalogue

All assessments

Search across protocols, document IDs, finding titles and vulnerability classes. Filters combine; the quick view summarises an assessment without leaving the catalogue.

12 assessments · page 1 of 2

  • Arbalest Bridge

    QX-TSA-2026-005 · v0.9

    Under Review

    Bridge Security Assessment · Bridge

    Architecture: BridgeGateway · MessageReceiver · ValidatorSet · TokenVault · WrappedToken · +3

    Ecosystem
    EthereumBaseArbitrum
    Language
    Solidity
    Scope
    6 items · 1,408 nSLOC
    Review ended

    8findings

    Remediation69% · 3 open
    Read assessment of Arbalest Bridge
  • Fenwick Lending

    QX-TSA-2026-002 · v1.1

    Published

    Formal Verification · Lending

    Architecture: MarketCore · InterestRateModel · LiquidationEngine · ReserveManager · OracleRouter · +2

    Ecosystem
    Arbitrum
    Language
    Solidity
    Scope
    5 items · 996 nSLOC
    Published

    5findings

    Remediation100% · no open items
  • Northstar Custody

    QX-TSA-2026-011 · v1.1

    Published

    Infrastructure Security Review · Custody

    Architecture: MPC signing nodes · Policy engine · Signing coordinator · Client API · Approvals console · +2

    Ecosystem
    EthereumSolana
    Language
    Rust, Go, TypeScript
    Scope
    5 items · 13,930 nSLOC
    Published

    8findings

    Remediation100% · no open items
  • Merivale Markets

    QX-TSA-2026-010 · v0.9

    Under Review

    Smart Contract Audit · DEX

    Architecture: OrderBook · Router · FeeController · ListingManager · Operator key · +2

    Ecosystem
    BNB Chain
    Language
    Solidity
    Scope
    5 items · 2,104 nSLOC
    Review ended

    8findings

    Remediation63% · 4 open
    Read assessment of Merivale Markets
  • Larkspur Wallet SDK

    QX-TSA-2026-004 · v1.1

    Published

    Penetration Test · Wallet Infrastructure

    Architecture: Signing SDK · Wallet connector · Pairing relay · Chain registry · Integrating dApp page · +2

    Ecosystem
    Cosmos
    Language
    TypeScript, Go
    Scope
    4 items · 7,420 nSLOC
    Published

    7findings

    Remediation100% · no open items
  • Axeline Bridge

    QX-TSA-2026-012 · v0.8

    Under Review

    Bridge Security Assessment · Interoperability

    Architecture: Endpoint · VerifierRegistry · AttestationVerifier · Executor · Attesters · +2

    Ecosystem
    OptimismAvalancheArbitrum
    Language
    Solidity
    Scope
    6 items · 2,386 nSLOC
    Review ended

    8findings

    Remediation63% · 4 open
    Read assessment of Axeline Bridge

Workspace

Assessment workspace

Follow one assessment through its seven stages, see how its findings break down by severity and remediation status, and export the findings table as CSV.

Arbalest Bridge

QX-TSA-2026-005 · v0.9 · d9e6c02925a9

Under ReviewBridge Security Assessment

Assessment stages

5 of 7 complete · review 21 Sept 2026 – 6 Oct 2026

  1. Stage 1, complete:21 Sept 2026ScopingRepository, commit and in-scope files agreed.
  2. Stage 2, complete:CompleteArchitecture reviewComponents, trust levels and assumptions mapped.
  3. Stage 3, complete:CompleteThreat modellingAssets, actors and threats enumerated.
  4. Stage 4, complete:6 Oct 2026Review and testingManual review, tooling, fuzzing and verification.
  5. Stage 5, complete:6 Oct 2026ReportingFindings written with exploit scenarios and fixes.
  6. 6Stage 6, in progress:In progressRemediation reviewFix commit reviewed finding by finding.
  7. 7Stage 7, not started:PendingPublicationTechnical Security Assessment document generated.

Findings by severity

8findings

Remediation by severity

69% remediated · 3 open or partial

ResolvedPartially resolvedAcknowledgedOpen
0123CriticalHighMediumLowInformational
Arbalest Bridge findings by severity and remediation status
CategoryResolvedPartially resolvedAcknowledgedOpen
Critical1000
High1100
Medium0012
Low1000
Informational1000

8 of 8 findings shown

Findings of Arbalest Bridge
IDFindingSeverityL / IStatus
AB-01Duplicate signatures are counted towards the thresholdBridge message validation · CWE-347CriticalH / HResolved
AB-02Message digest omits destination chain and receiver contractSignature replay · CWE-294HighM / HResolved
AB-03Signed validator-set updates can be replayed after rotationSignature replay · CWE-294HighM / HPartially resolved
AB-04Vault accounting assumes the full amount arrivesBusiness logic · CWE-682MediumM / MOpen
AB-05Fixed-window rate limiter allows double the cap at window boundariesBusiness logicMediumL / HAcknowledged
AB-06Signature recovery accepts malleable signaturesCryptography · CWE-347LowL / LResolved
AB-07Pause and unpause emit no eventsCode qualityInformationalL / LResolved
AB-08Validator rotation takes effect immediatelyGovernance manipulationMediumL / HOpen

Reading an assessment

An assessment covers one commit. It is evidence about that code under stated assumptions, not a statement that a protocol is secure.

  1. 01Compare the commit. Check the reviewed and remediation commits against the code you are actually integrating.
  2. 02Read status, not counts. A resolved critical finding and an open medium one carry different residual risk. The remediation analysis shows both.
  3. 03Check the trust assumptions. The architecture section lists what the review assumed to be trusted. Anything outside it was not tested.

Commission an assessment you can publish.

Every Quantix assessment is written to be checked: scope, method, findings, fixes and limitations, with commit references anyone can compare.