Renaiss Fair
Renaiss inventoryreal graded slabs, and the pool every pack is built from
Pandora 248 — the line machinePandora 248 · the line machine
BLUEPRINT · PANDORA 248

How a pack is formed

  • 01Candidate poolRenaiss inventory
  • 02Target EVwithin ±7% of the pool mean
  • 03Top-tier cardredrawn fresh as the starting point for every attempt, then the rest fills in around it
  • 04Commitmentthe accepted lineup is sealed into a Merkle root
Merkle root · pending

Fairness should not
be believed.It should be
verified

Structural guarantees. Probability transparency. VRF-verifiable fairness. Every draw can be independently certified. The result can't be manipulated. Not Renaiss's call. Not even Renaiss knows which card the drawer will get, the moment payment lands.

Begin with ascroll or thearrow keys
PILLAR I · CONSTRUCTION

How a pack gets built

The algorithm tries, and tries again, under rules published in advance. Fall short on any condition, and the whole attempt is discarded — until every condition holds.

View source
AttemptEV $359.55
$237$273
≠above the target rangeTarget EV$237 – $273Every retry redraws the top-tier card itself, too — it's not one fixed card with everything else reshuffled around it.
Pandora 248 — the line machine
Pandora 248Target EV$255
Merkle root · pending
Legendary
Epic
Rare
Uncommon
Common
PILLAR II · SEAL

The moment it's sealed, no one can touch it

The sealed lineup is hashed into a Merkle root and recorded on-chain the moment it's accepted. Add a card, remove one, or swap one afterward — the root no longer matches.

Pandora 248 — the line machine
Pandora 248✓Target EV$255
Merkle root · pending✓root 0x········
Verified by Renaiss Fair · On-chain✓root 0x········
PILLAR III · DRAW

Not all randomness is real

True randomness means even the platform can't predict it, can't control it, and has nothing to reference. This true random number can be verified, and replayed, by anyone.

α = keccak256( tag ‖ blockHash ‖ packId ‖ checkoutId )→index = keccak256(β) mod remaining cards
RenaissWITH RENAISS FAIR

The seed comes from on-chain data that doesn't exist until after the drawer pays. Not even Renaiss can compute the result before then — the drawer can recompute it and check nothing was touched.

Pandora 248 — the line machine
OTHER PLATFORMUNVERIFIABLE

The result comes from a private database — possibly referencing data only the platform knows. The drawer can only take its word for it, with nothing to check.

An opaque claw machine — no way to see inside
Private database

Fairness, compared

The Renaiss Fair draw beside the ways packs are usually ripped.

Renaiss Fair Gacha
Physical card shop
Web2 Platform
Other Web3 Platform
Pillar I · ConstructionHow packs are formed
Published algorithm.

Every pack's target EV must stay within a fixed tolerance of the pool average, and that tolerance configuration is open to public. Any pack that misses on a condition is discarded.

Curated by hand.

Packs can be weighed, mapped, or hand-picked before they ever reach the shelf.

Private backend.

A polished storefront in front — pack composition happens in a system only the platform can see.

Web3 in name only.

The token lives on-chain; the assembly logic almost never does. Publishing the construction rules is the rare exception, not the norm.

Pillar II · SealSealed & tamper-proof
Merkle root, committed on-chain.

Add, remove, or swap one card and the root no longer matches — tampering exposes itself.

Nothing is sealed.

The shelf can change at any moment, and no record survives.

Editable records.

A private database can be revised silently, with nothing left behind to detect it.

Rarely committed.

Most lineups are never locked on-chain before sale — and a pool that was never sealed is free to drift.

Pillar III · DrawVerifiable randomness
VRF with public verifiable proof

The seed is born from a block hash after payment — even Renaiss can't precompute it, and anyone can replay it.

Decided in advance.

The order of the packs is fixed before you walk in.

Server-side RNG.

The result comes from code no outsider can audit.

A VRF is the exception, not the rule.

The typical draw still runs on server RNG or a platform-supplied seed — “on-chain” describes the asset, not the randomness.

Proof resolutionTier-level vs card-level
Down to the exact card.

The VRF index maps to one position in the lineup, which is committed under the Merkle root and ordered by unique token ID. The proof names your card, not just its rarity.

No proof at any level.

Neither tier nor card can be demonstrated after the rip.

No proof at any level.

Tier and card alike rest on the platform's word.

Nothing, for most; tier-level, for the few.

The majority publish no proof at all. The minority with a VRF can prove which rarity you hit — the exact card is still assigned off-chain, with nothing to check.

Verdict

Fair, and verifiable

The shelf can be curated

The database has the last word

Web3 branding, Web2 machinery