A new coin says "no premine" or "decentralized mining". This tool checks that claim against two public pages: the project's announcement and a block explorer page. GenLayer validators each read the pages on their own, extract a few facts, and must agree before a verdict is stored on chain.
A verdict describes what the two pages you supply show at the time of the check. It is not a proof about anything outside those pages.
Watch a check (50 seconds)
A real check on GenLayer Studio with the waiting time cut, using a fictional test coin. Captions are on screen. There is no sound. Also on YouTube.
Run a check
A temporary account is created in this browser tab only. It needs no wallet and holds nothing of value. It is enough to try the checker on Studio.
Transaction progress
Recorded checks
Loading…
How a verdict is decided
- Read. Each validator fetches both pages itself.
- Extract. Its language model fills in a short fixed form: does each page support or contradict the claim, the top miner's share of blocks, how many blocks that covers, and whether the earliest blocks show an extra allocation. The model never picks the verdict.
- Decide. A fixed rule table in plain code turns those facts into supported, contradicted or undetermined.
- Agree. Validators accept the result only if they reach the same verdict by the same rule, and their numbers match within the tolerance. If they do not agree, nothing is recorded.
Why these thresholds
- Above 50%. A miner with most of the hash power can out-build everyone else and rewrite recent blocks. No reading of "decentralized" survives that.
- At or below 33%. Above a third, withholding blocks pays for a miner however poorly connected it is (Eyal and Sirer, 2014). At or below a third the largest miner is under that bound.
- Between the two. The claim is neither clearly true nor clearly false, so the verdict is undetermined.
- At least 50 blocks. With fewer, a miner holding a third of the hash power is too likely to show a majority by luck. At 50 blocks that chance is under 1%.
The project's own page can never produce "supported" by itself. That always needs explorer evidence. The notes shown with each check are written by one validator and are not verified by the others.