Security
SWSS Ecosystem Security
Pre-launch
Section
Security
Documentation category
Type
Guide
Technical reference
Summary
Security in the SWSS ecosystem is structural: authority is divided by domain, and a compromise in one domain does not become authority in another.
SWSS Foundation Notice

This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.

All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.

Join SWSS DevHub →Have a question? Use the Need Help? button below.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content

Most descriptions of platform security are descriptions of diligence: controls applied carefully, reviewed regularly, operated by competent people. Diligence matters, but it is the same claim every operator makes and it is not what an institution can rely on, because it cannot be verified from outside and it degrades silently.

SWSS states something stronger and more specific. In this ecosystem, security is a property of how the parts are divided, not only of how well they are run. Authority is separated by domain, each domain owns its own completely, and no domain holds the authority of another even temporarily. A compromise is therefore bounded by the domain it occurs in, not because a control would stop it from spreading, but because there is no authority in that domain to spread with.

How Authority Is Divided

DomainOwns, completelyHolds no authority over
SWSS Identity Verification LayerIdentity, verification, credentials and the signing of what a member has approvedBalances, staking, settlement. It holds no holdings and initiates nothing
SWSS AppMember holdings and everything they do: wallet operations, staking, treasury movement, bridgingIdentity issuance. It cannot create or alter a credential
SWSS RWAXDEED-1 records and exchange dataConsensus, validator admission, member holdings
SWSS NodeXValidator qualification and operationMember holdings and identity. A validator secures settlement; it does not gain authority over what settles

The distinction is easiest to see in the identity layer. It authenticates a member and signs what that member has approved, and it holds nothing. An attacker who obtained everything the identity layer holds would obtain the ability to authenticate, and nothing that authentication alone can move, because the authority to move it lives in a different domain under different control. See SWSS Identity Verification Layer.

What Consensus Guarantees Rather Than Promises

Several properties institutions normally rely on an operator to promise are decided by the protocol instead, which means they hold whether or not the operator is behaving well.

  • Ordering is not discretionary. Transaction order is fixed before block production and immutably once the round concludes, so fair sequencing is a protocol guarantee rather than an operational commitment. See DSA: Deterministic Sequencing Arbitration.
  • Finality is attested, not asserted. A Finality Certificate is produced by the validator set at the block that settled a transaction. No application above consensus can certify what consensus has not decided. See BFTFA: Byzantine Fault Tolerant Finality Attestation.
  • Validator identity is accountable. Validators are admitted after institutional verification and Foundation approval, so every signer is a legally identified entity rather than an anonymous key. See Developer and Validator Access.
  • Sensitive records settle without disclosure. Zero-knowledge settlement allows a record to be verified without publishing its contents. See SCP-ZK: Zero-Knowledge Settlement Privacy.

Operated by the Foundation, Not Delegated

The SWSS Technology Team operates the ecosystem's security infrastructure directly (custody, administrative control planes, validator and network infrastructure) on infrastructure the Foundation controls. Where a third party performs a function, as identity verification providers do, the Foundation admits the provider and the resulting credential is the Foundation's rather than the vendor's. A supplier's own security posture does not silently become SwssChain's.

The Rest of This Section

PageWhat it establishes
Key Custody and ProtectionHow signing material is held, and why the operational detail is unpublished
Administrative Access ControlHow authority over SWSS's own systems is granted, proved and withdrawn
Infrastructure and Network ProtectionHow the network and the systems that serve it are protected and observed
Contract Assurance and Deployment ControlHow contracts are reviewed, verified, deployed and superseded
Incident ResponseHow SWSS detects, contains and closes out a security event
Reporting VulnerabilitiesHow to reach the security team, and what protection a researcher has
Independent AssuranceWhat is reviewed by parties who did not build it

Verifying This Yourself

The claim that validator identity is accountable and that rotation happens on chain is not one a reader has to accept. The active set is returned by the chain, including the block at which each validator was admitted and the address any rotated validator was rotated from.

curl -s -X POST "$SWSS_RPC_ENDPOINT" \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","method":"swss_getValidatorSet","params":[],"id":1}'
{
  "result": {
    "epoch":       77,
    "blockNumber": 155925,
    "validators": [
      { "address": "0x36841E62...", "addedAtBlock": 0 },
      { "address": "0x5eD15343...", "addedAtBlock": 74000, "rotatedFrom": "0x06c40a72..." }
    ]
  }
}

The rotation is a fact of the chain rather than an entry in a directory maintained by SWSS, which is what makes it checkable by a party that does not trust the directory. Endpoints are issued on admission: see Developer and Validator Access.

Risk factors affecting the ecosystem as a whole are set out in the SwssChain Whitepaper: Risk Factors.