Products
SWSS Bridge
Pre-launch
Section
Products
Documentation category
Type
Guide
Technical reference
Summary
SWSS Bridge, the cross-chain asset bridge connecting SwssChain to external EVM networks with cryptographic attestation and trustless settlement.
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 Bridge

SWSS Bridge is the official cross-chain asset bridge connecting SwssChain to external EVM-compatible networks. It enables the movement of supported assets between SwssChain and other networks using a cryptographically attested lock-and-mint mechanism secured by the SCP validator set.

Supported Networks

Network Status Supported Assets
Ethereum MainnetLiveSWSS Coin (wrapped), USDC, USDT
BNB ChainQ3 2026SWSS Coin (wrapped), USDC
PolygonQ3 2026SWSS Coin (wrapped), USDC

Bridge Mechanism

SWSS Bridge uses a lock-and-mint model for outbound transfers (SwssChain to external network) and a supply-retirement and redeem model for inbound transfers (external network to SwssChain). The process is as follows:

SwssChain → External Network:

  1. The user locks the asset in the SWSS Bridge escrow contract on SwssChain.
  2. The lock event is observed and attested by the SCP SAPE node set.
  3. Upon reaching the required attestation threshold (2/3+ of active SAPE nodes), the Bridge Relay mints the equivalent wrapped asset on the destination network.
  4. The wrapped asset is delivered to the user's specified destination address.

External Network → SwssChain:

  1. The user sends the wrapped asset to the SWSS Bridge contract on the external network. The contract retires the wrapped asset supply.
  2. The retirement event is observed and attested by the SCP SAPE node set monitoring the external network.
  3. Upon threshold attestation, the Bridge Relay releases the equivalent native asset from the SwssChain escrow to the user's SwssChain address.

Security Model

The SWSS Bridge does not rely on a separate multisig operator set: attestation is performed by the same SCP validator nodes that secure the SwssChain network itself. This design eliminates the risk of a separate bridge operator key compromise. The attestation threshold of 2/3+ of active SAPE nodes means that bridge security inherits directly from the SwssChain consensus security guarantees.

Bridge escrow contracts on external networks are immutable after deployment and cannot be upgraded without a full redeployment, ensuring no administrative override is possible.

Bridge Fees

SWSS Bridge charges a flat fee per transfer, denominated in the asset being bridged. The fee schedule is published on the SWSS Bridge product page. Bridge fees cover the gas cost on the destination network and a protocol sustainability reserve allocation. No portion of bridge fees is directed to any individual operator.

Using the Bridge

The SWSS Bridge is reached from the SWSS App bridge module, and will have its own web address on release. Programmatic bridge submission is available via the SWSS Bridge API for applications requiring automated cross-chain asset movement. Contact the SWSS developer team for API access credentials.