Credit deposits at deposit_confirmations and verify the round's coins with the quorum before paying (B-82, DEP-03, DEP-04, DEP-09, DEP-12, DEP-14, ELC-17, ELC-27, RND-21, RND-22, RND-25, RND-39, DAT-10, DAT-11, DAT-24, DAT-62, DAT-67, DAT-68, AUD-12, AUD-44, AUD-45, API-30, API-31, API-36, ADR-06, ADR-52)

A user could bet and then double-spend the 1-conference deposit that funded the bet with a
private chain: the bet left the chain but its participant stayed `confirmed`, and the payout
failed "insufficient pool UTXOs" for ever with everyone else's money stuck. Coinbase outputs
were also credited at 1 confirmation (maturity is 120).

Deposits
- `round_config.deposit_confirmations` (default 6, 1-100, editable from /admin) is the
  threshold for a deposit; an output of a platform transaction (any txid of a
  pending_transactions row, RBF versions included) keeps 1; a coinbase output needs 120,
  recognised from the raw transaction, which must hash to the txid (`is_coinbase`, cached).
  `read_deposit_policy` / `classify_new_deposits` run between the read and the write, so no
  session is open across the lookup.
- The quorum must also place the coin deep enough on our own tip (ELC-17).
- Confirmed outputs short of their threshold are pending deposits (memory only, replaced at
  every refresh): shown in `pending_balance_sats` / `has_pending` (also for DEP-13's withdrawal
  message), never spendable. No scripthash notification announces a maturing deposit, so each
  new block refreshes only the users that have one, one task per user (DEP-09 now says so).

Payout
- `_trigger_payout` verifies the round's confirmed participants' bet outputs with the other
  servers (`verify_pool_outpoints`: strict majority of >= 2 answers per outpoint, a
  mempool-only coin or a tie gives no verdict) and builds from exactly those outpoints
  (RND-22), never from whatever else sits at the address. No quorum: `payout_failed`, `pool
  verification unavailable`, nothing changes. Bets that are gone become `reorged_out`, one
  `participant_reorged_out` row each, `pool_amount_sats` rewritten (only downward) in the same
  transaction, and the 70/30 split is computed on what is left.
- Winner's own bet gone: nothing is built; `rounds.payout_blocked_at` (Alembic f2c64a8d1e93,
  with `deposit_confirmations`, plain add_column) is set, `payout_blocked` and the pause with
  `paused_reason = 'payout_blocked'` are written in one transaction; `POST /admin/resume` clears
  the mark and the next attempt verifies again. /admin/rounds returns it.
- Rounds opened before B-80 (pool = the shared reserve address) keep the old active-server
  `listunspent` choice, since that address holds no single round's bets.

Ambiguities resolved: the winner's row stays `confirmed` while held (AUD-45 says every
participant whose bet is gone becomes `reorged_out`, but OPS-30/DAT-68 need the verification to
repeat after the resume, which only a `confirmed` row allows); `/`'s deposit hint no longer says
"1 confirmation" (7 languages, same keys); guides updated.

Tests changed because the spec changed: listener tests that credited height-100 coins at tip 0
now set a tip past every threshold; the payout fixtures seed confirmed participants (the new
source of the inputs) instead of an active-server `listunspent`, FakeNetwork answers the
verification, and test_round_pool_address asserts the quorum is asked about the round's
address. New: thresholds at exactly 6/5, configured value, coinbase at 119/120 and a mismatching
or missing raw tx, platform outputs at 1, dust, quorum height, waiting-deposit display and
disappearance, block-triggered refresh, resume, verification verdicts, gone bets excluded with
the split recomputed, winner gone held and paused, held payouts untouched until the resume,
re-verification after it, no quorum, a payout with 1 and with 400 participants against
reserve+fee+dust, admin config bounds and migration. Mutation-checked: threshold 1, ignored
coinbase, no height bound, no verification and no winner hold each fail tests.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

docs/api.md

@@ -577,7 +577,7 @@ esiste una API separata per l'amministrazione, solo un'autenticazione diversa.
   `app/rounds/service.py:round_deadline`, `app/rounds/service.py:winner_share`,
   `app/rounds/service.py:rounds_can_open` ·
   *Test:* `tests/unit/test_rounds_route.py`
-  *Stato:* da implementare (B-82, B-95), per i campi marcati · *Oggi:*
+  *Stato:* da implementare (B-95), per i campi marcati · *Oggi:*
   `bet_amount_sats` è sempre il costo configurato.
 
 #### GET /rounds/stream
@@ -760,8 +760,7 @@ dei parametri operativi in
     "draw_confirmations", "max_round_pool_sats", "paused", "paused_reason"}`.
   *Codice:* `app/api/routes/admin.py:read_config` ·
   *Test:* `tests/unit/test_admin.py`
-  *Stato:* da implementare (B-82, B-95) · *Oggi:* mancano
-  `deposit_confirmations` e `max_round_pool_sats`.
+  *Stato:* da implementare (B-95) · *Oggi:* manca `max_round_pool_sats`.
 
 #### PUT /admin/config
 
@@ -778,7 +777,7 @@ dei parametri operativi in
     | `fee_rate_sat_vb` | 1 – 10 000 (`MAX_FEE_RATE_SAT_VB`) |
     | `rbf_timeout_seconds` | 60 – 604 800 |
     | `draw_animation_seconds` | 0 – 600 |
-    | `deposit_confirmations` | 1 – 100 — *da implementare (B-82)* |
+    | `deposit_confirmations` | 1 – 100 |
     | `draw_confirmations` | 1 – 20 |
     | `max_round_pool_sats` | `0` (disattivato), oppure da `bet_amount_sats` a 4 000 000 000 000 000 — *da implementare (B-95)* |
 
@@ -803,9 +802,9 @@ dei parametri operativi in
   *Codice:* `app/api/routes/admin.py:update_config`,
   `app/api/routes/admin.py:RoundConfigUpdate` ·
   *Test:* `tests/unit/test_admin.py`
-  *Stato:* da implementare (B-82, B-95), per i due campi nuovi e la copia
+  *Stato:* da implementare (B-95), per `max_round_pool_sats` e la copia
   all'apertura di costo ed `fee_address` · *Oggi:* sono accettati i primi
-  otto campi.
+  nove campi.
 
 #### POST /admin/pause e POST /admin/resume
 
@@ -834,9 +833,6 @@ dei parametri operativi in
   *Codice:* `app/api/routes/admin.py:pause_lottery`,
   `app/api/routes/admin.py:resume_lottery` ·
   *Test:* `tests/unit/test_admin.py`, `tests/unit/test_pause_reason.py`
-  *Stato:* da implementare (B-82), per l'azzeramento di `payout_blocked_at` ·
-  *Oggi:* `rounds.payout_blocked_at` non esiste ancora; le pause automatiche
-  esistenti sono solo `resurrected_tx`.
 
 #### GET /admin/users
 
@@ -893,8 +889,7 @@ dei parametri operativi in
     completa di un round è in [API-45](#get-roundsround_idproof).
   *Codice:* `app/api/routes/admin.py:list_rounds` ·
   *Test:* `tests/unit/test_admin.py`
-  *Stato:* da implementare (B-82), per `payout_blocked_at` · *Oggi:*
-  la lista si ferma a `bump_reserve_sats`.
+
 
 #### GET /admin/audit-log