Contact person: Business Client

Phone:Show

Email:Show

Location: Ethiopia

Budget: Recommended by industry experts

Time to start: As soon as possible

Project description:
"Project Overview: Real-Money Multiplayer Game Casino App
This project involves developing a high-security, real-time multiplayer gaming platform that integrates several classic games (Chess, Checkers, Ludo, and a Card Game) with a real-money betting and wallet system.
Critical Note: This application operates as an online casino. All development must prioritize security, transaction integrity, anti-cheat measures, and compliance with relevant iGaming regulations (e.g., KYC, AML, licensing). The business entity is responsible for securing all necessary legal licenses before the monetary features are fully implemented.
________________________________________
1. Phase 1: Core User & Financial System (Backend Priority)
1.1 User Authentication & Security
• Sign-Up/Login: Standard email and password authentication. Must include strong password hashing (e.g., bcrypt) and JWT tokens for secure session management.
• Security: Implement Two-Factor Authentication (2FA) as a mandatory or highly encouraged feature for all users, especially for financial transactions.
• KYC/Age Verification: System must be designed to integrate with a third-party KYC service for identity and age verification, which is required for real-money gambling.
1.2 The Financial Wallet System
• Digital Wallet: Each user must have a secure, unique internal money wallet.
• Ledger System: The wallet must be managed by an immutable transaction ledger (like a double-entry accounting system) to log every deposit, withdrawal, bet, win, and rake deduction. This is essential for auditing and financial integrity.
• External Integration: The system needs APIs to integrate with payment gateways (e.g., Stripe, PayPal, Binance pay, Bybit pay or specialized iGaming payment processors) for Deposits and Withdrawals.
• Internal Transfer: Users must be able to securely transfer money from their wallet to another registered user's wallet. This must be a logged transaction requiring user confirmation (e.g., password or 2FA).
________________________________________
2. Phase 2: Social & Matchmaking Features
2.1 Friends List & Social
• Friends Management: Users can search for and send Friend Requests to other users via username or email. They can view a list of accepted friends.
• Online Status: Implement a system (using WebSockets) to display the real-time online/offline status of friends.
2.2 Matchmaking System
• Random Match: A service to quickly pair a player with another available random player who has selected the same game and same bet size.
• Private Challenge (Friends): Users can send a game invitation to a specific friend from their list. The invitation should specify the game and the bet amount.
________________________________________
3. Phase 3: Game Logic & Real-Time Play
3.1 Game Authority & Real-Time Engine
• Authoritative Server: The backend server must host the authoritative game logic for all four games (Chess, Checkers, Ludo, Card Game). The client only sends input (a move); the server validates the move, updates the global game state, and broadcasts the new state to all players in that match. This is the primary anti-cheat mechanism.
• Real-Time Tech: Use WebSockets (e.g., [login to view URL], SignalR) for low-latency, bi-directional communication to handle piece/card movements and immediate game state updates.
3.2 Game Setup Parameters
When players enter a match (either random or private), they must agree upon:
• Game Type: Chess, Checkers, Ludo, or Card Game.
• Bet Amount: The amount of money to be wagered by each player.
• Time Per Move: A time limit for each individual move (e.g., 30 seconds, 1 minute). This must be tracked by a server-side timer.
3.3 The Core Logic: Bet Settlement & Payout
This logic is managed by the server's Transaction Manager:
1. Bet Lock: When a game starts, the specified Bet Amount is immediately moved from both players' wallets into a secure, temporary Escrow/Hold state.
2. Game End Triggers: The server determines the loser based on three possible outcomes:
o Normal Loss: Player loses according to game rules (Checkmate, no legal moves, etc.).
o Time Out: The server-side timer expires before a player makes a move. The player is declared the loser.
o Cancellation/Disconnect: If a player cancels the game or their connection drops, they are immediately declared the loser.
3. Payout: Upon determining the winner and loser:
o The total pot (2x Bet Amount) is calculated.
o The Company Rake (a specified percentage, e.g., 5-10%) is immediately deducted and transferred to the Company Wallet.
o The remaining prize money is transferred instantly from the Escrow to the Winner's Wallet.
________________________________________
4. Phase 4: Frontend & User Experience
• Consistent UI/UX: A clean, engaging, and professional user interface that is consistent across all four games.
• Wallet Display: A clear and always-visible display of the user's current wallet balance.
• In-Game Timer: A visual countdown timer that reflects the server-side timer for the "Time Per Move" rule.
• Game History: Users should have a history screen logging all matches played, outcomes, and the associated financial transactions (bets/winnings).






Technology Stack Recommendation (Suggestion)



Component Recommended Technology Rationale
Backend Node.js (Express) or Golang Excellent for scalable, high-concurrency real-time servers.
Real-Time [login to view URL] (with Node.js) The industry standard for reliable, real-time web applications.
Database PostgreSQL (for User/Financial Data) Strong relational integrity, transactional safety (ACID compliance) required for money management.
Caching/State Redis Used for ultra-fast storage of active game sessions, temporary bet escrow, and leaderboards.
Frontend React / Vue (with Canvas/PixiJS) Allows for robust, modular, single-page application development for the casino shell and game views." (client-provided description)