# Architecture

**Frontend**: Next.js, SSR for SEO, typed API client; wallet adapters (EVM first).\
**Backend**: TypeScript/Node with CQRS; Redis for sessions/queues; Postgres for ledgers.\
**Contracts**: EVM (BSC) for token & game settlement; proxy pattern w/ multisig.\
**RNG**: Commit–reveal for fast rolls; VRF (weekly jackpots).\
**Analytics**: Event pipeline → warehouse → public dashboards (transparency).\
**Infra/Sec**: Cloudflare, WAF, 2FA, secrets vault, least‑privilege IAM.

## Data Transparency

* Public dashboards for bankroll, payouts, RTP by game, treasury flows.
* Open APIs for community "+EV" tooling and odds verification.

## Provably Fair & Security

* **RNG:** commit–reveal per roll; periodic VRF‑secured jackpots.
* **Audits:** third‑party smart‑contract audit(s) pre‑mainnet; web security review.
* **Bug Bounty:** continuous public bounty (scope: contracts, game logic, auth).
* **Custody:** isolated hot wallets, limited hot balances; cold storage for treasury.
* **Key Mgmt:** multisig for upgrades/treasury; break‑glass procedures.
* **Monitoring:** anomaly detection, PnL drift alarms, AML red‑flag rules.
