Products
SWSS NodeX
Pre-launch
Section
Products
Documentation category
Type
Guide
Technical reference
Summary
SWSS NodeX, the validator node infrastructure platform for SwssChain, covering node requirements, operator onboarding, and SCP participation.
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

SWSS NodeX

SWSS NodeX is the validator node infrastructure platform for the SwssChain network. It provides the tooling, monitoring, and management interface that node operators use to participate in the SwssChain Consensus Protocol (SCP) validator set, contribute to Finality Certificate production, and earn staking rewards through the Stake Gravity Protocol.

Node Roles

A SWSS NodeX validator participates in all four pillars of the Settlement Consensus Protocol. These are not roles an operator chooses between, every admitted validator performs each of them:

Role Abbreviation Function
Stratified Asset Prioritisation EngineSAPEValidates transactions, propagates blocks, signs Finality Certificates
Deterministic Sequencing ArbitrationDSAAggregates delegated stake from SWSS Coin holders
Predictive Commitment ArchitecturePCAProvides cryptographic attestation of node uptime and performance
Byzantine Fault Tolerant Finality AttestationBFTFAArbitrates finality disputes and enforces BFT consensus rules

Minimum Hardware Requirements

Component Minimum Recommended
CPU8 cores / 16 threads16 cores / 32 threads
RAM32 GB64 GB
Storage2 TB NVMe SSD4 TB NVMe SSD (RAID-1)
Network100 Mbps dedicated1 Gbps dedicated
Uptime SLA99.5%99.9%
OSUbuntu 22.04 LTSUbuntu 22.04 LTS

NodeX Dashboard

The SWSS NodeX Dashboard, available to operators the SWSS Foundation has admitted to the validator set, provides real-time visibility into:

  • Block production statistics and missed block rate.
  • Finality Certificate signing participation rate.
  • Delegated stake volume and DSA health metrics.
  • PCA uptime attestation history and current Stake Gravity Coefficient.
  • Slashing event log and penalty history.
  • Reward accumulation and distribution history.

Operator Onboarding

The validator set is admitted, not joined. Running the software and holding the stake does not make an operator a validator: SwssChain settles real-world assets, and every entity signing a Finality Certificate is a legally identified one. Admission runs through SWSS NodeX in this order:

  1. Apply through SWSS NodeX. Register the operating entity and the jurisdictions it operates from.
  2. KYB. Complete Know Your Business verification through the SWSS Identity Verification Layer (registration, directors, beneficial ownership) via a provider admitted to the Foundation-governed IVL Provider Registry.
  3. Foundation approval. The SWSS Foundation reviews the verified application and approves or declines admission to the validator set. No stake, hardware or uptime record substitutes for that decision.
  4. Provision and install. Hardware meeting the specification above, and the SWSS NodeX client, which is distributed to approved operators only.
  5. Stake. Deposit at least the Stake Gravity Protocol minimum operator stake.
  6. Register keys. Node public keys are registered against the approved operator identity with the SCP validator set coordinator.
  7. Testnet trial. Complete the validator trial on SwssChain testnet 122606, minimum 30 days, before admission to mainnet 122605.

Approval may be withdrawn. An operator whose KYB lapses, or whose verified entity changes control, returns to review.

The current minimum operator stake threshold and testnet trial period requirements are published on the SWSS NodeX product page.

Slashing Conditions

Node operators are subject to stake slashing under the SCP's Byzantine Fault Tolerant Finality Attestation (BFTFA) for the following provable misbehaviour:

  • Double-signing blocks at the same height.
  • Equivocation: signing two conflicting finality certificates for the same block.
  • Extended downtime exceeding the protocol's liveness threshold.

Slashing penalties are proportional to the severity and recurrence of the violation. Slashed stake is redistributed per the Ecosystem Revenue Recirculation Protocol.

Frequently Asked Questions
6 questions
Can I run a validator if I have the stake and the hardware?

Not on that basis alone. The validator set is admitted, not joined: apply through SWSS NodeX, complete KYB, and receive SWSS Foundation approval before provisioning.

Why does a validator need business verification?

Every entity signing a Finality Certificate is signing evidence a registry or court may later rely on. That evidence is worth what the identity of its signers is worth.

Where do I get the node client?

It is distributed to approved operators only, through SWSS NodeX after admission.

How long is the testnet trial?

A minimum of thirty days on testnet 122606 before admission to mainnet 122605.

What can I be slashed for?

Double-signing at the same height, equivocation between conflicting finality certificates, and downtime beyond the liveness threshold. Penalties scale with severity and recurrence.

Can approval be withdrawn after admission?

Yes. Lapsed KYB or a change of control in the verified entity returns the operator to review.