Build on D9
Connect D9 Wallet to your DApp, query on-chain state, and submit finalized transactions.
Connect Your First DAppConfigure the networkChoose an RPC endpoint, set environment variables, and verify the genesis hash.Install the SDKConnect D9 Wallet and read chain state with typed APIs.Work with runtime palletsAssets, AMM swaps, merchant payments, referrals, burn mining, and voting.Copy an exampleReady-to-use TypeScript flows for wallet connection, sign-in, and transfers.
Find a guide by task
Section titled “Find a guide by task”| Task | Guide |
|---|---|
| Authenticate users with D9 Wallet | Sign-In (SIWX) |
| Request and verify an off-chain signature | Sign Messages |
| Submit a transaction and confirm finality | Transactions & Finality |
| Keep wallet state in sync across reloads | Session Lifecycle |
| Convert token decimals and SS58 addresses | Tokens & Addresses |
| Call JSON-RPC methods or runtime APIs | RPC & Runtime APIs |
| List your DApp in D9 Wallet | Publish to DApp Store |
| Deploy and operate a validator node | Deploy a Validator Node |
| Diagnose an error code or failure | Troubleshooting |
Core integration rules
Section titled “Core integration rules”- Never ask for mnemonics, seeds, private keys, or wallet passwords. Private keys remain exclusively inside D9 Wallet.
- Never log pairing URIs, send them to analytics, or embed them in public URLs. Pairing URIs contain sensitive handshake secrets.
- Verify the network using the 32-byte genesis hash, not the WalletConnect chain ID. See Chain Identity.
- Query chain state and estimate fees through your own RPC connection. The wallet connector handles signing sessions only—it does not query chain state.
- Broadcast signed transactions yourself, wait for finalization, and inspect
System::Events. The wallet only signs; a signature alone does not execute on chain.
