GALABET

GALABET FAIR / RESULT VERIFIER

Check the result.
Follow the calculation.

Open a completed record or enter its revealed inputs. See what reproduces, what differs and which checks still need information.

Check a record ↓

No account. No seed upload. Calculated on your device.

Fox astronaut comparing a seed capsule with its revealed record at an inspection desk

THE INSPECTION DESK

Bring the record.

Use the original inputs and parameters. A different set of rules can produce a different result.

LOCAL CHECK

Checked in your browser. Your inputs are not uploaded to Galabet.

Fox investigator following two record strips to locate a differing symbol

READ THE REPORT

A difference has
a place to start.

Commitment mismatch
The revealed seed does not produce the supplied hash. Check that the commitment belongs to this seed session.
Outcome mismatch
The calculation produced another result. Compare the nonce, game parameters and revealed inputs with the original record.
Not provided
A required comparison value is missing. This is an unfinished check, not evidence of a bad result.

INSIDE THE RECORD

Every check needs
its own evidence.

The revealed input, the signing key and the flight receipt answer different questions. Here is how to read them.

REVEALED INPUTS

Open the capsule.
Keep the seal.

The commitment is the seal you saved before play. Once the seed is retired and revealed, hash it again and compare the two.

For Crash and Flight, the revealed input is a game hash, used with the recorded salt.

SEED INSPECTIONSHA-256
Revealed seedSaved commitment
SHA256(revealedSeed)compare withsavedCommitment

Keep both values. The hash alone cannot reproduce the round.

GALABET / RECORD CHECK
ATTACHED TO THE RECORDSignature
inspection
Record + signature↔Public key
Ed25519KEY CHECK
ILLUSTRATION / NOT A VERDICT
SIGNATURES

A matching key.
A separate identity.

A valid signature ties the record to the supplied public key. It does not tell you who owns that key.

Confirm the key’s owner separately. An unsigned record can still have its calculation checked.

FLIGHT RECEIPTS

The flight ends.
The record stays.

Reproduce the endpoint from the revealed game hash. Read the accepted cash-out as a separate event in the server’s record.

ILLUSTRATIVE FLIGHT PATH
Cash-out actionCrash endpoint
KEEP THE TWO SEPARATEEndpoint calculation

Reproduced from the revealed inputs.

Cash-out receipt

Requires the server’s accepted action and timing.

A pasted receipt alone cannot authenticate when cash-out arrived or prove that a payout was made.

FOR YOUR APPLICATION

Use the same
inspection code.

The browser and Galabet’s inspection API call the same library function. It validates the input before comparing values and returns a separate status for each check.

Calling the API sends your record to that server. The tool above runs locally and does not call it.

JavaScript / local inspection
import { inspectRecord } from '@galabet/fair';

const report = await inspectRecord(record);
console.log(report.status);
console.table(report.checks);

Bash / your local API server
curl -X POST http://localhost:3000/api/verify/inspect \
  -H 'Content-Type: application/json' \
  --data-binary @completed-record.json