14 Min. Read+ 100 Exp

Wallets, keys, and testnet

Handle keys safely and get the testnet funds the next lessons need.

Learning objectives

By the end of this lesson, you will be able to:

  • back up a seed phrase and say what it lets you recover;
  • explain what a private key controls, and what losing one costs;
  • choose testnet over mainnet while your app is still under development; and
  • get free testnet Dash from a faucet, ready for the next lesson.

A wallet is a set of keys

You met the wallet in module 6 as the software that holds your keys. Here is the part that matters for money. A wallet does exactly two essential jobs: it works out public keys and addresses so other people can pay you, and it keeps the matching private keys so you can spend what arrived. The Dash itself never lives inside the wallet — it is a record on the shared ledger. The wallet's value is that only its holder can move that record.

That is why the private key is the root of control. The public key is computed from the private key, and the address is computed from the public key. Everything flows down from that one secret, so whoever holds the private key can spend whatever the address receives.

A mental model

The address is your public mailbox: anyone can drop Dash into it. The private key is the only key that opens the mailbox. Guard the key, not the mailbox.

Seed phrases

If your wallet held a pile of unrelated keys, every single one would need its own backup. It does not. One phrase recovers the entire wallet.

That phrase is the seed phrase (also called a mnemonic): a string of 12 to 24 ordinary words such as "rifle adjust ..." that your wallet generates the first time you set it up. The words are not arbitrary — they encode 128 to 256 bits of random data. Word count tracks that length: 128 bits makes 12 words, 160 makes 15, 192 makes 18, 224 makes 21, and 256 makes 24. With an optional extra password, the phrase is hashed into your wallet's 512-bit root seed — a standard called defines exactly how words turn into that seed, the single source every later key is derived from.

Because the seed phrase reproduces the root seed, the seed phrase is the backup. Anyone who can read twelve words owns everything those words derive. Treat it the way you would treat the money itself:

Guard the phrase

Write the seed phrase down and keep it offline. Never type it into a website, send it in a chat, or store it in a screenshot or password manager that syncs. Any app, person, or site that asks for it can spend your funds — legitimate software never needs it.

Derivation

The root seed expands into the whole wallet through derivation: computing each key and address from the one before, along a fixed path. Because every step is deterministic, the same seed always produces the same keys and addresses, in the same order. That is what makes a single backup sufficient: reinstalling your wallet and giving it the same phrase rebuilds the same wallet, address by address.

Derivation follows standards so that different programs agree with one another. describes how one seed grows the key tree, and lays out where standard money addresses sit in that tree. A receiving address, for instance, sits at a path written something like m/44'/1'/0'/0/0 on testnet and m/44'/5'/0'/0/0 on mainnet — the slashes are steps through the tree, exactly the way a file path walks a folder structure. The 1' or 5' near the start is the coin type, the step that names which network you are on, which is one reason the same seed produces different addresses on testnet than on mainnet.

One seed, two jobs

As module 6 previewed, the same seed phrase also derives your identity keys — the keys that own your data on Dash Platform. You do not hand-craft that part either: the Dash SDK performs the derivation for you from the same phrase. Back up once, and you have covered both.

What a private key controls (and what losing it costs)

A private key has one job, and it is absolute: it spends the at its address. When you send Dash, the wallet produces a signature with the private key, and everyone else checks that signature against the matching public key. No other action can move those funds, but the matching private key is the only thing that can.

That power has no safety net. There is no "forgot your key" link and no reset, because no company is in charge of the ledger. If you lose the private key — or leak it to someone else — the funds it controls are gone, both for you and for everyone else, permanently. The docs put it plainly: a key that is generated, used, and then lost before it is backed up leaves the stored duffs "likely lost forever."

This is the whole reason the seed phrase matters. The seed phrase can regenerate the private key, so the phrase is the backup for the key. Lose the phrase and the key, and nothing brings either back.

No recovery path

Test this rule on testnet before it ever matters on mainnet: send worthless coins, delete the key, and watch that the funds cannot be recovered. The habit — back up first, use second — is the point.

Testnet versus mainnet

Dash runs as two separate networks, and every lesson from here uses both of them in different roles.

Mainnet is the real network. The Dash on it has real value, and moving it has real consequences — so it is the wrong place to learn, experiment, or test.

Testnet is a near-identical copy that runs on coins with no real-world value. You can fund it, break it, and start over without risking anything, because the coins are worthless. It exists precisely so developers can practice on the real thing before touching real money.

MainnetTestnet
Coins have value?Yes — real DashNo — worthless test Dash
Use it forSending and receiving real moneyDeveloping, testing, and breaking things
Cost of a mistakeReal, permanent lossNothing but time

A few differences to remember. Testnet and mainnet are separate chains: coins do not move between them, so you can never accidentally "promote" testnet Dash to mainnet. Testnet also relaxes some checks and may be reset at any time when the network needs a fresh start. Dash Platform runs its own testnet — about 150 plus and , operated by Dash Core Group — so you get the full stack to practice against.

The workflow this course follows: do everything on testnet while you build, and treat mainnet as the place your finished app eventually runs.

Getting testnet Dash from a faucet

Testnet coins are worthless, which means you get them for free. A faucet is a service that dispenses them: you provide an address, and it sends you some test Dash. There is nothing to buy and nothing at stake.

That free test Dash is what the very next lesson needs. To create an identity and start using Dash Platform you must first fund it, and that funding comes from these faucet coins.

Which address do you give the faucet?

You give the faucet the address you intend to spend from. The exact address type — and the step of deriving and funding it — belongs to the next lesson, so for now it is enough to know that a faucet sends test Dash to an address you provide.

Point a browser at the Dash Platform testnet faucet:

One warning: faucets are a convenience, not a guarantee. They move, get rate-limited, or go down, and the exact URL changes from time to time. If that link is down, the Dash Core Group maintains its own faucet at https://testnet-faucet.dash.org/ as an alternative, and the latest address is listed in the Dash developer docs.

Checkpoint

Pass the quiz to complete the lesson.

Knowledge check

Restoring your progress…

4 correct to pass

What you accomplished

You can now treat keys the way an operator, not a tourist, does. You know a wallet is just its keys, that one seed phrase recovers the entire wallet through deterministic derivation, and that a private key is the single thing that spends the Dash at an address — so losing or leaking either it or the phrase means losing the funds forever. You can tell mainnet from testnet and choose testnet while you develop, and you know to get free testnet Dash from a faucet. That fund is the last missing ingredient before you fund a Platform address and create your first identity.