Skip to main content

​
Operator URLs

​
Explorers

Inspect transactions, virtual outputs, and batches:

Bitcoin Explorer

Mutinynet Explorer

Signet Explorer

​
Local Operator

Run arkade-regtest to spin up a Bitcoin regtest network with the Arkade operator, the emulator, a solver (the ghcr.io/arkade-os/solver image), and covclaimd as a Docker Compose stack. Requirements
On Windows, run the commands in PowerShell — no WSL required. The solver and covclaimd profiles pull in the ark and emulator profiles automatically, so the stack brings up the operator and its wallet, the mempool explorer, the emulator, a solver, and covclaimd. start also initializes the ark client against the local operator and seeds it with offchain funds. node regtest.mjs stop stops the services and preserves their data; node regtest.mjs clean removes all containers and volumes. Service ports Point the SDK at http://localhost:7070 to test wallet creation, offchain payments, and unilateral exits without touching public test networks. Create the identity with { isMainnet: false }, and pass arkProvider: new RestArkProvider('http://localhost:7070') to Wallet.create. On regtest, the SDK reads onchain data from the stack’s Esplora API at http://localhost:3000/api by default. Fund your wallet start funds the ark client with 1 BTC. To fund your own wallet, send from the ark client to your wallet’s tark1 address:
--amount is in sats. secret is the default ARKD_PASSWORD. Mine blocks The stack mines one block every 10 minutes. To confirm an onchain transaction or pass a timelock sooner, mine blocks yourself. For example, the unilateral exit delay on this stack is 5 blocks: