Most settlement infrastructure treats compliance as something applied to a transaction after the network has processed it. On SwssChain the obligations that matter to a regulated counterparty are properties of the settlement itself, decided at or beneath the point a transaction becomes final.
This page is technical, not legal
It describes what the protocol does. Regulatory licensing, the operating entities, jurisdictions and the classification of SWSS Coin are set out in the SwssChain Whitepaper: Legal & Regulatory Framework, which is authoritative. Nothing here modifies it, and nothing here is legal advice.
What the Protocol Enforces
| Requirement | How the protocol answers it |
| Verified participation | Credentials issued through the Foundation-governed IVL Provider Registry operate at the consensus layer, so a participant's verified status is a property of the network rather than of the interface they are using. See SWSS Identity Verification Layer |
| Jurisdiction recorded, not attached | A DEED-1 settlement carries its jurisdiction code, legal owner and institutional signature as fields of the settlement record. 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 |
| No discretionary ordering | Deterministic Sequencing Arbitration fixes transaction order before block production and immutably once the round concludes, so fair sequencing is a protocol guarantee rather than a policy commitment. See DSA |
| Accountable admission | Validators and developers are admitted after KYB and SWSS Foundation approval, so every signer and every integrator is a legally identified entity. See Developer and Validator Access |
The Provider Registry, and Who Is Accountable
Identity verification is performed by providers admitted to the Foundation-governed IVL Provider Registry. The structure determines accountability, and it is worth stating precisely: 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.
Two consequences follow for an integrator. A verified institution carries its status across every SWSS property rather than re-verifying per product. And if a provider is later removed from the registry, credentials already issued through it remain valid: only new issuance from that provider stops. Verification is a Foundation-governed credential, not a receipt from a supplier.
What This Does Not Cover
The protocol enforces the properties above. It does not discharge an integrator's own obligations: licensing in the jurisdictions you operate in, your own AML programme where one is required of you, your customers' onboarding, and your handling of the credentials issued to you. See Developer Obligations.
Next Steps