Every score is proven.
When SOL is on the line, nothing is taken on faith. Every gameplay result is validated server-side before it can touch the leaderboard or the payout. Here is the full pipeline, all fifteen layers of it.
Layer Group 01
Identity: who gets on the board.
Before a single zombie falls, the pipeline establishes exactly who is playing and makes it expensive to pretend otherwise.
Cryptographic Identity
Authentication is an Ed25519 signature from the player's Solana wallet. The signed message includes a single-use, server-issued nonce with a short expiry, preventing replay attacks. The verified public key is the sole identity used for ranking and reward settlement. Scores cannot be submitted on behalf of another wallet.
Token-Holding Requirement
Ranked play requires a minimum $15 position in $DBG, verified on-chain at session start and re-verified at intervals during play. Every extra account costs capital, which scales directly against Sybil attacks and wallet farms.
Layer Group 02
The run: scored by the server, not the client.
Final scores are never accepted as client claims. Every run is tracked, timed and audited from the first round to the last.
Server-Authoritative Scoring
Each run is registered server-side the moment it begins, and all progress is evaluated against server-recorded state and timestamps. The client has no mechanism to write to the leaderboard, directly or indirectly.
Continuous Run Telemetry
The game client reports every round transition to the server in real time, producing a timestamped event trail for the full run. A final score without a complete corresponding trail is rejected outright.
Temporal Trail Analysis
At submission, the trail is audited: round transitions must be strictly ordered and separated by intervals consistent with actual wave completion. Burst-injected telemetry, out-of-sequence events and trails that end below the claimed round are all rejection conditions.
Elapsed-Time Validation
Total run duration is checked against a per-round minimum derived from gameplay mechanics. A claimed round count that could not physically fit inside the measured wall-clock duration is rejected.
Statistical Plausibility Envelopes
Points and kill totals are bounded by the maximum possible output of the wave composition for the claimed round count. Submissions exceeding these envelopes are flagged automatically.
Progression by Elimination Only
Rounds advance only when every zombie in the active wave is eliminated. Exploiting unreachable positions does not advance rounds and therefore cannot generate leaderboard progress.
Layer Group 03
The board: one wallet, one verified best.
What survives validation still has to earn its place, and everything that gets flagged is thrown out in public view.
One Ranked Entry Per Wallet
The daily leaderboard records each wallet's single best run per UTC day, selected server-side. Duplicate and superseded runs are excluded from ranking automatically.
Hard Exclusion of Flagged Runs
Flagged runs are excluded at the database-query level from both the public leaderboard and payout winner selection. Exclusion is structural: no manual review or override step exists between flagging and denial.
Public Enforcement Log
All flagged submissions are published daily, including the wallet, linked X account, claimed round and the specific rejection reason. Enforcement is fully transparent and independently observable.
Device Correlation Analysis
Each run stores a salted one-way hash of client metadata, with no personal data retained. Correlated patterns across multiple wallets, such as coordinated farming, are detectable and actionable from this evidence.
Layer Group 04
The payout: verifiable to the last lamport.
The same rigor continues after the board locks. Settlement is atomic, auditable and public.
On-Chain Settlement Transparency
Daily rewards are settled as individual Solana transactions per recipient. All transaction signatures are published with Solscan references, making every payout independently verifiable on-chain.
Idempotent Settlement Ledger
A persistent ledger finalizes each payout day atomically. Re-execution, process interruption or restart cannot produce duplicate settlement; an interrupted distribution resumes only for unsettled recipients.
Key Isolation
The settlement wallet's private key lives in encrypted secret storage, accessible exclusively to the scheduled settlement process. It is never exposed to the web-facing application layer, request logs or client code.
Why this matters.
A daily SOL pool only means something if the board it pays is honest. Every layer above exists so that the only way to rank in DEAD BLOCK is to actually survive the rounds. Fabricated scores fail validation, farms bleed capital, and every denial and every payout is published where anyone can check it.
Read the rest of the system.
Anti-cheat is one pillar of the Play2Earn engine. See how the daily pool fills, how the top 30 split it, and where $DBG fits in.
Earn it or don't rank.
The pipeline doesn't negotiate. Survive the rounds and the board is yours.