Local devnet

Run a full Stacks blockchain locally with optional auto-deploy

Run a complete Bitcoin and Stacks development environment locally with Docker.

Contents

• Requirements
• Start devnet
• Auto-deploy
• Pre-funded accounts
• Development workflow
• Stop devnet
• When to use devnet
• Limitations

Requirements

Requirement	Notes
Docker Desktop	Installed and running
Clarinet	3.21+
RAM	8 GB+ recommended

Verify with:

stacksdapp doctor

Start devnet

stacksdapp dev

This starts:

• Bitcoin node
• Stacks node
• Frontend at http://localhost:3000
• File watcher for auto-regeneration
• Chain health monitoring (prefixed [dev] logs)

Deploy contracts in a second terminal once the node is ready (~30s):

stacksdapp deploy --network devnet

Auto-deploy

Deploy once the local chain is healthy. No second terminal required.

stacksdapp dev --auto-deploy

The supervisor waits for the devnet node, then runs deploy automatically.

Pre-funded accounts

Devnet includes pre-funded accounts in contracts/settings/Devnet.toml:

[accounts.deployer]
mnemonic = "twice kind fence tip hidden tilt action fragile skin nothing glory cousin green tomorrow spring wrist shed math olympic multiply hip blue scout claw"
balance = 100000000000000

[accounts.wallet_1]
mnemonic = "sell invite acquire kitten bamboo drastic jelly vivid peace spawn twice guilt pave pen praise pork crisp unite giggle laundry steel scout cycle marry"
balance = 100000000000000

These are public burner mnemonics for local use only. The CLI prints a safety warning. Never reuse them on testnet or mainnet, and never commit real deployer seeds.

No real STX or external wallet is required for basic debug UI flows on devnet.

Development workflow

• Edit .clar files. Bindings regenerate automatically.
• ABI cache in contracts/.cache/ skips unchanged work.
• Deploy with --auto-deploy or stacksdapp deploy --network devnet.
• Test with pre-funded accounts.

Stop devnet

stacksdapp clean

Stops services and removes generated and devnet state.

When to use devnet

• Complex multi-contract interactions
• Bitcoin-specific features (sBTC, block data)
• Offline development
• Full stack simulation

Limitations

• Slower than testnet (Docker overhead)
• No real economic incentives
• Limited to local machine