Security
Independent Assurance
Pre-launch
Section
Security
Documentation category
Type
Guide
Technical reference
Summary
The principles governing external audit and formal verification of SwssChain components, and what is published when an engagement concludes.
SWSS Foundation Notice

This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.

All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.

Join SWSS DevHub →Have a question? Use the Need Help? button below.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content

Internal review establishes that a system behaves as its authors intended. It cannot establish that the authors' intent was itself sound, because the same assumptions produced both. SwssChain therefore subjects its protocol implementation and its first-party contracts to assurance performed by parties who did not build them.

Principles of the Assurance Programme

PrincipleWhat it commits SWSS to
More than one reviewerComponents that bind settlement receive review from more than one independent party. Two firms share fewer blind spots than one, and the second engagement exists to find what the first could not see
Findings published in fullReports are published complete, including findings of every severity. Redaction is limited to material that would function as an exploit guide for a system not yet remediated
Remediation verified by the finderHigh and Critical findings are re-examined by the party that raised them after remediation, to confirm the fix is effective and introduces nothing new. A fix asserted by the team that wrote it is not a closed finding
Assurance is continuousAn audit is a statement about a version, not about a system. Material change to an audited component triggers further review scoped to what changed
Formal proof where testing cannot reachConsensus rules and certificate verification are formally verified. Testing demonstrates behaviour on the inputs tried; proof establishes behaviour on every input possible

Publication

A completed report is published once the remediation it describes has been confirmed, together with the formal verification outputs produced alongside it. Publishing a finding before its fix is deployed would convert an assurance document into an attack description, which is why publication follows remediation rather than completion.

The Boundary of This Programme

Assurance covers first-party SWSS components: the consensus client, the Settlement Consensus Protocol implementation, and the contracts through which SwssChain settles. It does not extend to contracts deployed by other parties, and no assurance stated here should be read as covering them. Institutions building significant systems on SwssChain are expected to commission their own review, and this is a condition of admission rather than a suggestion: see Developer Obligations.

Weaknesses found outside a formal engagement are handled through the disclosure programme in Reporting Vulnerabilities.