SWSS Docs is the official documentation platform for SWSS Chain, SWSS Coin, and all SWSS ecosystem products — technical reference documentation, integration guides, protocol specifications, and product documentation.
SWSS Docs carries the complete technical specification of the protocol and the standards built on it: SCP v3.1.4 consensus, the DEED-1 Settlement Standard, SCP-ZK v3.3.0 for zero-knowledge privacy, IVL v1.4.3 for identity, the Deed Indexer API, and SDK tooling for every supported language. It is updated continuously as protocol versions advance, and it is version-controlled, so a reader can see not only what the specification says but when it changed.
It exists because a settlement layer that publishes claims and withholds specifications is asking to be trusted rather than checked. Everything documented here is public and permanently accessible, with no account, no key and no application process — a protocol specification that cannot be read without permission cannot be verified, which defeats the purpose of publishing one.
The documentation and this whitepaper answer different questions and are deliberately separate. This document explains what the system is and why it is built this way — the argument in SwssChain, the Consensus Protocol and the DEED-1 Standard. The documentation explains how to work with it. A reader deciding whether the architecture is sound belongs here; a developer constructing a deed transaction or querying the Deed Indexer belongs there.
What Is Documented
| Layer | What the documentation specifies |
|---|---|
| Consensus — SCP v3.1.4 | The four pillars, block production, finality and the Finality Certificate |
| DEED-1 Settlement Standard | The deed transaction class, metadata, ownership records and transfer rules |
| Zero-knowledge — SCP-ZK v3.3.0 | Proof domains, the nullifier registry and selective disclosure |
| Identity — IVL v1.4.3 | Credentials, verification and the gate applied before settlement |
| Deed Indexer API | Query surface for deeds and their history at scale |
| SDK tooling | Integration guides and libraries for supported languages |
The versions above are read from the published record rather than typed into this page, so the whitepaper and the documentation cannot disagree about which version is current. Where either disagrees with what a node reports, the node is correct.
Access And Versioning
Documentation is versioned alongside the protocol it describes. When a version advances, the specification advances with it and the change is visible rather than silent — which matters most for the readers who integrated against the previous version and need to know precisely what moved.
SWSS Docs is counted as a product in its own right for the same reason SWSS Explorer is: it has its own codebase and release cycle, and it stays useful and available independently of any product interface. Developer onboarding, credentials and testnet access are handled separately by SWSS DevHub; the documentation is the reference those developers then work from.
Milestones
| Period | Description | Status |
|---|---|---|
| Q1 2026 | SWSS Docs — live | Live |
What does SWSS Docs cover?