Network

Public Miden testnet services — explorer, RPC, faucet, remote prover, and status. The canonical live inventory lives at status.testnet.miden.io; the page below is an editorial overview that won't go stale as new endpoints ship.

Devnet

The same services exist on devnet under the devnet subdomain — e.g., status.devnet.miden.io, faucet.devnet.miden.io, devnet.midenscan.com. Swap testnet → devnet in any URL on this page to point at devnet instead.

Authoritative · Live

Testnet status ↗

Dashboard showing every public Miden testnet endpoint with live health checks. Bookmark this when something looks off — it's the source of truth for "is the network up."

→Explorer · Testnet

MidenScan (block explorer) ↗

Search by account ID, transaction ID, note ID, or block height. The verification surface referenced throughout the tutorials.

→

Developer endpoints

Submit · Query

RPC

gRPC endpoint the node exposes for submitting proven transactions and querying account / note / block state. Clients connect here by default; see status.testnet.miden.io for the current URL.

Test assets

Faucet ↗

Dispenses test assets (testnet MID and fungible test tokens) to the account ID you specify. Open faucet.testnet.miden.io to mint, or check the status page for the current endpoint.

→

Delegated proving

Remote prover

Off-loads proof generation to a hosted prover when the client doesn't have the compute for client-side proving. Opt in via the client's proverUrl option.

MidenScan

Block explorer

Same as the top-right card — included here so the developer-endpoint view is complete.

→

Canonical URLs live on the status page

Hard-coding testnet URLs in client configs is fine for demos, but the Miden ops team moves endpoints as new nodes come online. For anything production-ish, keep your configuration loading the current URLs from status.testnet.miden.io or the client's default (which tracks the canonical testnet host).

Typical flow

1. 01

   Install the toolchain — midenup pulls the client, CLI, and compiler in one step. See Installation.

2. 02

   Point the client at testnet — default config targets the testnet RPC, so miden new projects work out of the box.

3. 03

   Top up with the faucet — mint testnet assets to your account ID before attempting transactions.

4. 04

   Submit + verify — send a proven transaction via the RPC; watch the account and transaction IDs land on MidenScan.

5. 05

   Offload proving if needed — the remote prover URL is configurable if client-side proving isn't feasible (mobile, low-power clients).

Related

Tutorial

Deploy your first contract

End-to-end walkthrough — client → RPC → MidenScan verification.

→Architecture

Miden node

How the node receives transactions, aggregates batches, and produces blocks.

→