Testnet in the Wallets

1Before you start

Testnet is Divi's practice network: same software, same rules, coins worth nothing. Every IronDivi wallet can run on it, and the IronDivi browser extension even starts there. This page shows the testnet side of each wallet; for what testnet is and how to run your own testnet node, read Get Testnet DIVI first.

You need nothing installed. The web wallet runs in any browser, the Telegram wallet runs inside Telegram, and the extension is still a preview you cannot install yet (see section 3).

2IronDivi Web Wallet

The web wallet is a single page of JavaScript that keeps your keys in the browser and talks to Divi through the public RPC endpoint. There is no account and no server-side wallet: the recovery phrase is the wallet.

Open it on testnet

The network comes from the URL path. Open services.divi.domains/testnet/wallet/ and the header reads IronDivi Web Wallet TESTNET. The mainnet wallet lives at /wallet/ with no badge. There is no switch inside the wallet: to change network you change the URL (the site's top bar has a Switch to Testnet / Switch to Mainnet button that does exactly that).

# what the wallet does on load (divi-wallet/app.js)
const isTestnet = window.location.pathname.includes('/testnet');
const RPC_URLS = {
    testnet: 'https://services.divi.domains/api/testnet/rpc/',
    mainnet: 'https://services.divi.domains/api/rpc/'
};

Create or restore a wallet

1. Under Create New Wallet, pick 12 Words or 24 Words and press Generate New Wallet. Creating a wallet from scratch has its own page, Create a wallet; this one only covers what is different on testnet.
2. The Your Recovery Phrase screen shows the words. Save them in a password manager before you press I've Saved My Phrase: Proton Pass is free; 1Password, Bitwarden, Dashlane, Keeper and Apple Passwords all work too. How and why is in Back up your wallet.
3. The wallet then quizzes you on a few of the words (Check Your Recovery Phrase) and opens the dashboard.
4. To open an existing wallet instead, paste the phrase under Restore Existing Wallet. The field validates as you type ("Valid 12-word phrase") and, with Auto-submit when valid phrase detected ticked, opens the wallet as soon as the phrase checks out. It accepts 12 or 24 words.

On testnet the wallet can also offer to remember the wallet on this device behind an unlock; that offer is deliberately off on mainnet for now.

Faucet, receive, send

1. Press Receive. The panel shows your first address (it starts with x or y) and, on testnet only, a button labelled Request 1000 DIVI from Faucet. Press it: the wallet posts your address to the faucet and reports Received 1000 DIVI! TX: …. About a minute later the balance in the top bar updates; the wallet listens for new blocks over the testnet ZMQ feed, so you don't have to refresh.
2. Press Send. Fill Recipient Address, Amount and Fee, then Send Transaction. A confirmation sheet shows the network line Testnet (test coins, no value) (on mainnet it says Mainnet (real DIVI)), the amount and the real fee before anything is signed.
3. The transaction row links to the explorer. Paste the txid into Explorer 2.0 testnet to watch it confirm (the wallet's own links go to the classic testnet explorer at /testnet/explorer/; both show the same chain).

The Stake button is greyed out: staking in the web wallet is "coming soon". To stake on testnet use an IronDivi node, as in Get Testnet DIVI.

What it talks to

Everything the wallet knows comes from the public, filtered RPC proxy at https://services.divi.domains/api/testnet/rpc/. It is unauthenticated and allows read-only methods plus createrawtransaction and sendrawtransaction, which is exactly what a non-custodial wallet needs: the wallet builds the transaction, verifies the unsigned hex it gets back, signs each input locally, and broadcasts. You can call the same endpoint:

curl -s -X POST https://services.divi.domains/api/testnet/rpc/ \
     -H 'Content-Type: application/json' \
     -d '{"method":"getblockcount","params":[]}'
# {"error":null,"id":null,"result":359941}   (2026-10-21)

curl -s https://services.divi.domains/api/testnet/rpc/   # GET: lists the public methods

The faucet button is one HTTP call, the same one the faucet page makes:

POST https://services.divi.domains/testnet/faucet/api/request
Content-Type: application/json

{"address":"your x… or y… address"}

For a web page that wants the wallet to sign something, the wallet also listens for DIVI_SIGN_REQUEST window messages and answers with DIVI_SIGN_RESPONSE or DIVI_SIGN_CANCEL. That bridge only accepts messages from services.divi.domains and vps1.divi.domains (plus localhost dev ports when the wallet itself runs on localhost). Divi uses its own injected provider and this bridge, not WalletConnect. The full dApp story is in Connect a web page to the IronDivi browser extension.

3IronDivi browser extension (preview)

Unlike the web wallet, one build of the extension serves both networks, and it starts on testnet: the default settings set network: 'testnet', so a fresh install cannot touch real coins by accident.

1. Open the popup. Next to the account name is a Testnet badge; click it and a menu offers Mainnet and Testnet. The same choice is under Settings → Network.
2. Create an account with a password and a 12- or 24-word phrase, or import one. Each network keeps its own accounts, because the derivation path differs: m/44'/1'/0'/0/i on testnet, m/44'/301'/0'/0/i on mainnet.
3. On testnet the popup shows a faucet section (hidden on mainnet). It posts to the same faucet API as the web wallet, and the popup itself waits an hour between requests, which is stricter than the faucet's own 24-hour rule per address.

The extension reads and broadcasts through the same public endpoints as the web wallet (/api/testnet/rpc/ and /api/rpc/) and calls getaddressbalance, getaddressutxos, getaddresstxids, getrawtransaction, sendrawtransaction, validateaddress, getblockcount and getnetworkinfo. Any IronDivi (or legacy divid) node with the address index on can stand in for them.

For web pages it injects window.irondivi (isIronDivi: true) with irondivi_connect, irondivi_accounts, irondivi_getBalance, irondivi_signMessage, irondivi_sendTransaction, irondivi_signRawTransaction, irondivi_getNetwork and irondivi_disconnect; every request is approved in the popup. irondivi_getNetwork is how your page finds out whether the user is on testnet. The API is covered in Connect a web page to the IronDivi browser extension.

4Telegram wallet: /network and /faucet

The IronDivi Telegram wallet is two parts: the bot @divi_wallet_bot, which answers read-only questions in chat, and a Mini App at /telegram/wallet/ that holds the keys on your phone. The bot is non-custodial: it holds no keys and signs nothing. Every chat has its own network setting, and new chats default to mainnet.

1. Open the bot and send /network testnet. It answers:

   Network set to Testnet.
   
   The wallet will open on Testnet (test coins; use /faucet to get some).

   with an Open Wallet (Testnet) button. /network alone shows the current network and a Mainnet / Testnet keyboard; anything else gets Usage: /network mainnet or /network testnet.
2. Press Open Wallet (Testnet). The Mini App opens with a TESTNET badge; /wallet creates a wallet there and /restore restores one. The phrase is generated and typed only inside the app, never in the chat. If you ever paste a phrase into the chat, the bot deletes it and tells you to treat it as compromised.
3. Copy a receiving address from the app and send /faucet y… (your address). The bot asks the faucet for you and replies:

   Faucet (Testnet): sent 1000 DIVI to y…
   TX: https://services.divi.domains/testnet/explorer/tx/…

   If the faucet says no, the reply is Faucet (Testnet): followed by the faucet's own message (the cooldown and limit messages are listed in Get Testnet DIVI).
4. Check with /balance y…, or inside the app, whose Receive panel has the same Request 1000 DIVI from Faucet button as the web wallet.

The Mini App also has its own Mainnet / Testnet switch in a strip under the balance; switching clears the screen, shows Scanning testnet…, rescans the addresses for that network and remembers the choice. Like the other two wallets it derives testnet keys at coin type 1' and mainnet at 301', so one phrase serves both networks without mixing funds.

Like the web wallet, staking in the Telegram wallet is "coming soon"; use an IronDivi node for that.

5The three wallets side by side

All three are IronDivi wallets and agree on the chain parameters, which also match C++ Divi's CTestNetParams.

Because the paths agree, you can open the same phrase in any of the three (or in an IronDivi node) and see the same testnet coins. For scripting against the chain directly, see Talk to a Divi node from Python and JavaScript.

6Send the coins back

Faucet coins are shared. When you are done, send what you have left to the faucet's return address from the wallet's Send panel, leaving a little for the fee:

yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4

In the Telegram chat, /send yJehBfdK9KbrwPRjYrzkrPES9uG5nFLjY4 999.9 opens the app with the payment filled in for you to confirm.

If something goes wrong

The faucet's own refusals (24 hours per address, 2 per network per day, daily budget) are explained in Get Testnet DIVI. Still stuck? Ask the Divi chatbot, or see all tutorials.