Regulatory compliance is not a constraint on the SWSS Chain model. It is a foundational design requirement built into the architecture from the first protocol decision.
SWSS Chain is designed to operate within, not in tension with, the legal and regulatory frameworks governing real-world asset settlement, financial services, and digital asset classification across its primary operating jurisdictions.
This section sets out the entities and licences under which the ecosystem operates, where its technology is built, how identity verification is governed, and the classification this document applies to SWSS Coin. It also describes how compliance is enforced by the protocol rather than administered above it, which is the part of the framework that is a property of the architecture rather than of a policy document. What it does not do is set out limits stated plainly at the end.
Regulatory Licencing
| Regulator / Framework | Entity | Scope |
|---|---|---|
| BVI Entity | SWSS FoundationBVIParent Company | Global headquarters, overseeing all international operations |
| FINTRAC Canada (MSB Licence) | SWSS FintechCanadaMSB Licence | AML compliance, KYC, payment processing, SWSS Pay operations |
| UK Entity | SWSS FintechUKSales & Operations | European market expansion, sales and client relationships |
| UAE Entity | SWSS FintechDubaiMiddle East Operations | Middle East operations and investor relations |
SWSS Chain Global Technology Centre — Malaysia
SWSS FoundationMalaysiaCore Development & R&D
The SWSS Chain Global Technology Centre is the primary research, development, and technology operations facility for the SWSS Chain protocol and every ecosystem product. All core protocol development — including SCP version advancement, DEED-1 Standard expansion, and SWSS AI OwlX v1 model development — is conducted within this facility. Malaysia was selected based on its established technology infrastructure, a regulatory environment supportive of blockchain and fintech innovation, and the availability of specialist technical talent required for settlement-layer protocol engineering at the level SWSS Chain demands.
KYC & AML Architecture
Identity verification for all SWSS ecosystem participants is conducted through providers admitted to the SWSS IVL Provider Registry — a Foundation-governed on-chain mechanism ensuring all identity verification meets compliance standards across SWSS Chain's operating jurisdictions. AML monitoring is conducted continuously across settlement activity on SWSS RWAX, which settles today, and applies to SWSS Pay from the point its payment operations open.
The registry is the structural part of this arrangement and is worth stating precisely, because it determines who is accountable. The Foundation admits the provider; the provider performs the verification; the credential issued against that verification is the Foundation's and is recorded on chain rather than held by the vendor that produced it. A verified institution therefore carries its status across every SWSS property, and that status outlives its relationship with any one provider — if a provider is later removed from the registry, credentials already issued through it remain valid and only new issuance from it stops. Verification is a Foundation-governed credential rather than a receipt from a supplier.
Compliance Enforced By The Protocol
swss compliance trace --settlement
Compliance here is enforced by the infrastructure rather than requested by a policy, and the difference is the third stage. A policy can be waived by whoever administers it. A protocol that cannot represent an unverified holder has nothing to waive.
Most settlement infrastructure treats compliance as something applied to a transaction after the network has processed it. On SWSS Chain the obligations that matter to a regulated counterparty are properties of the settlement itself, decided at or beneath the point where a transaction becomes final. That is a design claim rather than a legal one, and each part of it is established elsewhere in this document.
| Requirement | How the protocol answers it |
|---|---|
| Verified participation | Credentials issued through the Foundation-governed provider registry operate at the consensus layer rather than as an application check above it, so a participant's verified status is a property of the network and not of the interface they happen to be using. See the Identity Layer |
| Jurisdiction recorded, not attached | A DEED-1 settlement carries its jurisdiction code, legal owner and institutional signature as fields of the settlement record itself. They cannot be separated from the instrument later, because they were never a document alongside it |
| Evidence of settlement | The Finality Certificate is emitted by consensus at the block that settled the transaction. An application above consensus cannot certify what consensus has not finished deciding, which is why this is a genesis property rather than a feature |
| No discretionary ordering | Deterministic Sequencing Arbitration fixes transaction order mathematically before block production and immutably once the round concludes. Ordering cannot be influenced retroactively or purchased by fee, so fair sequencing is a protocol guarantee rather than a policy commitment |
| No replay of a proof | The on-chain nullifier registry records every proof spent. A proof of ownership or compliance cannot be presented twice, and that is structural rather than monitored. See ZK Settlement Privacy |
The practical consequence is that a counterparty assessing this infrastructure does not have to take the operator's word about controls. Each row above is observable on chain, and Ecosystem Performance sets out how an outside party verifies settlement activity without cooperation from SWSS.
Confidentiality And Compliance Together
Regulated participants are routinely asked to choose between demonstrating compliance and disclosing information they are constrained from disclosing. SWSS Chain does not require that trade, because a proof and a disclosure are different things. Through zero-knowledge settlement privacy, a party can establish that it holds valid identity verification, or that it owns a settled deed, without revealing who it is, which instrument it holds or what the asset is worth. What a successful verification confirms is that the claim is true and has not been presented before — and nothing else is disclosed.
Where a deed record itself must be read rather than proven, access is governed by the three-tier control described in the Identity Layer rather than by an all-or-nothing publication of the record. Institutional custody arrangements, confidentiality obligations to a client, and cross-border settlement where identity disclosure is legally constrained are the ordinary cases this exists for, and they are the cases a public ledger without these layers handles worst.
SWSS Coin Legal Classification
SWSS Coin is the native currency of SWSS Chain — a live, operational blockchain network. It is not a security. It does not represent ownership, profit rights, or a claim on any asset. It is the fuel that powers transactions on a running settlement infrastructure. Its classification as a utility coin is consistent with the legal frameworks of its primary operating jurisdictions. SWSS Coin holders should obtain independent legal advice regarding the classification applicable in their jurisdiction.
What This Section Does Not Claim
This section is not legal advice and does not purport to be. It describes the framework the ecosystem is designed to operate within, and it makes no representation about the treatment of any holding, transaction or asset in any particular jurisdiction. It offers no jurisdiction-by-jurisdiction analysis, no opinion on the tax position of any participant, and no assurance that a characterisation stated here will be the characterisation applied by a regulator or a court. Anyone relying on any of it should obtain independent legal advice in their own jurisdiction.
Nor does this section state a governing law. The entities above operate the ecosystem and the licences are theirs, but the law governing a particular instrument — a deed, a membership, a payment service — is stated in the documentation a member executes for it, and that documentation governs. A whitepaper naming one law for all of them would be describing a simpler structure than the one that exists, and a reader would be relying on the wrong document.
Nor does a licence in the table above extend beyond its stated scope. Each names the regulator or framework, the entity that holds it, and what it covers; nothing may be inferred from it about activity, jurisdiction or product outside that scope. And nothing in this document is an offer, a solicitation or a promise of return — Risk Factors sets out the risks that apply across the ecosystem, and it should be read alongside this section rather than after it.
Is SWSS Coin a security?