rng-crypto-specialist

Design and audit provably fair RNG systems with SHA-256 and HMAC-SHA256.

39|12|Updated Feb 8, 2026
One-click install
npx skills add https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine --skill rng-crypto-specialist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rng-crypto-specialist
Source: https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine/tree/main/rng-crypto-specialist
Command: npx skills add https://github.com/egorfedorov/Slot-Casino-Game-Developer-Skills-for-Stake-Engine --skill rng-crypto-specialist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Provably fair RNG systems are critical for casino games to ensure reproducible, tamper-evident outcomes that players and auditors can verify.

Core Features & Use Cases

  • Commit-reveal design governance for server seed and client seed lifecycles.
  • Deterministic outcome derivation using HMAC-SHA256 with rejection sampling to prevent modulo bias.
  • Transcript verification tooling and compliant sign-off documentation for audits.
  • Security best practices to prevent seed leakage, nonce reuse, and replay attacks.

Quick Start

Provide serverSeed, clientSeed, and nonce, then run the verification workflow to derive and validate the outcome.

Frequently Asked Questions about rng-crypto-specialist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a provably fair RNG system for casino games?

A provably fair RNG system uses a commit-reveal flow for server and client seed lifecycles, deriving deterministic outcomes via HMAC-SHA256 with rejection sampling to prevent modulo bias and ensure tamper-evident verification.

What is rejection sampling in provably fair RNG and why is it needed?

Rejection sampling in provably fair RNG is a bias-free mapping technique that discards out-of-range values during outcome derivation, preventing modulo bias and ensuring uniformly distributed results across game boundaries.

How do I verify a provably fair game outcome using server seed and nonce?

You verify a provably fair outcome by providing the serverSeed, clientSeed, and nonce to a verification workflow, which derives and validates the result against the committed hash using SHA-256 and HMAC-SHA256.

How does a commit-reveal scheme prevent seed leakage in casino games?

A commit-reveal scheme prevents seed leakage by hashing and committing the server seed before gameplay, revealing it only after the session ends, which blocks replay attacks and nonce reuse while maintaining outcome transparency.

Can I use this provably fair verification tooling for third-party audits?

Yes, you can use this verification tooling for third-party audits because it generates transcript verification outputs and compliant sign-off documentation tailored for reproducible, tamper-evident auditing.

What are the limitations of HMAC-SHA256 for nonce progression across server boundaries?

HMAC-SHA256 requires strict nonce progression management across server and client boundaries to prevent reuse; if nonces repeat or seeds leak, the deterministic chain breaks and replay attacks become possible.