mirror of
https://github.com/Such-Software/smirk-backend-core.git
synced 2026-10-17 15:31:38 +02:00
jwinterm
d96f457b69
Add ready-to-run .env + README recipes (personal, public-free, friends, paid-access, paid-relay, community) and the premium-relay design overview, with audit fixes to the config template and spec: - Drop the inert INSTANCE_ID knob (config never read it) and document the real per-node id, which is derived from ADMIN_PUBLIC_URL. - Warn that a placeholder PUBLIC_API_URL is rejected at boot in production (Nostr identity is on by default); soften the recipe "boots today" status. - Remove dead template vars: BTC/LTC Core-RPC settings and the non-existent PUBLIC_EXPOSE_FEATURES (replaced with the real per-field landing switches). - Mark ALTCHA_HMAC_KEY conditional in PoW-off recipes; blank placeholder payment creds so a recipe doesn't ship a key that fails validation. - Fix premium-relay spec drift: the migration creates no premium_until index, disabled endpoints return 400/200 (not 404), and neutralize operator voice.
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+ thePAYMENT_*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).