Overview
SWSS DevHub is gated. Every developer signs in with SWSS IVL and is then reviewed by the Foundation before the portal opens.
Sign in with SWSS IVL → Apply → Foundation review → Access
There is no password anywhere in this flow, and nothing to redeem.
Step 1 — Sign in with SWSS IVL
Choose Sign in with SWSS IVL. You are sent to SWSS IVL's hosted login, which accepts email or Google. If you have never used SWSS IVL before, an account is created for you on first sign-in, with a wallet already attached.
DevHub never sees a password, and never issues one.
Step 2 — Apply
Signing in is not access. A first sign-in with no application gives you a visitor session, which can do exactly one thing: submit the application form on the gate page. You are asked for:
- Your name and email
- Company or project, if you have one
- What you intend to build on SwssChain
Step 3 — Foundation review
Applications are reviewed by hand. Nothing about approval is automatic, and there is no queue position to check — the gate page shows your status while the application is pending.
If your application is declined, the gate page says so.
Step 4 — Access
On approval, your session upgrades itself the next time the gate page checks — there is nothing in your inbox to act on and no code to enter. The portal, the faucet and API keys open at that point.
Sessions
A developer session is an httpOnly cookie (swss_dev_token) that lasts 24
hours, after which you sign in with SWSS IVL again.
Approval is re-checked on every request, not just at sign-in. The session proves who you are; the Foundation's decision — which can change — is what grants access. If access is withdrawn, it stops immediately rather than at the end of the day.
Legacy invite codes
Accounts created before 2026-08-02 were issued a single-use invite code and set a password. That flow is retired. Existing developers sign in with SWSS IVL like everyone else, and new developers never receive a code.
Losing access
Contact the Foundation through Support. Because identity is SWSS IVL's and access is the Foundation's, there is no password for anyone — support included — to reset.
