Proof of Hunt
1 2 3 4 5 6 7 8 9 10 11
Studionet public beta Paper Trail

Twelve clues. No answer key is stored.

Each answer is a fact on the live web. Find it, and the next clue unlocks.

Enter the race Try a clue first
Controls
12
Winner
One
Attempts
6
Entry
Free

The course

Twelve sources on the live web: published standards, a CERN proposal from 1990, and SDK documentation. Find each answer in its source. The contract stores no answer key. Scroll the list and the map inks in behind you.

1 2 3 4 5 6 7 8 9 10 11
Course 01Start

    Try a clue

    An interactive illustration using a scripted answer and simulated validator messages. It makes no network calls or transactions and is not part of race 01. Use the play view for actual on-chain judging.

    In October 1969 the first message was sent between two ARPANET nodes. The operator typed LOGIN, and the system crashed partway through. Give the letters that arrived.

    Somebody wrote the answer down. Fifty years ago.
    Every clue points at a document that already exists

    Race rules

    Reveal within 24 hours of committing. Judging and retries close seven days after the commit. Both deadlines are capped by the race closing time, 30 days after it opens. An expired unrevealed commitment spends one attempt; an expired revealed commitment spends none. A source outage may prevent completion before the deadline. Anyone can expire overdue commitments or cancel an overdue unfinished race.

    One active commitment per runner. Six attempts per clue. No answer key is stored on chain; revealed player answers are public. The winner is determined by the earliest valid final-clue commitment, after earlier pending commitments are resolved or expired.

    Positions

    Live finalized positions from the public Studionet beta. No prizes or deposits; this demonstration course has publicly known answers.

    Loading live positions…

    The order shown is the order the race is decided in: furthest along first, and between runners on the same control, whoever committed earlier. Not whoever's verdict came back first.

    Validators read the live source. Then agree on a verdict.

    These clues have no stored answer key: being right depends on what a live document says. GenLayer validators read the source and agree on a verdict and source digest. The contract checks the agreed result before advancing a runner.