Hierarchical Betting Exchange Software Build

I’m commissioning a full-featured betting exchange that runs on a Super Master → Master → Agent → User hierarchy. Each level must be able to create and manage the tier directly beneath it, with every transaction automatically mirrored in a tight, tamper-proof ledger. Commissions, credit limits, exposure, and profit-and-loss should all roll up in real time so upper tiers always see an up-to-the-second snapshot of their network’s risk. At launch the platform must cover three market types: sports match betting placed before kick-off, live in-play sports markets, and virtual casino games such as roulette and slots. Odds, limits, and settlements need to refresh instantly once results are known, so users can keep betting without lag. Cash handling is manual for now. Deposits and withdrawals are requested by the user, queued for the relevant Agent’s approval, and only reflected in a wallet after that sign-off. No direct bank or card processing is required in this phase, but the database should be ready to add automated gateways later. Because the exchange will run continuously, I expect a modular back-end—micro-services or equivalent—that can scale horizontally. WebSocket or similar push technology is essential for live odds, while REST or GraphQL endpoints will drive the dashboards. A lightweight admin panel that lets me audit ledgers, force settlements, and freeze accounts rounds out the first milestone. Deliverables • Production-ready back-end code with unit tests • Normalised database schema and migration scripts • API documentation sufficient for front-end teams to plug in immediately • Basic web admin interface for hierarchy management, manual cash approvals, and real-time reporting • Deployment instructions for a Linux environment (Docker or bare metal) Acceptance criteria • Any bet placed, settled, or voided is reflected throughout the hierarchy within two seconds. • Ledger totals for every level match an independent reconciliation script run against raw bet logs. • Role-based access controls ensure that no tier can view or edit data above its clearance. If you’ve built real-time financial or gaming systems before and can walk me through the architectural choices you’d make here, I’d like to see a concise proposal and a rough timeline for the first deployable version.