archy/testnet/README.md

89 lines
2.5 KiB
Markdown
Raw Normal View History

release(v1.7.41-alpha): post-OTA auto-rollback so a bad release cannot strand the fleet Closes failure mode FM5 from docs/bulletproof-containers.md: the v1.7.38 + v1.7.39 rollouts left every affected node on an unreachable UI (nginx 500) with no recovery path short of SSH. This release adds a self-check guardrail to the update flow. What changed: - apply_update() writes a pending-verify marker with old+new version and a 150s deadline immediately before scheduling the service restart. - verify_pending_update() runs from main.rs startup. If the marker is present and within its freshness window, the new binary waits 15s for nginx + backend to settle, then probes https://127.0.0.1/ every 5s for up to 90s (self-signed certs accepted). - On any probe success within the window, the marker is cleared and nothing else happens. - On window-exhaust, the new binary: 1. Moves the broken /opt/archipelago/web-ui to web-ui.failed.<ts> (quarantined, not deleted, so we can post-mortem). 2. Restores web-ui.bak on top of web-ui. 3. Calls rollback_update() to restore the previous binary. 4. Updates state.current_version to reflect the rollback. 5. systemctl --no-block restart archipelago so the OLD binary boots. - Markers older than 10 minutes are treated as stale and cleared without probing, so a crashed-during-startup marker from weeks ago cannot spontaneously roll back a healthy node on a later reboot. - rollback_update() binary copy now goes through host_sudo instead of tokio::fs::copy, so it escapes the service's ProtectSystem=strict mount namespace. Without this, the rollback silently failed with EROFS on /usr/local/bin and orphaned the rollback - the exact opposite of what auto-rollback is for. Tests: 4 new unit tests in update::tests covering marker round-trip, absent-marker noop, no-panic on verify_pending_update with nothing to verify, and an invariant assert that the 90s probe window stays below the 600s stale threshold. All passing. Side fix: scripts/create-release-manifest.sh was dying with exit 141 (SIGPIPE from tar tvzf pipe head pipe awk) under set -euo pipefail. Replaced with a single awk NR==1 that doesn't short-circuit the upstream pipe, so the release-build flow is idempotent again.
2026-04-22 16:14:35 -04:00
# Lightning Testnet Stack (Signet)
Real Bitcoin signet + LND + ThunderHub + Fedimint for testing Lightning features.
## Quick Start
```bash
docker compose -f docker-compose.testnet.yml up -d
```
First run takes ~10 minutes for signet blockchain sync (~200MB).
## Access
| Service | URL | Credentials |
|---------|-----|-------------|
| ThunderHub | http://localhost:3010 | password: `thunderhub` |
| Fedimint Guardian UI | http://localhost:18175 | — |
| LND REST API | http://localhost:8080 | — |
| Bitcoin RPC | localhost:38332 | user: `bitcoin` / pass: `bitcoinpass` |
## Get Signet Coins
1. Get a new address: `docker exec archy-lnd-signet lncli --network=signet newaddress p2wkh`
2. Visit https://signetfaucet.com and paste the address
3. Wait for 1 confirmation (~10 min)
4. Check balance: `docker exec archy-lnd-signet lncli --network=signet walletbalance`
## Open a Lightning Channel
```bash
# Connect to a signet peer (example: ACINQ signet node)
docker exec archy-lnd-signet lncli --network=signet connect 03...@signet-node:9735
# Open channel (amount in sats)
docker exec archy-lnd-signet lncli --network=signet openchannel --node_key=03... --local_amt=100000
```
Or use ThunderHub's UI at http://localhost:3010 to manage channels visually.
## Create & Pay Invoices
```bash
# Create invoice
docker exec archy-lnd-signet lncli --network=signet addinvoice --amt=1000 --memo="test payment"
# Pay invoice (from another node or ThunderHub)
docker exec archy-lnd-signet lncli --network=signet payinvoice <bolt11>
```
## Useful Commands
```bash
# Node info
docker exec archy-lnd-signet lncli --network=signet getinfo
# List channels
docker exec archy-lnd-signet lncli --network=signet listchannels
# Check Bitcoin sync progress
docker exec archy-bitcoind-signet bitcoin-cli -signet -rpcuser=bitcoin -rpcpassword=bitcoinpass -rpcport=38332 getblockchaininfo
# View logs
docker compose -f docker-compose.testnet.yml logs -f lnd-signet
docker compose -f docker-compose.testnet.yml logs -f thunderhub-signet
# Stop everything
docker compose -f docker-compose.testnet.yml down
# Reset all data (fresh start)
docker compose -f docker-compose.testnet.yml down -v
```
## Architecture
```
bitcoind-signet (port 38332)
↓ RPC + ZMQ
lnd-signet (gRPC 10009, REST 8080, P2P 9735)
↓ macaroon + TLS
thunderhub-signet (web UI on 3010)
bitcoind-signet
↓ RPC
fedimint-signet (Guardian UI on 18175, API on 18174)
```
All containers share the `signet-net` bridge network for internal DNS resolution.