Job Description

Responsibilities

• This ensures security while enabling seamless integration into our Laravel-based Back Office system
• You will develop a separate High-Low game backend and frontend
• It must be built on a provably fair gaming system using blockchain/cryptographic verification
• It will interact with our casino platform via Laravel APIs
• All game transactions will be recorded in our existing Back Office
• Real-time WebSockets will be used for price updates & bet execution
• High-performance & ultra-low latency implementation is required
• Develop a standalone High-Low betting module (backend + frontend)
• Implement real-time price updates using Binance WebSocket API
• Build a scalable WebSocket server (Node.js + Redis) to handle thousands of users
• Implement betting logic (users place HIGH/LOW bets on live crypto prices)
• Ensure fair bet settlement based on final price at the end of each round
• Implement provably fair gaming using cryptographic verification (e.g., SHA-256, Ethereum smart contracts, or Chainlink VRF)
• Securely integrate with our Laravel-based iGaming platform via APIs:
• Validate user authentication
• Check & update player balances
• Store bet transactions & results in Back Office
• Ensure the game runs at maximum speed, even under high traffic loads
• Optimize WebSocket connections to prevent lag & ensure ultra-low latency
• Develop a React.js frontend matching our casino UI/UX
• Ensure secure, fair, and high-performance game logic
• Write clean, modular, and well-documented code
• Redis – For caching and pub/sub communication
• PostgreSQL / MySQL – Database for storing bets & transactions
• Security Best Practices – Prevent exploits, fraud detection
• To ensure this, the developer must implement:
• WebSockets Optimization (High-Speed Real-Time Connections)
• Redis Pub/Sub will be used for real-time bet updates
• Must implement automatic failover to Chainlink Price Feeds or CoinGecko API in case Binance goes down
• Prices must be cached in Redis for instant access to reduce API latency
• Failover & Auto-Scaling
• Develop the standalone High-Low betting module
• Ensure API-driven architecture (no direct casino access) Implement real-time WebSockets for price updates
• Build & optimize betting logic with provably fair verification
• Deliver clean, scalable, and secure code
• Optimize for ultra-fast performance, scalability, and security

Requirements

• High-Low Game Development Experience (Must Have)
• Provably Fair Gaming Development (Must Have)
• Node.js (Express/Nest.js) – WebSocket Development
• React.js or Vue.js – Frontend UI & WebSocket handling
• Laravel (PHP) – API communication (NO direct casino access, API-only)
• Scalability Knowledge – Handle high-concurrency users (100,000+ active connections)
• Experience with iGaming / Casino Game Development
• Knowledge of Trading Platforms / Forex / Crypto Betting
• Experience with AWS / DigitalOcean for scalable hosting
• Understanding of Chainlink VRF for random number generation
• This game must be ultra-fast and highly scalable
• Must handle 100,000+ concurrent users without lag
• WebSocket connections must be load-balanced using NGINX or AWS ALB
• PostgreSQL/MySQL must be optimized for high-frequency transactions
• Bets should first be stored in Redis before batch-writing to the database every second
• Database partitioning & indexing must be applied to prevent slow queries
• Users must be able to verify the fairness of the game using cryptographic proof
• The game seed must be hashed before the round starts, ensuring that results cannot be manipulated
• Rate-limiting & bot detection must be implemented to prevent abuse
• Game logic must be auditable & verifiable to ensure fairness
• DDoS protection (Cloudflare/AWS WAF) must be in place to prevent attacks
• Must deploy multiple WebSocket servers behind a load balancer
• Game must automatically scale up and down based on traffic demand
• AWS or DigitalOcean must be used for auto-scaling server infrastructure
• API-Driven Integration with Our Platform (Key Requirement!)
• Game data must be logged in our Back Office, so admin staff can view transactions
• Potential for ongoing work: Long-term collaboration possible