SWSS RWAX
Wallet and Payments
Pre-launch
Section
SWSS RWAX
Product documentation
Type
Guide
Technical reference
Summary
Why RWAX holds no wallet of its own, what it consumes from the SWSS Unified App, and where balances actually live.
Article Content

RWAX operates no wallet. Balances, transfers and settlement are the SWSS Unified App's domain, and RWAX consumes that one surface rather than reimplementing it.

Why It Is Built This Way

Authority in this ecosystem is per domain. Two systems that both moved money would be two systems that could disagree about what a member holds, and reconciling them afterwards is the failure the design exists to avoid. So there is one wallet authority, and RWAX asks it.

RWAX holds no treasury key for BNB Chain. What it holds are the keys for its own domain: issuing deeds on SwssChain, and attesting completed work.

What This Means in Practice

ConcernWhere it is handled
Your balances, sending and receivingThe Wallet Screen
StakingStaking in the Application
Moving SWSS Coin between networksConverting SWSS to wSWSS
Paying for a deedAcquiring a Deed: in RWAX, to the address the screen shows

Deed Truth Flows the Other Way

RWAX consumes wallet operations from the SWSS Unified App; the SWSS Unified App consumes deed data from RWAX. Neither is the other's master. Each is the authority for exactly one domain and a client for the rest.