Security
Infrastructure and Network Protection
Pre-launch
Section
Security
Documentation category
Type
Guide
Technical reference
Summary
How SwssChain validator, node and service infrastructure is operated, isolated and observed by the SWSS Technology Team.
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

A settlement network is only as available as the infrastructure that carries it. SwssChain's validator set, its node infrastructure and the services that surround them are operated directly by the SWSS Technology Team on infrastructure the Foundation controls, rather than assembled from managed services whose operators would inherit a position inside the network.

How the Infrastructure Is Arranged

PropertyWhat it means in practice
Isolated by functionConsensus, public-facing services and administrative control planes run in separate environments with separate credentials. A component reachable from outside is not a component that holds signing authority
Separated by network, not by conventionSystems that hold data or signing authority are not reachable from the public internet at all. Reachability is a property of the network they sit in rather than a rule applied at the application
Distributed across independent failure domainsThe validator set is distributed so that the loss of any single site, provider or region does not halt settlement. Consensus continues while a minority is unavailable, by design of the protocol rather than by operational response
Controlled at the edgePublic-facing endpoints apply capacity and rate controls, so demand, whether accidental or deliberate, is absorbed at the boundary rather than reaching the systems behind it
Observed continuouslyInfrastructure is monitored continuously for availability and for anomalous behaviour, with alerting into the response process described in Incident Response
Validator identity rotates on chainA validator's operating address can be rotated through an on-chain procedure without the validator leaving the active set, so replacing operational material is a routine action rather than an outage. See On-Chain Validator Address Rotation

Access to the Network Is Admitted, Not Assumed

Participation in SwssChain infrastructure is granted rather than taken. Validators are admitted through institutional verification and SWSS Foundation approval; developer access to network endpoints is granted to approved participants under the terms described in Developer and Validator Access. Every party holding a connection to the network is therefore a known and legally identified entity, which is what makes abuse attributable rather than merely detectable.

Proven Before It Carries Value

SwssChain's consensus and infrastructure have been operated continuously on testnet for more than 365 days of sustained testing before mainnet settlement carries institutional value. That period exists to expose the failures that only appear under real duration (resource exhaustion, clock drift, upgrade behaviour under load, partition recovery) none of which a short test can reach. The protocol version, block behaviour and validator set in production are observable from the chain itself and from SWSS Explorer, so the operational claims made here can be checked rather than taken.

Endpoint addresses and infrastructure topology are not published here

Network endpoints are issued to approved participants through the access process rather than listed on a documentation page, and the arrangement of the infrastructure behind them is not described. Neither is useful to a legitimate integrator, who receives what they need on admission, and both are useful to anyone else.