How bustabit/v1-gameserver works
Project type and purpose
• Project type: Backend service (no bundled frontend)
• Purpose: Run a provably-fair bitcoin betting game. It exposes HTTP/WebSocket endpoints, manages game logic, records history in Postgres, and interacts with the Bitcoin network (via RPC or Coinbase APIs) and BIP32 keys.
File structure
Top-level files:
– server.js (entry point: boots HTTP & WebSocket servers, loads modules)
– populate_hashes.js (precompute commitment hashes script)
– config files: nodemon.json, .gitignore, cert.pem/key.pem (SSL)
– package.json (dependencies, start script)
server/ folder modules:
– config.js (env var loader: DATABASE_URL, BIP32_DERIVED_KEY, COINBASE_*)
– database.js (Postgres client wrapper)
– bitcoin_client.js (RPC or Coinbase API handler)
– game.js (core game rules, spin/wager logic)
– game_history.js (logs results, queries/stores in DB)
– socket.js (WebSocket routes & event broadcasting)
– lib.js (utility functions)
– sorted_array.js (data structure for game odds or bet ordering)
README
• Stack: Node.js + Postgres + BIP32 key + optional Coinbase APIs
• Runtime: npm start → server listens on port 3841
• Setup: env vars for DB & external keys, DB schema in server/schema.sql
• No frontend; clients connect via HTTP/WebSocket