Sign in with Dash testnet platform

How to test (public testnet demo)

Testnet only. Never enter a mainnet recovery phrase into the demo site, the Android authenticator, or the dev simulator. Testnet identities and faucets have no real value.

What you need

  1. A Dash Platform testnet identity with a finalized DPNS name you control (for example created in DashPay testnet / related testnet tooling). SIWD proofs are name + key + identity: without a resolvable name, this public demo rejects the login (name_ineligible).
  2. The Android authenticator (testnet APK or build from source), with that identity imported from the recovery phrase — not the app’s alice/bob fixtures. Fixtures only work against a local site in hybrid/simulator mode.
  3. Optional for self-hosters: a private/local deployment with SIWD_ENABLE_SIMULATOR=true and hybrid/simulator verify mode, plus the dev simulator.
  4. Optional: testnet dash for identity registration (via a public testnet faucet if required by your wallet flow).

Why alice/bob fail here: they are synthetic local keys. On live testnet, bob.dash does not resolve; alice.dash is a different real identity than the fixture. This host uses verifyMode=platform.

Suggested path

  1. Install the authenticator (prefer build from source; debug APK is for convenience only).
  2. Import your testnet recovery phrase (and optional BIP-39 passphrase if you set one when creating the wallet). Confirm the DPNS name appears under Identities.
  3. On this site, open Sign in with Dash.
  4. Scan the QR with the authenticator (or paste the capability URL).
  5. Choose the imported identity (not alice/bob), then approve only if you started this login for this exact domain moments ago.
  6. The browser finishes and creates/opens your site account (identity-bound).

Risks & courtesy

APK & source

Download testnet debug APK · Authenticator source · Full get-started notes