惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

小众软件
小众软件
量子位
阮一峰的网络日志
阮一峰的网络日志
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
美团技术团队
J
Java Code Geeks
Apple Machine Learning Research
Apple Machine Learning Research
腾讯CDC
V
Visual Studio Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
博客园 - 三生石上(FineUI控件)
IT之家
IT之家
博客园 - 【当耐特】
L
LangChain Blog
A
About on SuperTechFans
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
N
Netflix TechBlog - Medium
博客园_首页
WordPress大学
WordPress大学
博客园 - Franky
Engineering at Meta
Engineering at Meta
C
Check Point Blog
aimingoo的专栏
aimingoo的专栏
M
MIT News - Artificial intelligence

DEV Community

Authentication Security Deep Dive: From Brute Force to Salted Hashing (With Java Examples) Why AI Systems Don’t Fail — They Drift Spilling beans for how i learn for exam😁"Reinforcement Learning Cheat Sheet" I Replaced Chrome with Safari for AI Browser Automation. Here's What Broke (and What Finally Worked) How Python Borrows Other People's Work The $40 Architecture: Processing 1 Billion API Requests with 99.99% Uptime Vibe Coding: A Workflow Guide (From Zero to SaaS) Most webhook security guides protect the wrong side. The scary part is delivery. Headless CMS for TanStack Start: Build a Blog with Cosmic EU Age Verification App "Hacked in 2 Minutes" — What Actually Happened Comfy Cloud’s delete function does not actually remove files Running AI Models on GPU Cloud Servers: A Beginner Guide Event-driven media intelligence with AWS Step Functions and Bedrock I scored 500 AI prompts across 8 quality dimensions — here's what broke How to Call Google Gemini API from Next.js (Free Tier, No Backend Needed) The Portal Protocol: Reclaiming Human Connection in the Age of AI How to Fix Your Team's Scattered Knowledge Problem With a Self-Hosted Forum Intro to tc Cloud Functors: A Graph-First Mental Model for the Modern Cloud Designing Multi-Tenant Backends With Both Ownership and Team Access I Built a Neumorphic CSS Library with 77+ Components — Here's What I Learned PostgreSQL Performance Optimization: Why Connection Pooling Is Critical at Scale Cómo construí un SaaS multi-rubro para gestionar expensas en Argentina con FastAPI + Vue 3 🚀 I Built an Ethical Hacking Scanner Tool – Open Source Project I Replaced /usage and /context in Claude Code With a Single Statusline A Pythonic Way to Handle Emails (IMAP/SMTP) with Auto-Discovery and AI-Ready Design I Collected 8.9 Million Polymarket Price Points — Here's What I Found About How Markets Really Move EcoTrack AI — Carbon Footprint Tracker & Dashboard Everyone's Using AI. No One Agrees How. 5 self-hosted ebook managers worth trying in 2026 Building Your First AI Agent with LangChain: From Chatbot to Autonomous Assistant
Why Pure RNG is Broken- Building a "Card Deck" Lottery in...
Сhekers · 2026-05-06 · via DEV Community

"Pure RNG promises nothing. A shuffled deck promises everything - eventually."

When designing the reward system for active users at SolChekers, we hit a classic Web3 wall.

Usually, projects just roll a digital dice. You get a 1% chance to hit a jackpot on every action. Mathematically, it’s completely fair. Psychologically, it’s a disaster.

With pure independent probabilities, a dedicated user could perform 500 actions and win absolutely nothing, simply because they hit the bad end of the variance curve. That means frustration, churn, and a flooded support inbox.

We needed a system that offered guarantees. So, we killed the dice and brought in the Card Deck.

The Concept: Decks over Dice

Instead of generating a random number on the fly, we assign each user a personalized virtual "deck" of cards. The deck's composition is based on their activity tier.

If there is one Flush (Jackpot) card in a 10-card deck, pure RNG cannot guarantee you'll roll it in 10 tries. A deck does. You are guaranteed to hit it; the only mystery is when.

Here is how we built this pattern in Rust.

1. The Deck State

Every deck tracks its remaining cards, the user's current session strength (Tier), and a soft-pity counter (bad_streak).

use rand::{Rng, rngs::StdRng, SeedableRng};
use sqlx::Row;

/// A user's personal deck. Each card represents one future outcome.
/// When empty, the deck is reshuffled — guaranteeing the user *will* win,
/// just not when. Pure RNG can't promise that.
#[derive(Debug, Clone)]
struct Deck {
    cards: Vec<Card>,    // remaining cards, FIFO
    cursor: u16,         // position for tamper-proof commit
    tier: Tier,          // current "session strength"
    bad_streak: u8,      // soft-pity counter
}

#[derive(Debug, Clone, Copy, PartialEq, Eq)]
enum Card { Crumbs, Small, Medium, Good, Flush, Reserve, Buffer }

#[derive(Debug, Clone, Copy)]
enum Tier { Tiny, Small, Medium, Big, Whale }

Enter fullscreen mode Exit fullscreen mode

