Practical overview
When it fits
Use arkd when developing or evaluating server-side infrastructure for an Arkade instance and its off-chain Bitcoin transactions. Its documented alpha status makes the project's production-use warning important to consider.
Who it is for
- Operators running an Arkade instance
- Developers building server-side Bitcoin execution applications around Arkade
- Teams evaluating Arkade infrastructure in local or test-network environments
Documented uses
- Create and manage batch outputs through Bitcoin transactions
- Facilitate off-chain transactions between users
- Provide liquidity for commitment transactions that settle batches on-chain
- Set up a local regtest development environment for arkd
Requirements & limits
The repository is public and specifies an MIT license. Its README provides release-binary installation instructions and Docker package links.
- The README marks the software alpha, experimental, and not for production use.
- Supported Bitcoin networks listed in the README include regtest, testnet3, signet, mutinynet, and mainnet.
- Configuration supports PostgreSQL, SQLite, or Badger for the main database; PostgreSQL or Badger for event storage; and Redis or in-memory live storage.
- The documented wallet setup includes signer configuration, wallet unlocking, on-chain BTC funding, and a wait of at least two confirmations.
- Local development requires Go 1.26 or later and Nigiri.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up an arkd wallet and prepare it for operation
Follow the documented startup and wallet-funding sequence for an arkd instance.
Before you start
- arkd and arkd-wallet installed and configured
- A configured wallet signer or custom signer, unless loading a signer during setup
- BTC for the on-chain wallet address
Steps
Start arkd-wallet, then start arkd.
Create a wallet with a password or restore one using a mnemonic and password.
If neither the wallet nor a custom signer is configured as signer, load the signer before unlocking the wallet.
Unlock the wallet, generate a funding address, send BTC to it, and wait for at least two confirmations.
Expected outcome
A funded, unlocked arkd wallet prepared for use by the server.
Guide limitations
- The README identifies arkd as alpha software and says not to use it in production.
- Signer loading may need to be repeated at each restart unless the required environment variables are exported.
Prepare a local regtest development environment
Set up the documented prerequisites and start arkd in local development mode.
Before you start
- Go version 1.26 or later
- Nigiri
- The arkd repository
Steps
Start the local Bitcoin environment with
nigiri start.Clone the arkd repository and change into its directory.
Download Go dependencies with the command below.
go mod downloadStart the wallet using the command below or the command below, then start arkd with the command below or the command below.
make run-walletmake run-wallet-nosignermake run-lightmake run
Expected outcome
The documented local regtest services and arkd development process are started.
Guide limitations
- The README notes that wallet startup also starts PostgreSQL and NBXplorer services from
docker-compose.regtest.yml. - The README advises using
make docker-stopto tear down the development environment. - The project is alpha software and is not recommended by its README for production use.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 14 October 2026
- Original website title
- arkade-os/arkd · Official homepage title · retained in its source language

