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.
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.
The systems that publish SwssChain's content, admit its validators and operate its services all have administrative surfaces. Those surfaces are a target precisely because they are where legitimate authority is exercised, and an ecosystem that secures its consensus layer while leaving its control planes conventionally protected has moved the weak point rather than removed it.
Properties of Administrative Authority
| Property | What it means in practice |
|---|---|
| Identity comes from the Foundation | Administrative identity is issued and governed centrally by the SWSS Foundation. An application does not maintain its own private notion of who an administrator is, so there is no local account store to compromise and no application-specific password to leak |
| Proved on every request | Authority is verified on each individual request, not established once at sign-in and trusted thereafter. A session that ceases to be valid ceases to be able to act at its next request rather than at its next login |
| Two independent factors of authority | Reaching an administrative surface requires more than one independent thing to be correct. Possession of either alone is not sufficient and does not indicate that the other exists |
| Attributable, never shared | Every administrative action is attributable to a named, verified individual. There are no shared administrative credentials anywhere in the ecosystem |
| Withdrawal is immediate and central | Because identity is governed centrally, removing a person's authority removes it everywhere at once. There is no per-application deprovisioning step that can be forgotten |
| Uniform across modules | Enforcement is applied to every administrative module without exception. A module is not permitted to opt out, and the absence of enforcement on any one of them would be a defect rather than a configuration |
A Denied Request Reveals Nothing
This is the design decision in this area worth stating explicitly, because it runs against the ordinary convention and the reason is not obvious.
Conventional systems distinguish between "you are not authorised" and "this does not exist". That distinction is a convenience for legitimate users and an oracle for everyone else: it confirms that an administrative surface exists at the address being probed, which is the single most useful fact an attacker can learn before they have anything else. SwssChain's administrative surfaces do not make that distinction. A request that does not carry valid authority receives the same response as a request to something that was never there.
The consequence is that an unauthorised party cannot use the system's own responses to establish that there is anything to attack, let alone to enumerate it. The cost is borne entirely by administrators, who occasionally see an unhelpful response when something is genuinely misconfigured. That trade is made deliberately and in that direction.
What the Two Responses Look Like
The design decision above is easier to see than to describe. Below are two requests: the first to an administrative surface that exists, carrying authority that is not valid; the second to a path that has never existed on any SWSS system.
GET /<administrative-path> HTTP/1.1
Authorization: Bearer <expired or invalid session>
HTTP/1.1 404 Not Found
GET /<path-that-was-never-real> HTTP/1.1
HTTP/1.1 404 Not Found
The responses are identical, and that is the entire point. Neither one confirms that an administrative surface exists at the address being probed, so an unauthorised party cannot use the system's own answers to establish that there is anything there to attack. A conventional 401 would answer that question on the first attempt.
What Administrative Authority Does Not Extend To
Administrative authority over an SWSS application is authority over that application. It is not authority over member holdings, which are moved only by the member through SWSS App, and it is not authority over settlement, which is decided by the validator set. The boundaries are the ones described in SWSS Ecosystem Security, and they apply to SWSS's own staff exactly as they apply to anyone else.
Changes that bind the protocol rather than an application are enacted through SWSS Governance, where the decision is recorded on chain and remains auditable by parties who were not present when it was taken.
