docs(09): canonical arena URL is now https://botfights.archipelago-foundation.org (user-created DNS+NPM+LE)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
This commit is contained in:
archipelago 2026-07-30 21:46:39 -04:00
parent 2ec9a70dfd
commit 4f51de9f81

View File

@ -22,7 +22,8 @@ BotFights is a standalone app (separate repo) distributed to Archipelago nodes a
BOT-03 is built and DOCUMENTED as a decentralized "arena = nostr relay" model, per project philosophy:
- **Any node can host a public arena** — it is the same app image; a public arena is just a BotFights instance without `ARENA_UPSTREAM_URL` that others point at.
- **Each node chooses its arena community** via `ARENA_UPSTREAM_URL` (env/manifest); unset = standalone.
- **The Foundation's VPS2 arena (`http://146.59.87.168:9100`) is only the well-known default**, like the vps2 FIPS anchor — a rendezvous, not an authority. Nothing in the code hardcodes a center.
- **The Foundation's VPS2 arena is only the well-known default**, like the vps2 FIPS anchor — a rendezvous, not an authority. Nothing in the code hardcodes a center.
- **Canonical arena URL (updated 2026-07-30, supersedes the plain-IP decision): `https://botfights.archipelago-foundation.org`** — the user created the DNS A record + NPM proxy host + Let's Encrypt cert mid-execution. TLS is live and verified; `TRUSTED_PROXY=1` enabled on the arena. Raw fallback `http://146.59.87.168:9100` still works. `ARENA_UPSTREAM_URL` in the manifest (09-06) and all docs/prompt examples use the HTTPS domain.
- The game UI is always served from the user's own node; only match/fighter state lives on the chosen arena.
- The unified AI prompt + docs (BOT-02) and `docs/arena-deployment.md` MUST present it this way, including "how to host your own arena" as a first-class section.
- Later phase (roadmap note): nostr-event-based fighter/arena discovery across multiple arenas.