2. Rebuilding and Drawing

When a deck runs out, we build a new one. If a user has a long bad_streak (too many empty draws), we bump up their Tier to inject better cards into their next shuffle.

impl Deck {
    /// Build a fresh deck with composition shaped by tier and pity.
    /// Higher tier → more "Good"/"Flush" cards. Long bad streak → upgrade tier.
    fn rebuild(tier: Tier, bad_streak: u8, rng: &mut impl Rng) -> Self {
        // The exact mix is the secret sauce — left abstract on purpose.
        let mut cards = compose_deck(tier, bad_streak);
        shuffle(&mut cards, rng);
        Self { cards, cursor: 0, tier, bad_streak: 0 }
    }

    /// Draw the next card. The deck *commits* to its remaining future
    /// the moment it's shuffled — players can't reroll, can't skip.
    fn draw(&mut self) -> Option<Card> {
        let c = self.cards.pop()?;
        self.cursor += 1;
        Some(c)
    }
}

Enter fullscreen mode Exit fullscreen mode

3. The UI Twist: Showing the Future

Because the deck is finite and already shuffled, the system actually "knows" the user's future. This unlocks a killer UI feature: *Expected Value (EV) Remaining.
*

Instead of just showing users what they’ve already won, we can show them the mathematical value currently trapped inside their remaining deck. It’s an incredibly powerful retention hook.

impl Deck {
    /// Expected value of *what's left*. A deck knows its own future.
    fn ev_remaining(&self, pool: u64) -> u64 {
        self.cards.iter().map(|c| card_value(*c, pool)).sum::<u64>()
            / self.cards.len().max(1) as u64
    }
}

Enter fullscreen mode Exit fullscreen mode

  1. Atomic Execution (The Ledger) In Web3, distribution logic has to be bulletproof. The prize pool, the deck state, and the ledger must move together atomically. We use sqlx to lock the rows and ensure idempotency. No race conditions, no double spends.
/// One lottery event — atomic and idempotent.
/// The pool, the deck, the ledger: all move together or not at all.
async fn deal_card(
    db: &sqlx::PgPool,
    user_id: i32,
    activity: u64,
    source_id: &str,
) -> anyhow::Result<Outcome> {
    let mut tx = db.begin().await?;

    // Lock the row to prevent concurrent draws
    let row = sqlx::query(
        "SELECT deck, cursor, tier, bad_streak, pool_balance \
         FROM lottery_state WHERE user_id = $1 FOR UPDATE"
    )
    .bind(user_id)
    .fetch_one(&mut tx)
    .await?;

    let mut deck = decode_deck(&row);
    let pool: u64 = row.get::<i64, _>("pool_balance") as u64;

    // Empty deck = a fresh promise. Tier may shift based on activity.
    if deck.cards.is_empty() {
        let mut rng = StdRng::from_entropy();
        let tier = upgrade_tier(deck.tier, deck.bad_streak, activity);
        deck = Deck::rebuild(tier, deck.bad_streak, &mut rng);
    }

    let card = deck.draw().expect("just rebuilt");
    let prize = card_value(card, pool);

    // Pity accumulates on weak draws — feeds back into tier upgrades.
    deck.bad_streak = if prize == 0 { deck.bad_streak + 1 } else { 0 };

    sqlx::query(
        "UPDATE lottery_state SET deck = $1, cursor = $2, tier = $3, \
         bad_streak = $4, pool_balance = pool_balance - $5 \
         WHERE user_id = $6"
    )
    .bind(encode_deck(&deck))
    .bind(deck.cursor as i32)
    .bind(deck.tier as i32)
    .bind(deck.bad_streak as i32)
    .bind(prize as i64)
    .bind(user_id)
    .execute(&mut tx)
    .await?;

    // Replay-safe ledger: same source_id = same outcome, always.
    sqlx::query(
        "INSERT INTO ledger (user_id, card, amount, source_id) \
         VALUES ($1, $2, $3, $4) ON CONFLICT (source_id) DO NOTHING"
    )
    .bind(user_id)
    .bind(format!("{:?}", card))
    .bind(prize as i64)
    .bind(source_id)
    .execute(&mut tx)
    .await?;

    tx.commit().await?;

    Ok(Outcome { 
        card, 
        prize, 
        ev_remaining: deck.ev_remaining(pool) // Revealing the future to the UI
    })
}

struct Outcome {
    card: Card,
    prize: u64,
    ev_remaining: u64,
}

Enter fullscreen mode Exit fullscreen mode

The Takeaway

The crypto space can feel like a chaotic casino. But by applying strict, pedantic engineering principles-what I call the disciplined degen approach-you can build systems that are reliably fair.

The Card Deck pattern completely eliminates the "infinite loss" problem. Users are no longer fighting variance; they are actively playing out a guaranteed set of rewards, earning better decks through their engagement.

How are you handling fair RNG and user retention in your Web3 stacks? Drop a comment below, or let's argue about the Rust borrow checker.