SWSS Chain is a sovereign Layer 1 blockchain built from genesis for a single purpose: the legal settlement of real-world assets. Settlement, identity and privacy are protocol functions specified at genesis rather than standards layered on afterwards. Mainnet operates at Chain ID 122605 under SCP v3.1.4 consensus and produces a block every 1 second. Development commenced in Q1 2019, and mainnet was declared production-ready only after more than 365 consecutive days of independently operated validator testing. The SwssChain section sets out the architecture in full, and The Problem explains why an existing chain could not simply be adapted to carry it.

Settlement here is a protocol function rather than an application deployed above one. A deed transaction is a native transaction class, processed ahead of every other class, and the protocol issues a Finality Certificate for it — a signed, irreversible attestation produced by the active validator set rather than by a contract, described in full under the Consensus Protocol. The record that transaction produces is the DEED-1 Settlement Standard: a legal settlement instrument, not a collectible, carrying full ERC-721 compatibility so that any standard wallet can hold and display it. The Identity Verification Layer binds every participant to an on-chain credential before they are permitted to settle, and ZK Settlement Privacy allows a sensitive record to be proved without being published.

Every product in the ecosystem operates on this chain and settles in the same currency. SWSS Coin is the native currency for gas, staking and settlement, and a fraction of every settlement is permanently retired from circulation through the Transactional Settlement Levy set out in Tokenomics — so activity on the network contracts supply rather than expanding it. Consensus is secured by the validator set operated through SWSS NodeX, the settlement record is published by SWSS Explorer, and the ecosystem overview lists every product that settles on this layer.

Chain Parameters

The Deed Transaction Class

On SWSS Chain the settlement is the transaction itself, not a contract deployed to represent one. A deed transaction is a native class the protocol understands directly, scheduled ahead of every other class in the block, so a property transfer is never queued behind unrelated network activity. The protocol validates the participants' credentials, applies the state change, and emits a Finality Certificate as part of consensus rather than as an afterthought.

That certificate is the output that matters outside the chain. It is signed by the active validator set, cannot be altered, revoked or overwritten, and is permanently public — which is what allows a registry or an institutional counterparty to treat it as evidence rather than as a claim. The instrument it attests is DEED-1, and the indexing layer that makes a settled deed searchable is the Deed Indexer.

Networks and Endpoints

Two networks run the same client build. SwssChain mainnet is Chain ID 122605 and the SwssChain testnet is Chain ID 122606; both produce a block every 1 second, so the testnet rehearses the production protocol rather than approximating a reduced version of it. Contracts, tooling and integrations that work against one work against the other.

The endpoints in the table above are the only addresses that belong in a wallet, an application or any infrastructure. Older third-party material occasionally lists a shorter address on the same domain; it has no DNS record and resolves nowhere, so an integration configured from that material fails at connection time rather than degrading quietly. Full EVM compatibility at the Cancun level means standard JSON-RPC libraries and wallets connect without modification — compatibility is the floor here, not the product.

Security and Finality

Finality is deterministic rather than probabilistic. A block is either finalised under SCP v3.1.4 or it is not, and once it is, the state change is irreversible — there is no confirmation count after which a settlement becomes safe to rely on, because it was either settled or it was not. This is the property a legal settlement layer needs and a probabilistic chain cannot offer.

The validator registry recognises three classifications — Foundation, Institutional and Custodian — and the classification is a field on the chain itself rather than an off-chain directory. Institutional and Custodian validators are admitted by on-chain proposal against verified credentials, so the set is open without being anonymous. Operations, delegation and admission run through SWSS NodeX, and a correction to a settled deed is appended as a new attested event rather than written over the original, which preserves the full provenance instead of replacing it.

Block Explorer

The settlement record is published through SWSS Explorer at swssscan.swss.io, which is a product in its own right and has its own page. Block production, the active validator set, every deed settlement and every Finality Certificate are readable there without an account, which is what makes the claims on this page checkable rather than merely stated.