91appe.bet backend — internal docs
-- reference / read-only --

How the schema actually works, then every table in it

The diagram below shows the real mechanism — how a bet, a deposit, or a withdrawal moves through the database. The reference underneath lists all 104 tables individually, grouped by function, each with its original obfuscated name for traceability.

Money & data flow

Three user-initiated flows (deposit, bet, withdraw) all read and write the same wallet balance. Game settlement runs on its own clock, independent of any single user request, and feeds results back into the bet a player already placed.

Player (app) submits deposit proof places a bet requests withdrawal deposit_transactions was: thevani bets_wingo_1min × 16 game/duration variants withdrawal_transactions was: hintegedukolli withdrawal_bank_accounts was: khate payout destination Cron scheduler every 1 / 3 / 5 / 10 min round_sequence_wingo_1min generates period no. · × 16 variants RNG / blockchain hash → outcome results_wingo_1min × 16 variants settles bet: outcome + payout user_wallets.balance was: shonu_kaichila.motta credits on approval debits stake on placement credits payout on win debits on approval
Deposit, bet, and withdrawal are three independent request flows that all ultimately read or write user_wallets.balance. Game settlement (teal path) is decoupled from the request that placed the bet — it runs on a cron schedule and writes back into the same bet row once a round resolves. The same shape repeats for WinGo, 5D, K3, and TRX games at 1/3/5/10-minute durations — 16 near-identical copies of the bet/round/result trio.