Wallet
Connect a signer so the broadcast console can sign state transitions on your behalf.
The explorer never persists your keys. Imported keys stay in this tab's memory. Disconnect, inactivity (> 10 minutes hidden), or reload clears the local signer. An operation already in progress can retain signing material until it finishes. Mnemonic and WIF fields are cleared after each connection attempt. JavaScript cannot guarantee that every copy of a secret is erased from memory.
Drop in the key-backup JSON file you exported from the bridge, or paste the JSON below. Keys live only in this tab's memory.
Drop backup JSON here or click to pick a file
File stays local — never uploaded.
…or paste JSON
Extension signing is unavailable for SDK operations in this explorer. Use a bridge backup, mnemonic, or WIF signer whose private keys match enabled on-chain identity keys.
Paste a BIP-39 mnemonic and the identity ID it controls. The seed lives only in this tab's memory. We use DIP-13 account 0 by default; enter the exact path used by your wallet if it differs. The derived key must match an enabled on-chain key.
Paste a single WIF-encoded private key plus the identity ID it controls. For one-off operations only; treat it like a burn credential.
Need an identity?
Identities are created in the Dash Platform bridge — it converts L1 DASH into Platform credits and registers the identity. Open the bridge and choose Create New Identity. Come back with the backup JSON and drop it in the import box above.
Bridge: bridge.dashhq.org. For a top-up, choose Manage Identity, then Top Up Identity, and enter your identity there.