Digi-ID

Digi-ID is passwordless login built on the same cryptography that secures DigiByte itself. When you open a Digi-ID login page, the site generates a random one-time challenge and shows it as a QR code. Your wallet scans it, shows you which domain is asking, and, once you unlock, signs the challenge with a key that never leaves your device. The site verifies that signature against the DigiByte address your wallet reports and signs you in as the owner of that address. There is no password to remember or store, nothing to phish, and no identity provider in the middle.

The scheme descends from BitID, the 2014 Bitcoin sign-in protocol, and was adopted for DigiByte as Digi-ID in 2018. It is deliberately small: one URI format, one signed-message scheme, one callback. That is what makes it easy to implement on both sides. DigiScope uses Digi-ID as one of its three sign-in methods, and the DigiByte Android wallet can sign in to DigiScope with a single tap without any QR code at all, because a native app can be the browser and the wallet at once.

This hub collects everything DigiScope knows about Digi-ID. Start with the concept lesson to understand the four steps and why they are safe. Then, if you are building, the two integration guides walk through DigiScope’s own server implementation and the Android wallet’s client implementation, with the real code and the traps each side has to avoid. Reading is free; signed-in members can take the check at the end of each lesson to earn DGB.

Frequently asked questions

What is Digi-ID?
A passwordless login for websites: your DigiByte wallet signs a one-time challenge and the site verifies the signature against your address. No password is created or stored anywhere.
Does the website learn my private key?
No. A signature proves you hold the key without revealing it. The site learns only your DigiByte address.
Which wallets support Digi-ID?
The DigiByte Android wallet handles digiid:// QR codes and links, and can sign in to DigiScope with one tap. Developers can test a server with DigiByte Core’s signmessage command, which uses the same signed-message scheme.
Can a captured login be replayed?
No. Each login uses a fresh random nonce that the server marks spent on first valid use, and the signed URI names the exact site the signature is for.
Can I add Digi-ID to my own site or wallet?
Yes — the two integration guides on this page walk through DigiScope’s server implementation and the open-source Android wallet’s client implementation, with code.
Digi-ID at a glance The website issues a one-time challenge as a QR code. The wallet signs it with a key that never leaves the phone and posts only the signature. The server recovers the address from the signature and starts a session. Your website 1. mint a random nonce 2. show it as a QR code 5. verify the signature 6. start a session digiid://…?x=<nonce> DigiByte wallet 3. scan, show the domain 4. sign the URI private key never leaves the phone unlock: PIN or biometric QR carries only the URI + nonce POST { uri, address, signature } no password, no shared secret, one use per nonce
Digi-ID at a glance

Sign in with Digi-ID

Learn Digi-ID

Build with Digi-ID

  • Add Digi-ID login to your app (server side) — Issue a one-time challenge, render it as a QR, verify the wallet’s signature in the right order, hand the browser exactly one session, and sweep expired rows — walked through DigiScope’s own code.
  • Handle digiid:// in your wallet — Parse the URI, confirm the domain, choose a legacy or per-site SLIP-0013 identity key, sign with DigiByte’s message prefix and a compressed key, and post the callback — from the open-source DigiByte Android wallet.