https://github.com/hirosystems/stacks-testnet-env
https://github.com/hirosystems/stacks-testnet-env
Last synced: 9 months ago
JSON representation
- Host: GitHub
- URL: https://github.com/hirosystems/stacks-testnet-env
- Owner: hirosystems
- Created: 2024-10-10T23:23:30.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2024-10-23T01:53:49.000Z (over 1 year ago)
- Last Synced: 2025-10-14T19:04:35.006Z (9 months ago)
- Language: TypeScript
- Size: 37.1 KB
- Stars: 0
- Watchers: 3
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
# Stacks Testnet Environment
Easily run a Stacks miner in Kypton mode with a signer and Bitcoind testnet instance
# Getting Started
1. Make sure you have Docker and Docker Compose installed and running on your machine.
1. If you already have a generated keychain for the miner and/or the signer, place them in the `keychains` dir in separate YAML files named `miner.yaml` and `signer.yaml`.
1. If you already have chainstate data for bitcoind, stacks core, or the stacks signer, place them in their respective dirs within `chainstate`.
Then run:
```bash
./run.sh
```
This will generate a new set of miner and signer STX/BTC keys if needed, generate miner and signer configs, check the balances of all relevant addresses, assist in funding them if needed, and start all services.
This will output the logs from each service. You can view the logs for a single service with:
```
docker-compose logs
```
Add `-f` to automatically follow new logs. The service names can be found in [./docker-compose.yml](./docker-compose.yml), such as `stacks-node`, `signer`, and `monitor`.
### Shutdown
```bash
./stop.sh
```
### Reset
Warning: Running this script will wipe all local chainstate data, requiring you to re-sync your bitcoin and stacks nodes to chaintip the next time they're booted up.
```bash
./reset.sh
```