Proof — PLINTH

Sample data — this build serves fixtures. Nothing on this page has been read from the chain yet.

Proof01

Nothing here asks you to trust us.

A card game that hands out rarity has one hard problem: the house rolls the dice. We do not roll them. The chain does, in public, after you have committed.

Packs are settled by a block

Your receipt records the block height at request time and the height we will settle on: a hundred blocks later. The first block at or past that height picks the beast with its hash, modulo the pool size. Both blocks and both hashes are on the receipt.

Rarity is a published formula

At print time the twelve are ranked by real on-chain supply and cut into five bands. The thresholds are printed below. The seal is then frozen for the whole edition.

The cards are not NFTs

They are rows in our database bound to your address by a signature. We say so here, in plain words, because calling them NFTs without a contract would be a claimed feature that does not exist.

Why a hundred blocks and not one02

Why one hundred blocks and not one.This chain mines every ninety milliseconds, so the next block already exists by the time a receipt is written — settling on it would let whoever writes the receipt see the answer first. One hundred blocks puts the outcome about ten seconds beyond anyone's knowledge, ours included, and the wait is exactly as long as the pack takes to open.

The commit height is read by our server at the moment of the request, never sent by your browser. If the height came from the client, anyone could submit an old one whose settling block already exists, read the answer, and retry until they liked it. The settling block is read the same way, on the server.

settle target committed + 100
settle block first block with height ≥ target — not exactly the target, so the rule survives a slow chain
timeout 60 seconds — then the pack is void, and says so

If the settle block is not readable within 60 seconds the pack is voided and shown as voided. We do not settle it with a number of our own. Your free pack for that day comes back — a failure on our side does not spend it.

Worked example03

request at block 23,958,679
commit hash 0x01efd106…459b
settle target 23,958,679 + 100 = 23,958,779
settle block 23,958,779
settle hash 0x951a6e59…b2cb
last 4 hex → b2cb = 45,771 · 45,771 mod 12 = 3
index 3 of the pool → SPCX · The Iron Dragonfly

Open settle block Open commit block

These are two real blocks on this chain, read on 30 July 2026. Open them, take the last four characters of the settle hash, and redo it with a calculator. If our answer and yours differ, we are wrong and you should say so loudly.

Rarity bands04

Band	Supply percentile at print	Count in edition I
COMMON	0–20th	1
BROAD	20–45th	3
NOTABLE	45–70th	3
RARE	70–90th	3
LEGENDARY	90–100th	2

Six measures, six sources05

Measure	What it is	Field	Read
Supply	How much of the stock exists on this chain.	blockscout · tokens/{ca} · total_supply	NIGHTLY
Holders	Addresses holding the token. We read token_holders_count and label it, so you know which of the explorer's two counts this is.	blockscout · tokens/{ca}/counters	NIGHTLY
Transfers	On-chain movements in the last 24 hours.	blockscout · token transfers, 24h window	NIGHTLY
Range	Intraday travel of the quote, in dollars.	rhj/prices · dailyHigh − dailyLow	NIGHTLY
Forge	Dollars minted and redeemed over the trailing 24 hours. It falls as well as rises. No other chain publishes this.	rhj/prices · mintBurnUsdVolume	NIGHTLY
Yield	Dividend per unit from the last corporate action we recorded, with its date. Zero only if the token has never paid one.	rhj/corporate-actions · cashDividend.rate	NIGHTLY

How we know a number is still true06

On 29 July the quotes endpoint answered normally and served prices that were twenty-three days old. Nothing in the response said so; the timestamp was simply stale. The next day the same endpoint was live to the nanosecond. So the lesson is not which endpoint to use. It is that a source can be wrong about its own freshness, and a site that takes its word for it will publish old numbers as current without ever noticing.

Every read is therefore checked against the clock before it is stored. If the gap is more than fifteen minutes, the value is not written as current. It is kept with its real timestamp, and wherever it appears it carries its true age instead of pretending to be fresh.

The same rule covers failure. When a read does not come back, the row keeps its last valid value and states how old it is. Nothing is interpolated, nothing is carried forward silently, and no gap is filled with a plausible number.

Generated assets07

Twelve beasts, one hand

Every beast was drawn to a single fixed style block and a locked sixteen-colour palette. The seal plate and the card back were built from the same block so nothing on the page looks borrowed.