Visual mutations
Let the bits change how your coin looks.
THE IDEA IS SIMPLE.
A coin. A stream. A possibility.
Randomness becomes useful when everyone can see the rules and follow the result.
01
Measurement
An authenticated provider produces a batch of measurement bits.
02
Commitment
The output digest, provider receipt, and batch identity are published.
03
Q-Stream
The coin’s ledger records the batch and its assigned consumer.
04
Event
A deterministic mapping turns the assigned bits into an outcome.
MEASUREMENT SERVICE NOT CONNECTED
This is the protocol’s required data path. Quantum origin requires an authenticated provider receipt; it cannot be inferred from a hash.
BITS ARE JUST THE BEGINNING.
Five ways to move the story.
Rare events
Unexpected moments. Published odds.
Community picks
One selection. A result everyone can check.
Cosmetic unlocks
Select non-transferable cosmetic traits.
Lore generation
Every batch can open a new chapter.
PUBLIC RULES
No rerolls.
No moving the goalposts.
A production stream must commit its rules before the bits arrive. Each batch is assigned once. Its inputs and mapping reproduce the same result.
That guarantee belongs in the consumer program and public ledger. A local browser alone cannot enforce it.
Recompute a resultACTIVE EVENT TABLE v1
OUTCOMEPROBABILITY
No special event
96.00%
Color mutation
3.00%
Rare event
0.80%
Epic event
0.18%
Mythic event
0.02%
Mapping: active-v1 · 10,000 possible values
A receipt, not a promise.
Every production batch needs a provider, job ID, generation timestamp, measurement description, raw-result digest, output digest, coin ID, and immutable consumption record.
Creator-fee funding requires explicit on-chain routing. Connecting a wallet does not activate fee collection or purchase measurements.