Why this system had to exist
I refactored the Playpal77 casino suite to transition it from a fragile, client-calculated setup to a fully server-authoritative, high-performance web platform. The business required an engaging, light-themed casino lobby that looked like playpal77.ph, backed by real-time games (Scatter Slots, Dice, Crash, Plinko) and robust, frictionless blockchain and fiat payment integrations.
I refactored the Playpal77 casino suite to transition it from a fragile, client-calculated setup to a fully server-authoritative, high-performance web platform.
The business required an engaging, light-themed casino lobby that looked like playpal77.ph, backed by real-time games (Scatter Slots, Dice, Crash, Plinko) and robust, frictionless blockchain and fiat payment integrations.
Architecture explorer
Select a layer to inspect the operating shape of the system.
React/Vite Casino Frontend
This layer participates in the wider system boundary described in the story above, connecting runtime behavior, user-facing interaction, and safety constraints into one deployable stack.
Before / after transformation
The outcome is easier to feel when you switch between baseline and optimized states.
Game Calculation
Client-calculated (insecure)
Optimized resolution
100% Server-authoritative RNG
What shipped
Authoritative 5x3 slot engine and Plinko, Crash, Dice arcade games running on Node.js server
Real-time event broadcasting and persistent wallet state synchronization using Socket.io and SSE
Secure payment processing gateway for Metamask blockchain and PIX transactions in PHP API
Automated Android TWA decompilation, drawable hot-fixing, and aapt2 compiler build script
