unisat-dev-docs

UniSat Wallet dApp Integration Guide

The window.unisat object is injected by the UniSat Wallet extension into every web page. dApps use this client-side provider to interact with the user’s Bitcoin wallet. It is separate from the backend UniSat Open API and does not require an Open API key.

Experimental RGB interfaces are documented separately because they have different method names, amount types, capabilities, and error codes:

Getting Started

  1. Detect the extension
  2. Connect and request accounts
  3. Access account info

Reference

Topic Description
Browser Detection Check if UniSat is installed
Connect Extension Request wallet connection and accounts
Access Accounts Get current account, address, public key
Address Types Supported address formats
Manage Assets Send BTC, inscriptions, Runes, BRC-20
Native RGB API (Experimental) UniSat-specific issuance, receive, payment, and RGB/BTC swap API
WebRGB v1 Provider Standard provider discovery, receive, send, transfer tracking, events, and errors
Manage Networks Switch networks, listen for changes
Derive Context Hash (Experimental) Deterministic secret derivation from wallet seed (experimental)
Sign Message BIP-322 and ECDSA message signing
Sign Transaction PSBT signing and transaction broadcasting
Mobile Integration Deep-link integration for mobile dApps