An internal security review of the full contract set is complete and its findings have been closed in remediation sprints. An external, integration- and configuration-scoped review precedes mainnet deployment and token generation.
Regional settlement is configured and paused per region. One region can pause while others continue, and ordinary token transfers carry on.
The compliance layer supports KYC tiers, per-address daily limits and Travel-Rule-aware thresholds. It is exercised on testnet and switched per market at launch; protocol modules and consumer addresses are classed separately, so limits apply to consumers only.
Bridged RWLY can exist only against RWLY locked on Polygon; bridge amounts are bounded per transaction and per day; the bridge pauses independently.
Deployment keys hold bootstrap roles only during deployment and are retired before token generation. Administrative, emergency, treasury and regional roles are held by governance multisigs distinct from the deployer; the role-health check that enforces this blocks the runbook on failure. Proxy administration is owned by the protocol's own proxy manager, and its ownership is transferable to governance.
Roles move to governance multisigs before token generation; the role-health check enforces it at deploy.
The protocol deploys region by region, gated on regulatory readiness. A jurisdiction's framework sets the calendar.
Middle East digital-asset regimes (UAE — VARA, ADGM, DIFC; Bahrain CBB) and the European Union under MiCA.
Excluded at token generation, pending a settled framework.
Where a framework is still forming, the application operates in points and local currency, and the protocol follows the framework.
One region can pause while others continue.