[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"project-80602":3},{"id":4,"name":5,"fullName":6,"owner":7,"repo":5,"description":8,"homepage":9,"htmlUrl":10,"language":11,"languages":10,"totalLinesOfCode":10,"stars":12,"forks":13,"watchers":14,"openIssues":15,"contributorsCount":15,"subscribersCount":15,"size":15,"stars1d":15,"stars7d":15,"stars30d":16,"stars90d":15,"forks30d":15,"starsTrendScore":15,"compositeScore":17,"rankGlobal":10,"rankLanguage":10,"license":10,"archived":18,"fork":18,"defaultBranch":19,"hasWiki":20,"hasPages":18,"topics":21,"createdAt":10,"pushedAt":10,"updatedAt":42,"readmeContent":43,"aiSummary":44,"trendingCount":15,"starSnapshotCount":15,"syncStatus":45,"lastSyncTime":46,"discoverSource":47},80602,"Crypto-Casino-Game","Sealva-Devs\u002FCrypto-Casino-Game","Sealva-Devs","Online Web3 Crypto Casino Platform - Crash, Jackpot, Roulette, Slot, Coinflip, Mine, Poker. It is designed for fast gameplay, real-time community, and serious risk control – without sacrificing developer friendliness.","",null,"TypeScript",62,35,1,0,72,4.67,false,"main",true,[22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"betting","casino","coinflip","crash","crypto-game","dice","gambling","game","gamify","gaming","jackpot","minegame","multi-chain","online-game","p2e","p2p","poker","slides","web3","web3-games","2026-06-12 02:04:04","# Crypto Casino Gaming Platform - Crash, Roulette, Jackpot, Coinflip, Mines ...\n\nWelcome to Crypto Gaming Hub, a modern cryptocurrency casino gaming platform. This platform offers multiple provably fair games including Coinflip, Crash, Mines, and Roulette.  \n  \n[Live link](https:\u002F\u002Fwww.bet366.casino\u002F)  \n\n\u003Cimg width=\"1912\" height=\"909\" alt=\"Screenshot_29\" src=\"https:\u002F\u002Fgithub.com\u002Fuser-attachments\u002Fassets\u002Fa0b5933b-6626-494e-a80d-346f6572059b\" \u002F>\n*Main dashboard showing all available games*\n\n## Overview\n\nREST and real-time backend for a crypto-enabled betting platform. The design prioritizes low-latency gameplay, real-time collaboration, and operational controls, while remaining straightforward to run and extend locally.\n\nThis repository contains the **public core**: shared API, persistence, authentication, Socket.IO, and notifications. **Payment processing** and **bot service** modules are not included; they are distributed separately. The architecture diagram below illustrates the full system so integrations points are visible.\n\n---\n\n## Architecture\n\n| Layer | Responsibility |\n|--------|----------------|\n| **API** | Express.js REST: authentication, users, games metadata, history, admin |\n| **Real-time** | Socket.IO for live game state, chat, and dashboards |\n| **Games** | Crash, Mine, Roulette, Coinflip, and related engines ship with the **private** backend. In this public build, game HTTP routes and game Socket.IO handlers are **disabled** |\n| **Data** | MongoDB (users, balances, bets, history, notifications, configuration) |\n| **Security** | JWT, wallet signatures, validation, rate limiting |\n| **Notifications** | Email (EmailJS) and in-app notifications |\n\n**Premium \u002F private (not in this repo):** blockchain settlement, deposit and withdrawal flows, autonomous bot players, and extended risk or treasury automation.\n\n### System diagram (full vision, including premium modules)\n\n```mermaid\ngraph LR\n  Client[Frontend] --> API[Express API]\n\n  API --> Auth[Auth]\n  API --> Games[Game Engines]\n  API --> Chat[Chat]\n  API --> Admin[Admin Panel]\n  API --> Notif[Notifications]\n  API --> WS[Socket.IO]\n  API --> DB[(MongoDB)]\n\n  %% Premium \u002F private modules (not in this repo)\n  subgraph PremiumModules[Premium Modules]\n    Pay[Payment Service]\n    Bots[Bot Service]\n    Risk[Risk & Treasury Alerts]\n  end\n\n  API --> Pay\n  Games --> Bots\n  Risk --> DB\n  Pay --> Risk\n```\n\nIn this shared backend you deploy the core API, MongoDB, EmailJS, and Socket.IO. Premium layers attach at the integration points shown above.\n\n---\n\n## Tech stack\n\n- **Runtime:** Node.js  \n- **HTTP:** Express.js  \n- **Database:** MongoDB, Mongoose  \n- **WebSocket:** Socket.IO  \n- **Auth:** JWT, wallet signatures, optional Supabase  \n- **Email:** EmailJS  \n- **Hardening:** Helmet, CORS, rate limiting  \n\n---\n\n## Prerequisites\n\n- Node.js 16 or later  \n- MongoDB (local or hosted), e.g. `mongodb:\u002F\u002Flocalhost:27017\u002Fyour_db_name`  \n\n---\n\n## Quick start\n\n### 1. Install dependencies\n\n```bash\nnpm install\n```\n\n### 2. Configure environment\n\n```bash\ncp env.example .env\n```\n\n**Minimum for local development**\n\n- `MONGODB_URI` — connection string  \n- `FRONTEND_URL` — frontend origin for CORS (e.g. `http:\u002F\u002Flocalhost:3000`)  \n- `JWT_SECRET` — set in `.env` (not committed); use a strong value outside development  \n\nPayment and bot-related variables are **not** required for this build.\n\n### 3. Start the server\n\n```bash\nnpm start\n```\n\n**Note:** The public release may ship with compiled output under `build\u002F` while TypeScript sources for private game engines under `src\u002F` may be absent.\n\n- Prefer **`npm start`** when working from this repository as distributed.  \n- `npm run dev` and `npm run build` may fail without the full private source tree.  \n- Maintainers with the complete codebase can use `npm run dev` as usual.\n\nThe server listens over HTTP (HTTPS is not configured in this shared build). The listening port is `PORT` from `.env` (default example: `3001`).\n\n### 4. Verify health\n\nOpen `http:\u002F\u002Flocalhost:3001\u002Fhealth`. Expected response shape:\n\n```json\n{ \"status\": \"OK\", \"timestamp\": \"...\" }\n```\n\n---\n\n## Environment variables\n\nTreat `env.example` as a template only; never commit production secrets.\n\n### Core\n\n| Variable | Required | Description |\n|----------|----------|-------------|\n| `MONGODB_URI` | Yes | MongoDB connection string |\n| `PORT` | No | HTTP port (default often `3001`) |\n| `NODE_ENV` | No | `development` or `production` |\n| `FRONTEND_URL` | Recommended | Primary frontend origin (CORS) |\n| `ADMIN_FRONTEND_URL` | No | Admin UI origin (CORS) |\n| `ALLOWED_ORIGINS` | No | Additional comma-separated CORS origins |\n\n### Authentication and rate limiting\n\n| Variable | Notes |\n|----------|--------|\n| `JWT_SECRET` | Required for production; dev fallback exists but must not be used in production |\n| `RATE_LIMIT_WINDOW_MS`, `RATE_LIMIT_MAX_REQUESTS` | General API rate limits |\n| `AUTH_RATE_LIMIT_WINDOW_MS`, `AUTH_RATE_LIMIT_MAX_REQUESTS` | Auth route limits |\n\n### Email and application identity\n\n- `EMAILJS_SERVICE_ID`, `EMAILJS_PUBLIC_KEY`, `EMAILJS_PRIVATE_KEY`  \n- `EMAILJS_OTP_TEMPLATE_ID`, `EMAILJS_VERIFICATION_TEMPLATE_ID`, `EMAILJS_WELCOME_TEMPLATE_ID`  \n- `APP_NAME` — branding in email and UI copy  \n\nIf EmailJS is not configured, email features log warnings and skip delivery.\n\n### Supabase (optional)\n\n`SUPABASE_URL`, `SUPABASE_ANON_KEY`, `SUPABASE_SERVICE_ROLE_KEY` — used by `supabaseAuth` middleware. Omit if Supabase is unused.\n\n### Solana and treasury (private \u002F full builds)\n\n- `NETWORK` — e.g. `devnet`  \n- `TREASURY` — treasury key material (highly sensitive; never in public repos or real values in samples)  \n\n### Logging and alerting\n\n`MB_LOG_LEVEL`, `MB_LOG_MAX_FILES`, `MB_LOG_FLUSH_MS`, `MB_LOG_HOOK_LEVEL`, `SLACK_WEBHOOK_URL`, `TELEGRAM_BOT_TOKEN`, `TELEGRAM_CHAT_ID`, `DISCORD_WEBHOOK_URL` — structured logging and optional alert hooks.\n\n### Admin bootstrap\n\n- `ADMIN_BOOTSTRAP_TOKEN` — one-time token for initial admin creation  \n- `ADMIN_EMAIL`, `ADMIN_USERNAME`, `ADMIN_DISPLAY_NAME` — defaults for the bootstrap user  \n\nRotate or discard `ADMIN_BOOTSTRAP_TOKEN` after use in production.\n\n---\n\n## Premium modules (outside this repository)\n\nThe following are **not** part of the public codebase but are referenced in the diagram for integration planning:\n\n- **Payments** — gateways, webhooks, deposit and withdrawal tracking, reconciliation, on-chain mapping; credentials such as `NOWPAYMENTS_*`, `CRYPTOPAY_*`, and RSA material belong only in private configuration.  \n- **Bot service** — configurable automated players for load and game-specific strategies; isolated from the public demo build.  \n\nBusiness-specific compliance, treasury policy, and provider choice remain in private deployments; this repository provides the auditable API and real-time core.\n\n---\n\n## Security: full \u002F private builds\n\nDo not publish the following in public repositories or shared sample environments:\n\n- **Secrets:** `JWT_SECRET`, `ADMIN_BOOTSTRAP_TOKEN`, `TREASURY`, Supabase service role key, payment API keys, EmailJS private key, bot-related keys.  \n- **Operational data:** production `MONGODB_URI`, production URLs, internal admin endpoints, webhook signing secrets.  \n\nThe public core does not require payment or bot secrets to run locally.\n\n---\n\n## Support\n\nIf you have any questions or would like a more customized app for specific use cases, please feel free to contact us at the contact information below.\n\n- Telegram: [@devsealva](https:\u002F\u002Ft.me\u002Fdevsealva)\n\n---\n\n**Happy Gaming! 🎰🎮💎**\n","这是一个基于Web3的在线加密货币赌场游戏平台，提供包括Crash、Jackpot、Roulette等多种公平证明游戏。项目采用TypeScript编写，核心功能包括低延迟的游戏体验、实时社区互动以及严格的风险控制机制，同时保持了对开发者友好的特性。技术栈方面，使用了Node.js作为运行环境，Express.js处理HTTP请求，MongoDB与Mongoose进行数据存储，并通过Socket.IO实现即时通讯。此外，还集成了JWT和钱包签名等安全措施来保障用户信息的安全。该平台适用于希望快速搭建或扩展加密货币博彩服务的场景，尤其是那些重视玩家体验与安全性并重的应用场合。",2,"2026-06-11 04:01:21","CREATED_QUERY"]