Upstream docs: https://learn.robosats.com/
Everything not listed in this document should behave the same as upstream RoboSats. If a feature, setting, or behavior is not mentioned here, the upstream documentation is accurate and fully applicable.
RoboSats is a peer-to-peer Bitcoin exchange over Lightning. This package runs the self-hosted client, not a coordinator. The client connects to RoboSats coordinators over Tor to facilitate P2P Bitcoin trades.
- Image and Container Runtime
- Volume and Data Layout
- Installation and First-Run Flow
- Configuration Management
- Network Access and Interfaces
- Actions (StartOS UI)
- Backups and Restore
- Health Checks
- Dependencies
- Limitations and Differences
- What Is Unchanged from Upstream
- Contributing
- Quick Reference for AI Consumers
| Property | Value |
|---|---|
| Image | recksato/robosats-client |
| Architectures | x86_64, aarch64 |
| Entrypoint | Default upstream entrypoint |
| Volume | Mount Point | Purpose |
|---|---|---|
main |
/root |
Client data, robot tokens |
| Step | Upstream | StartOS |
|---|---|---|
| Installation | Docker or hosted client | Install from marketplace or sideload .s9pk |
| Tor setup | Manual Tor proxy configuration | Auto-configured via Tor dependency |
| First use | Open web UI, generate robot | Same — open web UI and generate robot |
No setup wizard or credentials needed. The client is ready to use immediately after install.
| Setting | Value | Purpose |
|---|---|---|
TOR_PROXY_IP |
tor.startos |
Tor SOCKS proxy address |
TOR_PROXY_PORT |
9050 |
Tor SOCKS proxy port |
All configuration is done through the RoboSats web interface:
- Robot identity generation
- Order creation and management
- Coordinator selection
| Interface | Port | Protocol | Type | Description |
|---|---|---|---|---|
| Web UI | 12596 | HTTP | ui | RoboSats client interface |
None. All interaction is through the web interface.
Included in backup:
mainvolume — robot tokens and client state
Restore behavior:
- All data is restored
- No reconfiguration needed
Important: Your robot token is your identity. Back it up to recover active orders.
| Check | Display | Method | Messages |
|---|---|---|---|
| Web Interface | "Web Interface" | HTTP check (/selfhosted) |
"The web interface is ready" / "The web interface is not ready" |
| Property | Value |
|---|---|
| Service | Tor (tor) |
| Required | Yes |
| Version constraint | >=0.4.9.5 |
| Health checks | tor must pass |
| Mounted volumes | None |
| Purpose | Private connections to RoboSats coordinators |
All coordinator communication happens over Tor for privacy.
- Client only — This is the web client, not a coordinator; you connect to external coordinators.
- Requires Lightning wallet — Need an external Lightning wallet to send/receive payments.
- Tor latency — All traffic routed through Tor may be slower than clearnet.
- Coordinator trust — Must trust coordinators for escrow; client doesn't run its own.
- Full RoboSats client functionality
- Robot identity system
- Order book access
- Lightning escrow trades
- Multi-coordinator support
- Privacy features (Tor-only, no KYC)
See CONTRIBUTING.md for build instructions and development workflow.
package_id: robosats
image: recksato/robosats-client
architectures:
- x86_64
- aarch64
volumes:
main: /root
ports:
ui: 12596
dependencies:
- tor
startos_managed_env_vars:
- TOR_PROXY_IP
- TOR_PROXY_PORT
actions: none