SWSS DevHub is the single front door for every developer building on SWSS Chain. A developer arrives with no relationship to the Foundation and leaves with a verified identity, testnet funds, credentials scoped to what they are permitted to call, documentation, and a direct line to the engineers who built the protocol.
Settlement infrastructure is only as valuable as what is built on it. SWSS DevHub exists so that the distance between reading about SWSS Chain and settling a deed on it is measured in hours, not in procurement cycles. It is the developer community platform of the ecosystem: documentation, SDK tooling, testnet access, credentialed API access, and support, behind one identity and one door.
Identity Is Not Rebuilt Here
Access to SWSS DevHub is granted through SWSS ID. A developer signs in with the same verified identity used everywhere else in the ecosystem, and DevHub issues no password of its own and holds no second identity record. This is a deliberate architectural constraint rather than a convenience: an ecosystem with two identity authorities has none, and the credentials DevHub issues deliberately carry no identity attributes at all.
What A Developer Receives
| Capability | What It Provides |
|---|---|
| SWSS ID Access | One verified identity across DevHub and every other SWSS property, with no separate credential to manage |
| Testnet SWSS Coin | Testnet funds requested from the developer portal, for building and testing against Chain ID 122606 at no cost |
| Credentialed API Access | Keys scoped by permission class, so read access, extended protocol access and settlement submission are granted separately rather than all at once |
| Usage Accounting | Per-key request accounting and rate governance, so capacity is predictable under load rather than discovered during an incident |
| Protocol Documentation | Specifications, SDK reference and integration guides, maintained alongside the protocol rather than after it |
| Direct Support | A support channel routed by product and category to the Foundation engineering team |
| Release Intelligence | Changelog, protocol announcements and release notes ahead of deployment |
Testnet operates continuously as the verification environment for every SCP protocol advance before it reaches mainnet through on-chain governance. A developer building against testnet is building against the next release, not a simplified imitation of it.
Developer Access Points
| Resource | URL | Purpose |
|---|---|---|
| Developer Portal | devhub.swss.io | Access, credentials, testnet funds, support |
| Testnet RPC | testnet.swssrpc.swss.io | Chain ID 122606 (0x1DEEE) |
| Mainnet RPC | swssrpc.swss.io | Chain ID 122605 (0x1DEED) |
| Documentation | docs.swss.io | Protocol specifications, SDK and API reference |
| Block Explorer | swssscan.swss.io | Mainnet and testnet explorer |
Milestones
| Period | Description | Status |
|---|---|---|
| Q1 2026 | SWSS DevHub — live | Live |
What is SWSS DevHub for?