QUANTARA • QUANTUM-RESISTANT L1
Wallet & faucet runbook for Quantara Devnet-0
How to connect a wallet to Quantara Devnet-0, claim QTR (testnet) from the faucet, and safely move tokens around while you build.
Docs • Wallet & Faucet
Wallet & faucet runbook for Quantara Devnet-0
A practical guide for getting a Devnet-0 wallet online, claiming QTR (testnet) from the faucet, and using it safely in demos, tests, and early integrations.
Quantara Devnet-0 uses QTR (testnet) tokens with the same token symbol and decimals we plan for public testnet and mainnet. The difference: Devnet-0 tokens have no real-world value and are meant purely for builders and early validators.
This runbook explains how to connect a wallet, claim from the Devnet-0 faucet, and move QTR between accounts. It's the user-facing counterpart to the RPC guide and Integration guide which cover programmatic access.
Think of Devnet-0 as a rehearsal environment for your users: the flows you build here (connect wallet, receive funds, sign transactions) should translate cleanly to public testnet and, later, mainnet.
All Devnet-0 QTR is non-transferable to future networks and may be wiped or migrated at any time. Never treat Devnet-0 balances as investments or long-term storage.
Devnet-0 snapshot
Last updated: 2025-11-23 22:00 UTC. For the most recent endpoints, faucet status, and wallet releases, always confirm on the Status page.
1 • Concepts
What “wallet” and “faucet” mean on Devnet-0
A Devnet-0 wallet holds QTR test tokens; the faucet is a rate-limited tap for those tokens. Both are for builders, not speculation.
1.1 — Devnet-0 wallets
- • Any Substrate-compatible wallet that supports custom networks and SS58=73 can be used.
- • Our reference UI is the Quantara Wallet for Devnet-0.
- • Wallets talk to Devnet-0 through the same JSON-RPC endpoints described in the RPC guide.
1.2 — Devnet-0 faucet
- • The faucet is a small service that sends QTR (testnet) to eligible Devnet-0 addresses.
- • Reference UI: Quantara Faucet.
- • Requests are rate-limited and may require human checks (e.g., CAPTCHA, waitlist codes).
1.3 — Limits & expectations
- • Faucet grants are sized for testing contracts, apps, and validators — not “airdrop hunting.”
- • Tokens may be reset between Devnet-0 milestones or migrations.
- • We reserve the right to block abusive addresses or IPs to keep the faucet useful for builders.
2 • Wallet setup
Bringing your first Devnet-0 wallet online
The exact UI differs per wallet, but the core flow is the same: install, add an account, and point it at Quantara Devnet-0.
2.1 — Create a Devnet-0 address
- 1) Install your preferred wallet (Quantara Wallet, Polkadot.js extension, or similar).
- 2) Create a new account and securely store the mnemonic phrase. Never share or screenshot this phrase.
- 3) Confirm the address is encoded with SS58=73 when you view it in Quantara tooling.
- 4) Optionally label the account as “Quantara Devnet-0” in your wallet for clarity.
For deeper key-handling guidance, see the Key Management & Backups doc.
2.2 — Point the wallet at Devnet-0
- • Use the Devnet-0 RPC endpoint from this page or the Status page.
- • In many wallets you can add a custom network with name, symbol
QTR, decimals12and the WebSocket URL. - • After saving, confirm you can see basic chain info (name, current block) in the wallet.
- • If the wallet shows the wrong prefix or metadata, refresh the connection or update your wallet version.
If your wallet supports multiple Quantara stages (Devnet-0, public testnet, mainnet later), label each clearly to avoid sending funds to the wrong network.
3 • Faucet
Claiming QTR (testnet) from the faucet
Once your wallet is connected to Devnet-0, use the faucet to request a small QTR balance for testing and development.
3.1 — Prerequisites
- □ A Devnet-0 wallet address with SS58=73.
- □ Ability to sign a simple message (used by some faucets to prove control of the address).
- □ A browser that passes any human checks (CAPTCHA, etc.).
- □ If required, a valid invite or waitlist code for early campaigns.
3.2 — Single faucet claim
- 1) Visit quantarafaucet.com and connect your Devnet-0 wallet.
- 2) Confirm the displayed address matches what your wallet shows (prefix, checksum).
- 3) Complete any human verification (CAPTCHA, social checks, waitlist step).
- 4) Submit the request and wait for the transaction to appear in your wallet and the explorer.
If the faucet request succeeds but you do not see funds, verify that your wallet is still pointed at Devnet-0 and compare the address in the explorer.
3.3 — Fair-use guidelines
- • Request only what you need for current testing.
- • Prefer a small number of well-managed accounts.
- • Avoid automating faucet requests with scripts or bots.
- • For CI or large-scale testing, contact us about alternative funding flows instead of hammering the public faucet.
4 • Moving funds
Sending QTR between accounts & apps
Once you have a balance, you can start exercising the full user journey: transfers, fees, and application calls.
4.1 — Simple transfers
- • Use your wallet to send QTR between your own accounts.
- • Double-check the destination address and network before signing.
- • Expect small transaction fees to be deducted from the sending account.
- • For demos, simulate common scenarios: new user receive, tipping, app-specific flows.
4.2 — Existential deposit & dust
- • Like other Substrate chains, Quantara has an existential deposit (ED) below which accounts may be reaped.
- • Try to keep balances comfortably above ED when testing (wallets may show warnings if you go too low).
- • If an account is reaped, you can recreate it and fund it again with the faucet.
4.3 — App-specific flows
- • Use Devnet-0 to dry-run your application's full transaction flow end-to-end.
- • Log which pallets and calls your app uses, so we can keep RPC and indexing support aligned.
- • For gas/fee-heavy flows, contact us if you need dedicated funding accounts instead of repeated faucet use.
5 • Builders & teams
Using wallets & faucet in teams and CI
Treat Devnet-0 like a shared staging environment: separate human accounts from automation, and keep secrets handled like production.
5.1 — Team accounts
- • Keep personal and team-controlled accounts separate.
- • Store mnemonics in a team password manager or HSM, not in random developer laptops.
- • Document which accounts your app, bots, and validators use.
- • Use labels like “Devnet-0: app hot wallet” inside your wallet UIs.
5.2 — CI & scripted flows
- • Prefer a small number of pre-funded CI accounts over bots hitting the public faucet.
- • Rotate keys occasionally to rehearse production hygiene.
- • Keep Devnet-0 RPC URLs in environment variables so you can swap to public testnet later without code changes.
- • See Integration guide for example CI flows.
6 • Troubleshooting
When wallet or faucet flows misbehave
Most issues fall into a few categories: wrong network, RPC hiccups, rate limits, or browser extensions misbehaving.
6.1 — Common symptoms
- • Wallet shows “disconnected” or can’t fetch chain info.
- • Faucet says “request failed” or “rate limited.”
- • Transactions stay in “pending” for an unusually long time.
- • Balances differ between wallet and explorer.
6.2 — First checks
- • Confirm Devnet-0 is healthy on the Status page.
- • Verify your wallet is using the right network and RPC URL.
- • Compare the address and balance in the explorer.
- • Check the Troubleshooting and Known Issues docs for known patterns.
If you're still stuck, share a concise report in the builder / validator channels: what you tried, which network / address, what you expected, and what you saw instead. Screenshots and explorer links help a lot.
Next steps
From Devnet-0 flows to mainnet-ready UX
If your wallet and faucet flows feel smooth on Devnet-0, you’ve already done the hardest part of user onboarding.
Use this runbook together with the Devnet-0 launch checklist, RPC guide and Integration guide as your toolkit for building and testing on Quantara.
The best early projects are the ones that sweat the basics — clear wallet flows, reliable faucet UX, and predictable transaction behaviour — long before mainnet goes live. Devnet-0 is where we rehearse all of that together.