Network
STATUS
SWSS Chain Network
VALIDATORS · SCP CONSENSUS · BFT FINALITY
Block Time
1s
~0.5s effective finality
SWSS Chain Consensus Protocol
SCP v2.3.2 — Validator network operational — BFT finality instant
LIVESCP v2.3.2
SWSS Chain Consensus Protocol (SCP) is a purpose-built Byzantine Fault Tolerant consensus engine designed for RWA settlement. SCP provides instant finality, fair ordering for deed transactions, and legal-grade finality certificates — capabilities not available in general-purpose consensus protocols.
SCP Architecture — Four Pillars
SAPESynchronized Asynchronous Proposal Engine
SAPE enables block proposals to be prepared in parallel with the current consensus round. The proposal engine is synchronized to the BFT commit signal, allowing the next block to be ready the moment consensus commits.
DSADistributed State Advancement
DSA coordinates state transitions across all 4 validators without a central coordinator. Each validator advances state independently and reaches the same conclusion — guaranteed by BFT mathematics.
PCAParallel Commitment Architecture
PCA allows multiple commit phases to pipeline — while one block is being finalized, the next proposal is being built. This parallelism is the source of the SCP v1.2 predictive speed improvement.
SCPByzantine Fault Tolerance Finality Assurance
SCP provides the mathematical guarantee that once a block is committed by 3 of 4 validators, it is irrevocable — even if one validator acts maliciously. N=3F+1 with F=1 fault tolerance.
