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 Engine | SAPE | Validates transactions, propagates blocks, signs Finality Certificates |
| Deterministic Sequencing Arbitration | DSA | Aggregates delegated stake from SWSS Coin holders |
| Predictive Commitment Architecture | PCA | Provides cryptographic attestation of node uptime and performance |
| Byzantine Fault Tolerant Finality Attestation | BFTFA | Arbitrates finality disputes and enforces BFT consensus rules |
Minimum Hardware Requirements
| Component |
Minimum |
Recommended |
| CPU | 8 cores / 16 threads | 16 cores / 32 threads |
| RAM | 32 GB | 64 GB |
| Storage | 2 TB NVMe SSD | 4 TB NVMe SSD (RAID-1) |
| Network | 100 Mbps dedicated | 1 Gbps dedicated |
| Uptime SLA | 99.5% | 99.9% |
| OS | Ubuntu 22.04 LTS | Ubuntu 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:
- Apply through SWSS NodeX. Register the operating entity and the jurisdictions it operates from.
- 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.
- 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.
- Provision and install. Hardware meeting the specification above, and the SWSS NodeX client, which is distributed to approved operators only.
- Stake. Deposit at least the Stake Gravity Protocol minimum operator stake.
- Register keys. Node public keys are registered against the approved operator identity with the SCP validator set coordinator.
- 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.