diff --git a/docker-compose.arena.yml b/docker-compose.arena.yml index 9a1c06b..51c1a71 100644 --- a/docker-compose.arena.yml +++ b/docker-compose.arena.yml @@ -58,14 +58,22 @@ services: # the host into /opt/botfights-arena/.env (0600, never committed), # same pattern as JWT_SECRET above. - BOTFIGHTS_WALLET_ENCRYPTION_KEY=${BOTFIGHTS_WALLET_ENCRYPTION_KEY} - # Actual money movement is still deliberately NOT enabled (phase 09 - # CONTEXT.md scope fence: "OUT: Lightning/cashu payment changes" — the - # encryption key above only lets per-user wallet strings be stored, it - # doesn't move any funds on its own). A Cashu-based fixed-stake - # ("winner takes all, 21 sats") entry-fee design is being scoped - # separately before any of these are set: - # - BOTFIGHTS_NWC_URL= (the ARENA's OWN wallet — real funds) - # - BOTFIGHTS_CASHU_MINT_URL= + # Mint for the planned Cashu fixed-stake entry fee ("winner takes all, + # 21 sats each, only ever"). Verified live: NUT-4 (mint, bolt11/sat), + # NUT-5 (melt), NUT-7 (spend-check — required to reject an + # already-spent posted token), NUT-11 (P2PK — lets a payout be locked + # to the winner's own pubkey with no interactive receive step). The + # mint's own description: "Do not use with large amounts of ecash" — + # good alignment with the 21-sat cap. Setting this alone moves no + # funds — the existing payout code path (server/src/engine/ + # payments.ts) only reaches its cashu branch from ranked-mode fights, + # which still requires BOTFIGHTS_NWC_URL (unset) to even queue an + # entry fee. The actual "accept a posted token as a stake" capability + # does not exist in the codebase yet — still being scoped, see + # archy's 09-botfights-platform-upgrade/deferred-items.md. + - BOTFIGHTS_CASHU_MINT_URL=https://mint.minibits.cash/Bitcoin + # Still deliberately NOT set — the arena's own real-funds wallet: + # - BOTFIGHTS_NWC_URL= # - BOTFIGHTS_DEV_PAYOUT_LNADDRESS= volumes: