Files
smirk-backend-core/examples/paid-access
jwinterm a455c60ed0 docs: operator console guide + fix example recipes + document all env vars
- New docs/operations/CONSOLE.md: reaching /admin, NIP-98 login, the
  defaults->env->DB precedence model, per-section runtime-safe vs
  restart-required table, expected_versions concurrency, restart_apply_mode
  (with the systemd Restart=always requirement for auto), clearing a DB
  override. Linked from README + OPERATOR_SETUP.
- All six example recipes gained an explicit chain-enablement block
  (FEATURE_XMR/WOW on, BTC/LTC/GRIN off) so they no longer hard-fail
  Config::validate in production (default-on chains with empty sources).
- Documented all 16 previously-undocumented env vars in .env.example
  (RESTART_APPLY_MODE, TOR_ADMIN_ONION, DEPLOYMENT_MODE, TIP_SHARE_BASE_URL,
  ...); RELAY.md gained the premium-post policy + RELAY_WRITE_ALLOWLIST_NPUBS;
  ADMIN_PUBKEYS noted as reserved/inert.
2026-07-19 15:52:07 -04:00
..

paid-access — a paid hosted wallet backend

A one-time fee gates creating a NEW wallet (existing wallets and self-hosters bypass it). Non-custodial and pull-model: the backend only reads invoice status, and funds go straight to your own wallet.

  • Config: .env.example — REGISTRATION_REQUIRE_PAYMENT=true + the PAYMENT_* processor block (BTCPay-compatible; also served by xmrcheckout / wowcheckout). Price is fiat-denominated, payable in any coin the processor offers.
  • You are a merchant, not a money transmitter — you sell access to your service and never hold user funds. Have clear Terms (what the fee buys, refunds, fair use), treat the fees as income, and see ../LEGAL_AND_OPS.md.
  • PAYMENT_CONFIRMATIONS >= 1 (0-conf lets a paid invoice be reversed after signup).