The most sensitive real-world asset transactions require one property above all others: the ability to prove settlement without disclosure. SCP-ZK v3.3.0 delivers this.
SCP-ZK is the Zero-Knowledge Settlement Privacy layer integrated into the SWSS Chain protocol stack. It enables any party to prove legally required facts about a DEED-1 settlement record or an identity credential — ownership, compliance, authorisation — without revealing the underlying information to any counterparty, to the settlement layer, or to the public. It is built on Groth16 over the BN254 curve, and it is live on SWSS Chain mainnet.
What SCP-ZK Proves
The Production Ceremony
swss zk trust --chain
Each stage removes a party you would otherwise have to trust. The ceremony removes any single contributor, the fixed key removes us, on-chain verification removes the application, and the nullifier removes the holder — the same proof cannot establish the same thing twice, whoever presents it.
The cryptographic parameters underpinning SCP-ZK were generated on 3 June 2026 through a multi-party parameter generation ceremony, using the Groth16 BN254 proving system. Three parties contributed in separate sessions with no shared state: two independent external contributors and the SwssChain Foundation. Two circuits were parameterised, one for deed ownership and one for KYC compliance, which are the two proof domains described above. A ceremony transcript and the SHA-256 hashes of both production verifying keys are retained and available to institutional counterparties on request.
The security guarantee of a multi-party ceremony holds as long as at least one participant was honest, and each participant need trust only themselves. Because the three contributed in isolation, no single party can compromise the parameters, and that includes the SwssChain Foundation. Its own participation does not weaken the guarantee; it would have to be the only honest party for the ceremony to fail, which no participant can arrange.
Replay Protection
Every successful SCP-ZK proof carries a unique nullifier, a one-time cryptographic marker recorded on chain at verification in a dedicated nullifier registry contract. Any attempt to submit the same proof twice is detected at the protocol level before verification is attempted, so proof replay is architecturally impossible rather than merely detected after the fact. The registry is a permanent on-chain settlement record, publicly visible at swssscan.swss.io.
Why No Other RWA Chain Has This
Adopting an existing proof library does not produce this. What cannot be lifted is the integration: a completed production ceremony, an on-chain nullifier registry the protocol checks before verification, and two proof domains defined against the DEED-1 settlement standard rather than against a generic asset model. The proving system is public and the circuits are ordinary; the settlement layer they are wired into is not. SCP-ZK is live on SWSS Chain mainnet 122605, and the testnet at 122606 runs the same client build.
What can be proven without disclosure?