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.
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.
Which JSON-RPC methods are supported?
All standard Ethereum JSON-RPC methods, plus the SwssChain-specific swss_* methods for deed and Finality Certificate data. See Custom swss_* RPC Methods.
Do I need a WebSocket endpoint?
Only for eth_subscribe: new blocks, log events and pending transactions. Everything else works over HTTP.
When do I need an archive endpoint?
For historical state at a past block: analytics, indexing, and any query that reads balances or storage as of a specific height rather than latest.
Can I use a third-party RPC aggregator?
Not for settlement-critical infrastructure. Confirm the current endpoint from your issued configuration, an endpoint you did not obtain from the Foundation is an endpoint whose behaviour nobody has committed to.
What are the rate limits?
They are scoped to the tier your approval covers, and each key carries its own allocation. See Rate Limits and Throttling.
Can I share one key across development and production?
No. Use separate keys per environment so a development workload cannot exhaust the allocation your production traffic depends on, and so a compromised key can be revoked without an outage.
