01

The DICE Network

D

Decentralized

I

Incentivized

C

Cryptographic

E

Entropy

Mine VRF.
While you sleep.
on Solana.

A real box on your shelf mining verifiable randomness for Solana. No fans. No diminishing returns. No electricity tax.

  • 01Real hardware on your shelf — an ESP32 device drawing true entropy from physical noise, not a software seed.
  • 02Your node earns from every randomness request it helps fulfill — paid out on-chain to a wallet you control.
  • 03Plug in once. No staking, no token gates, no firmware tinkering. Earn until the device dies.
[ entropy · mesh ]LIVE
N · 90°S · 90°180° E
sf · nyc · ldn · par · ber · tyo · sgp · hkg · syd · dxb · bom · sao · bue · delGLOBAL
02

protocol · trace

One request. Four seconds.

Commit-reveal runs across six hardware nodes in parallel. The coordinator bundles the result into a single Solana transaction. No stake, no relayer, no token.

FIG_002 · commit-reveal · single roundwall clock : 3.9 scommitrevealdAppt=001coord+80ms02mesh × 6+1.2s03coord+2.8s04chain+3.9s05each hop verified · no stake · no token0.002 SOL / request
03

entropy · node

One board. Six silicon primitives.

The DICE-S3 node is built from a single ESP32-S3 module with a hardware TRNG, WiFi radio, and secp256k1 signing — nothing more. Each unit is tamper-evident and field-provisioned.

FIG_003 · DICE-S3 · explodedScale 1:1 · dimetric 2:1ESP32-S301 · WiFi ANT2.4 GHz trace02 · ESP32-S3TRNG · secp256k103 · USB-Cpower · flash04 · Status LEDspwr · net · ent · stat05 · XTAL26 MHz · PLL src06 · BOOT · RSTprovisioningREV_C · 2026[ scroll to separate ]
04

manifesto · three · pillars

Three things we won't trade.

Every design decision in DICE starts from these three constraints. If a feature violates one, it doesn't ship.

01 / 03

I

Hardware-true entropy

Every byte of randomness comes from a physical ESP32-S3 RNG. No software PRNG, no mock, no fallback. The silicon generates it, the silicon signs it.

02 / 03

II

No token, no gatekeeping

Consumers pay 0.002 SOL per request. Operators earn SOL directly. There is no DICE token. There is no allowlist. There is no governance trap.

03 / 03

III

Commit-reveal or nothing

No node can bias the output. Every node commits a hash, reveals a preimage, and the round is aggregated on-chain. Dishonesty is provable and slashable.

05

roadmap · trajectory

From devnet to permissionless.

Five milestones along a single curve. Shipped first, then the next one — no ten-year fog plan.

Q4 25Devnet launchSHIPPEDQ1 26Anchor 1.0 + SDK v1SHIPPEDQ2 26Mainnet betaQ3 26Operator rolloutQ4 26Permissionless

Q4 25

20-node mesh, commit-reveal, 4s rounds.

Q1 26

Stable program, TS SDK, hosted explorer.

Q2 26

Invite-only beta. Streaming VRF primitive.

Q3 26

Public pre-order. 100-node target, staking.

Q4 26

Open operator onboarding. DAO governance.

06

use · cases

What you can build.

A

01 / 03 · gaming

Provable game outcomes

Shuffle a deck, roll dice, pick a raid boss. The result is traceable to the hardware RNG that produced it.

B

02 / 03 · defi

Lottery + yield raffles

Weekly prize pool draws, airdrop lotteries, sweepstakes. One request, one winner, one on-chain signature.

C

03 / 03 · nft

Trait reveals + drops

Pick the mint order. Assign rarity. Randomize reveal metadata. Each step provably unbiased.

07

quickstart · dev

Drop in. Request entropy.

The SDK ships typed clients for Rust and TypeScript. One import, one method, one transaction.

$npm i @dicelabs/vrf
import { DiceClient } from "@dicelabs/vrf";

const client = new DiceClient({ cluster: "devnet" });

// Request one 32-byte random value for 0.002 SOL
const round = await client.requestRandomness({
  payer: wallet,
  callback: handleResult,
});

console.log(round.signature);

RETURN SHAPE

  • round_idu64
  • value[u8; 32]
  • nodesPubkey[6]
  • proofsecp256k1
  • latency~3.9 s

PRICING

0.002

SOL per request. No subscription. No token.

Read_SDK_docs
08

faq · beginner

Common questions.

Switchboard uses oracle VRF keys held by operators; Pyth uses a two-phase entropy scheme. DICE is different on the hardware layer — the random byte is generated by a physical ESP32 TRNG and signed in-chip, so there is no key custody question. The oracle cannot reveal what it doesn't hold.
DICE

Hardware-Backed Verifiable Randomness for Solana

from · dicelabs

Hardware-backed verifiable randomness for Solana. 20 physical nodes, commit-reveal protocol, 0.002 SOL per request.

tenzies · dice

Rolls

0

Best Time

Time

0s

roll dice · click to freeze · match all 10

// protocol

  • 20 physical ESP32 nodes
  • commit-reveal protocol
  • 0.002 SOL per request
  • solana mainnet
$echo "© 2026DICE Network"