archipelagoandClaude Opus 5
c966395eb9
Found while checking whether the /lnd-connect-info leak (a05956c4) was also reachable over Tor. It was not — but only by accident, and the accident was one app id away from failing. auto_add_tor_service() creates a hidden service for a freshly installed app, mapping onion:80 -> 127.0.0.1:<the app's host port>. It skips the node's own service and is_protocol_service() — which names the DAEMONS (bitcoin, bitcoin-knots, electrs, electrumx, lnd) but NOT their UI sidecars. lnd-ui and bitcoin-ui are real, installable app ids (apps/lnd-ui, apps/bitcoin-ui) whose host ports are 18083 and 8334: exactly the two ports that served the admin macaroon and the credential-injecting Bitcoin RPC proxy. So nothing structural prevented either from acquiring a GLOBAL onion as a silent side effect of being installed — re-exposing worldwide, and persistently, whata05956c4had just closed to mesh/LAN peers. Verified on a live node that this has not fired (services.json maps lnd to 8080 and holds no *-ui entry, and the running torrc contains neither port), so this closes a latent hole rather than an active one. The gate gets its own named predicate rather than an addition to is_protocol_service, because the two express different things: is_protocol_service says "this speaks a wire protocol, not HTTP", while never_auto_onioned says "this fronts the node's money and must not be published unasked". Conflating them would have made the fix look like a classification tweak. This gates only the AUTOMATIC path. An operator who deliberately enables Tor for one of these apps still can — that is an informed choice, not a silent default. Both endpoints are session-gated at the backend as ofa05956c4either way. Compile-checked clean. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Archipelago
Self-sovereign Bitcoin node OS and manifest-driven app platform.
Archipelago is a bootable personal server OS for Bitcoin infrastructure,
self-hosted apps, mesh communication, decentralized identity, and federation.
Apps are packaged as declarative manifest.yml files and run as rootless
Podman containers managed by the Rust backend.
What is here
core/- Rust workspace: backend API, container runtime, security, OpenWrt helpers, and performance/resource management.neode-ui/- Vue 3 + TypeScript frontend.apps/- app manifests and custom app container sources.docker/- supporting container build contexts for UI companion surfaces.image-recipe/- bootable image/ISO build inputs.Android/- Android companion app.scripts/- development, release, deployment, and validation tooling.docs/- architecture, app packaging, operations, API, and roadmap docs.
Platform model
Archipelago is built as a developer-ready app platform, not a fixed appliance:
- Apps are declared in
apps/<app-id>/manifest.yml. - The Rust parser in
core/container/src/manifest.rsis the canonical schema. - The orchestrator compiles manifests to rootless Podman/Quadlet runtime state.
- App data lives under
/var/lib/archipelago/<app-id>/. - Secrets are generated or read from
/var/lib/archipelago/secrets/and injected through Podman secrets rather than static environment values. - Release and app catalogs are signed and verified against a pinned trust anchor.
Start with:
- Architecture
- Developer Guide
- App Developer Guide
- App Manifest Spec
- Nostr Git Source Hosting Plan
- Operations Runbook
- Troubleshooting
Quick start
Frontend
cd neode-ui
npm install
npm start
The dev UI runs at http://localhost:8100 with a mock backend on :5959.
Backend
cd core
cargo build
cargo test --all-features
Linux is the supported backend runtime and release-build target. macOS is fine for frontend work and many Rust compile/test loops, but host integration tests that touch Podman, systemd, networking, or image build paths require Linux.
App manifests
./scripts/validate-app-manifest.sh apps/filebrowser/manifest.yml
python3 scripts/generate-app-catalog.py
python3 scripts/check-app-catalog-drift.py --release --strict
scripts/generate-app-catalog.py requires Python with PyYAML installed.
Documentation map
| Doc | Purpose |
|---|---|
| Architecture | System layers, crates, data paths, security model |
| Developer Guide | Local setup, code workflow, testing |
| API Reference | JSON-RPC API overview |
| App Developer Guide | How to package and test apps |
| App Manifest Spec | Manifest schema and validation rules |
| Nostr Git Source Hosting Plan | ngit/NIP-34 contribution workflow and maintainer model |
| Apps README | Packaged app catalog overview |
| Image Recipe | Bootable image build flow |
| Operations Runbook | Production operations and recovery |
| Open Source Readiness | Public-release cleanup checklist |
| Roadmap | Shipped, in-progress, and planned work |
| Unified Task Tracker | Launch hardening task list |
| Archive | Historical plans, audits, and handoffs |
Contributing
Read CONTRIBUTING.md before opening a pull request. For security issues, follow SECURITY.md and do not open a public issue.
License
Archipelago is licensed under the MIT License. Third-party notices are listed in NOTICE and generated license inventories in component release artifacts.