Six ways to pin a moment to the Earth

01 Earth-state beacon

Name a moment by the state of the planet instead of by a clock alone. The response carries the tick in UTC, unix_ns as a string, the held DVG to six decimals and in full, each domain, the latch, the beacon, and the previous beacon.

A signature over that beacon could not have been produced before the tick was published. That is the proof-after: the receipt sits after a measured Earth-state, and no later than the signing time.

Works today

• GET /v1/now returns the latest tick
• GET /v1/beacon/{tick or time} returns the tick at or just before that moment
• GET /v1/range returns a capped window
• Each beacon links to the history explorer for the same tick

curl "https://beacon.anomalyresearch.io/v1/beacon/2026-11-15T04:20:00.000Z"

02 Field-state receipts

Hash a file, a canonical snapshot of a variable, or a log line you want to be able to find again. Send only the SHA-256. The beacon signs the fingerprint together with the latest Earth-state. The file never leaves the browser or your machine.

Keep the receipt next to the file. Later, anyone can check the signature, the stored tick, and the file. A déjà vu log is the same call: hash the note, sign it, and you can show which beacon was current when you wrote the fingerprint down.

Works today

• POST /v1/sign signs a SHA-256 and appends the receipt to the log
• POST /v1/verify checks the signature, the beacon, and an optional file hash
• GET /v1/keys publishes the current Ed25519 public key
• The try-it signer hashes the file with Web Crypto and uploads the fingerprint only

HASH=$(shasum -a 256 notes.txt | cut -d' ' -f1)
curl -X POST https://beacon.anomalyresearch.io/v1/sign \
  -H 'content-type: application/json' \
  -d "{\"sha256\":\"$HASH\"}"

03 Verifiable draws

Announce a future tick, a population size n, and a count k. Until that tick exists, the service returns a commitment bound to the beacon that is current now. When the tick lands, the same request returns k distinct indexes derived from that tick's beacon.

The picker is SHA-256 counter mode with rejection sampling, documented on the docs page. There is no secret in the draw. Anyone can recompute the picks from the beacon.

Works today

• POST /v1/draw with a future seed_tick returns status: pending
• The same body, after the tick exists, returns status: drawn and the picks
• A seed tick that is already published is labeled as such

curl -X POST https://beacon.anomalyresearch.io/v1/draw \
  -H 'content-type: application/json' \
  -d '{"seed_tick":"2026-12-01T00:00:00.000Z","n":100,"k":3}'

04 Sigils, sound, and certificates

Every beacon has a generative seal. Five spokes follow the domain intensities. A rune in the middle is drawn from the beacon bytes. The same inputs always draw the same SVG. The permalink page adds a QR code and a short sine melody from the first eight beacon bytes.

Print the permalink on a certificate. A scan opens that moment: sigil, held value, domains, and a link into the history explorer.

Works today

• GET /v1/art/{beacon} returns the SVG
• /b/{beacon} is the permalink, with a QR code
• Play sigil runs in the browser from the beacon and the domain values

curl -o sigil.svg \
  "https://beacon.anomalyresearch.io/v1/art/BEACON?t=TICK_ID"

05 Condition triggers

A later version can call a URL when the held DVG or a domain crosses a line you choose. That notifier is not built. What exists today is a read: does the latest tick already satisfy the comparison?

Works today

• GET /v1/trigger is a description only. It registers nothing
• GET /v1/check?domain&op&value evaluates the latest tick and stores nothing

curl "https://beacon.anomalyresearch.io/v1/check?domain=held&op=gte&value=9"

06 A public research timeline

Latches and domain crossings are already in the publish row, and the beacon chain orders the ticks. Sign the fingerprint of a prediction while a beacon is current. The receipt names that beacon and the signing time. When a later tick is the outcome, anyone can see that the receipt's tick is earlier.

The service does not store the prediction text. It stores the fingerprint, the beacon, and the signature. The history explorer charts the same tick.

Works today

• Receipts carry tick_id, signed_at, and the beacon
• prev links each beacon to the prior tick
• Permalink pages link to history.anomalyresearch.io/?t=…

curl "https://beacon.anomalyresearch.io/v1/range?from=2026-11-14T00:00:00.000Z&to=2026-11-14T12:00:00.000Z"