SWSS Chain is not a roadmap. It is a running settlement layer, live on two networks, settling real-world assets today under a protocol built for the purpose.
The real-world asset economy is not emerging. It is already the largest pool of transferable value in human economic history, and what is emerging is the infrastructure adequate to serve it. The transition from paper-based, jurisdiction-locked, intermediary-dependent title processes to cryptographically certain, globally accessible, permanently recorded settlement is under way, and the infrastructure that serves it has to be adequate to the demands the market will place on it as it scales — not to the demands of the day it launched.
SWSS Chain was specified in 2019 for exactly that economy: not for the version of it that existed then, and not only for the one that exists now. Every decision described in this document — a settlement standard at the consensus layer, a certificate of finality produced by consensus itself, identity and privacy as protocol functions rather than applications — was taken because a settlement layer that acquires those properties later is a different settlement layer.
The Finality Certificates produced today will be as valid in 2050 as they are now. That permanence is not a technical feature; it is the design philosophy the whole architecture serves. The most valuable thing a settlement infrastructure can offer is irreversibility — the assurance that what has been recorded will remain recorded, and that what has been settled will remain settled.
The SWSS ecosystem is not a collection of separate products that share a blockchain. It is one settlement economy expressing itself through distinct market verticals — real estate, compute, artificial intelligence, payments, gaming, travel, decentralised finance, and each further class in the Expanding Deed Registry. The settlement layer is the gravity centre. The products orbit it, and every one of them settles through the same four layers beneath it.
What Has Already Been Established
A claim to have pioneered something is worth what it can be checked against, so this section states what is built and running rather than what is intended. Each item below operates on SwssChain mainnet 122605 and testnet 122606 today, and each is observable by a party that trusts nothing in this document.
| Established | What it means for real-world asset settlement |
|---|---|
| A settlement standard at the consensus layer | DEED-1 is a native transaction class rather than a contract convention, carrying the deed identifier, asset reference, legal owner, jurisdiction code and institutional signature as fields of the settlement itself. The instrument and its legal context cannot be separated afterwards, because they were never separate |
| A certificate of finality produced by consensus | The Finality Certificate is emitted by SCP at the block that settles the transaction, which is what allows a settlement to be cited as a legal event rather than reported as a record |
| Identity as a protocol function | SWSS IVL credentials and a Foundation-governed provider registry operate at the consensus layer, so verified status is a property of the network rather than of the interface a participant happens to use |
| Confidentiality without loss of proof | SCP-ZK and the on-chain nullifier registry let ownership and compliance be proven without disclosure, and make a proof unusable a second time |
| An identity standard for autonomous agents | A dedicated transaction class carries the AI Agent Identity record, separate from the class that carries a settled deed, so an agent can hold a verifiable identity without being mistaken for an instrument |
| Asset classes beyond property | The Compute Deed extends settlement to metered infrastructure, and the registry is specified to absorb further classes rather than to be replaced by them |
| A settlement economy already operating | Products settle through these layers today across several verticals, and their status is published in the ecosystem record rather than asserted here |
None of the above is a plan. Each is running on both networks and readable at swssscan.swss.io, which is the standard this document holds itself to throughout: a capability that cannot be checked is a claim, however carefully it is written.
Protocol Development Horizon
swss roadmap --horizon
The three are drawn differently on purpose. A document that renders what is running and what is being researched in the same weight is asking the reader to take both on the same trust, and the reader has no way to tell them apart.
Settlement requirements for regulated assets will keep moving, and a protocol that answers them has to advance at the layer that decides settlement. SCP is versioned and upgraded through on-chain validator governance, developed at the SWSS Chain Global Technology Centre, and each track below states what it delivers for settlement rather than only what it is called. The development record of what has already shipped is in the Master Development Timeline.
| Track | Capability for settlement | Status |
|---|---|---|
| SCP v3.1.4 with SCP-ZK v3.3.0 and SWSS IVL v1.4.3 | The production stack: four SCP pillars at the consensus layer, zero-knowledge settlement privacy with an on-chain nullifier registry, Foundation-governed credentials, and on-chain validator rotation. Running on mainnet 122605, with the forward track validated on testnet 122606 | Current Production |
| SCP v3.2.1 — forward track on testnet 122606 | Threshold signing architecture using distributed validator technology, so the signing duty behind a Finality Certificate is shared across a validator's infrastructure rather than resting on one key. A planned improvement to how institutional operators hold consensus responsibility | Planned |
| Forward privacy track | The forward privacy track, extending what can be proven about a settlement without disclosing it, for counterparties whose confidentiality obligations are stricter than disclosure-based compliance allows | Planned |
| Forward identity track | The forward identity track, broadening what a Foundation-governed credential can attest as more institutional classes and jurisdictions settle on the network | Planned |
| SCP v5.x and beyond — research | Capabilities under active research and deliberately withheld until they are production-ready. Nothing on this line describes what the network runs today | Research |
Two things are worth stating plainly about that table. Every forward track is marked as such, and what mainnet runs is what mainnet reports — the network answers the version question directly, so no reader has to take a roadmap as a description of the present. And an upgrade reaches mainnet through validator governance rather than by operator decision, which means the settlement layer advances by proposal and vote rather than by announcement.
One Standard, Expanding By Asset Class
The scale of what SWSS Chain is built for is not measured in products. It is measured in asset classes the settlement standard can absorb without becoming a different standard. A Home Deed records real estate. A Compute Deed records metered infrastructure. An AI Agent Deed records an autonomous agent's standing. Each is a class of the same DEED-1 instrument, settled through the same transaction type, certified by the same consensus, and readable by the same Deed Indexer without a release for each new class.
That is the difference between a standard and a product line. A settlement layer that needed a new instrument for every asset class would fragment as it grew, and each fragment would need its own legal characterisation, its own tooling and its own audit. The Expanding Deed Registry is specified so that a new class inherits the properties the existing ones already have — finality certified by consensus, jurisdiction and legal owner carried in the record, privacy available without loss of auditability, and identity verified at the protocol.
The classes that follow will be determined by which markets need settlement rather than by which are convenient to build, and each will be published in the ecosystem record as it ships. The commitment this section makes is architectural rather than commercial: whatever settles next settles through the same four layers, and nothing is granted a path around them.
SWSS Chain — Ecosystem Access Points
| Platform | URL | Purpose |
|---|---|---|
| Main Website | swss.io | SWSS Chain ecosystem hub |
| Whitepaper | whitepaper.swss.io | Official whitepaper and protocol documentation |
| Block Explorer | swssscan.swss.io | Live chain explorer, where every settlement is verifiable in real time |
| Mainnet RPC Endpoint | swssrpc.swss.io | SwssChain mainnet, chain id 122605, for developers and wallets |
| Testnet RPC Endpoint | testnet.swssrpc.swss.io | SwssChain testnet, chain id 122606, for integration and development |
| Documentation | docs.swss.io | Developer documentation, API reference, SDK |
| Investor Enquiries | [email protected] | Direct investor relations contact |
Legal Disclaimer
This whitepaper is provided for informational purposes only and does not constitute financial advice, investment advice, legal advice, or any solicitation to purchase or sell any financial instrument or digital asset. SWSS Coin is a utility coin — the native currency of SWSS Chain, a live operational blockchain network. It is not a security, does not represent ownership rights in any entity, and does not confer any right to profits, dividends, or distributions of any kind. Prospective participants should seek independent legal and financial counsel before making any decision based on the contents of this document. The regulatory status of SWSS Coin and related products may vary by jurisdiction.
SWSS Foundation — British Virgin Islands | SWSS Fintech — Canada (FINTRAC MSB Licensed) | SWSS Fintech — United Kingdom | SWSS Fintech — Dubai | SWSS Foundation — Malaysia
Where can SWSS Chain be independently verified?