Files
archy/apps/qortal/ui/qortal.png
ssmithxandClaude Opus 5.5 9fa58ef6a8 qortal: companion status UI, pasta network, spike-measured sizing
Companion UI: nginx inside the qortal image serves apps/qortal/ui on
12390 (gated, now interfaces.main): sync height vs best peer, chain/QDN
peers, version/uptime, Hub connection URL and a gateway launcher. Its
/core/ proxy is a GET-only allowlist of four public Core endpoints and
never carries the API key. start.sh supervises Core + nginx and exits
when either dies; SIGTERM reaches Core (clean shutdown in ~7s).

Spike findings on archy-x250-pa3:
- network: pasta. On a rootless bridge every forwarded connection
  appears to come from the container's own IP, so inbound p2p peers
  would all look identical; Core needs no other app.
- API whitelist off + apiRestricted pinned true (start.sh refuses
  otherwise). Forwarded connections arrive from a dynamic address no
  static whitelist can name; the key guards every state-changing route.
- Bootstrap + sync: 6.8 GB, ~17 min. QDN capped at 20 GiB via
  maxStorageCapacity; storage 40Gi.

API key reveal deliberately left out: the UI cannot verify the
dashboard session from a container, and the gate may be switched to
open at runtime.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-20 01:08:13 +00:00

47 KiB
256x256px