Get started testing

Testnet only. Never enter a mainnet recovery phrase into experimental software.

Option A — Android authenticator (testnet, available now)

This demo is aimed at Dash developers and others who may implement SIWD on their own sites, build their own authenticator, or integrate login capabilities into a wallet. There is a working standalone Android authenticator for testnet (sideload; not a Play Store product).

Prefer building from source so you can read and audit the code before putting a recovery phrase on a device. Source lives under apps/android-authenticator in https://github.com/rhelwig/SignInWithDash.
A prebuilt debug APK is published for convenience while iterating: Download SIWD Android authenticator (testnet debug APK). Treat it as a developer sample — verify the build from source for any serious use.
Real testnet DPNS required on this public site. You need a Dash Platform testnet identity whose finalized DPNS name you control (e.g. from testnet DashPay), plus the recovery phrase for those keys. The app’s alice/bob entries are local fixtures only — they do not log into platform-mode hosts like this one. Never enter a mainnet recovery phrase.
Flow: open Sign in with Dash here → scan the QR (or paste the capability URL into the app) → approve with an imported identity → browser finishes.

Wallet integration is not required to use SIWD. A separate authenticator keeps site-login signing apart from a full payment wallet; wallets may still choose to embed SIWD later.

Build tips: JDK 21, Android SDK; see the authenticator README and local network config notes.

Use only generated testnet credentials — never a mainnet phrase
Prefer scanning the QR from a device you control
Approve only if you started the login for this exact domain moments ago

Option B — Localhost with dev simulator

Not available on this public host. This site runs in platform verify mode with the simulator off. Fixture identities (alice/bob) and the /dev/simulator UI are for local development only (SIWD_VERIFY_MODE=hybrid or simulator, SIWD_ENABLE_SIMULATOR=true). Use Option A with a real testnet DPNS name instead.

Invites & access control

Site owners can restrict who may create accounts (allowlist), let existing users invite up to a fixed number of Dash names, and maintain ban lists. Signed-in users manage this under Access & invites.

Pen-testers

See Security & testing notes for intentional residual risks, rate limits, and what is in-scope for the demo.

Please run aggressive scanners against your own deployment, not the public demo.

Support

Optional: donate if you appreciate the work.