World’s Fair 2026 · Judge guide

START WITH
THE EVIDENCE.

Run the same bytes through three real Solana libraries. See the difference, inspect its scope, and take the report with you.

01 / Two minutes · nothing to install

Compare real Kit versions.

  1. Open the comparison and select the synthetic version-3 example.
  2. Run it against the pinned, published @solana/kit 3.0.3, 4.0.0 and 8.3.0 libraries.
  3. Inspect the results: the expected outcome is ACCEPT for 3.0.3 and REJECT for 4.0.0 and 8.3.0. The page executes the libraries to produce fresh results.
  4. Run a canonical legacy or v0 control, then download the JSON report with the input bytes, hash and results.
Run the real-library comparison ↗

Two decoder calls per version: transaction decoding followed by compiled-message decoding. The examples are synthetic, not fetched transactions. A difference is evidence to investigate—not a safety verdict or an established security bug. Impact is unassessed. Reports are unsigned. Use public, non-sensitive bytes; the comparison runs in your browser without a wallet or RPC.

02 / Separate demonstration harness

Inspect Conformance.

  1. Open Raven Conformance and select Solana transaction versions (Experimental), 30 vectors, corpus 1.4.
  2. Select SOL_BROKEN_SUBTLE, then Run Conformance (live). Expect 27 matching rows and differences at V03, V10 and V16.
  3. Select SOL_CONFORMANT_REFERENCE and run again. Expect 30 matching rows.
  4. Under Download & reproduce, choose Replay report. Expect Replay matched, bundle yes and semantics yes.
Open Conformance ↗

These are Raven-owned demonstration targets. V03 and V16 use the proposed, experimental v1 layout (SIMD-0385); V10 is a non-canonical length. The finite profile does not establish a defect in a customer’s decoder. MATCH means a retained expectation reproduced, not that a transaction is safe.

03 / Offline reproduction

Verify Agent Trust.

Use Node 22.18.0. Clone recursively into a new folder and run from the repository root. This setup requires GitHub access; the guide and browser comparison above are hosted on Raven.

git clone --recurse-submodules https://github.com/billybotticelli4u-collab/raven-worldsfair-2026.git
cd raven-worldsfair-2026
npm run demo

Expected output:

Valid receipt: PROCEED
One-field tamper: REFUSE

No npm install is needed for this command. It runs the pinned verifier on deterministic offline fixtures, not live-chain data. PROCEED is the fixture’s policy outcome, not permission to transact. This command prints the two Agent Trust lines; the Conformance results come from the separate run above.

Source & deeper reproduction.

This on-site quick guide leads with Raven’s browser comparison. A retained copy of the repository guide provides the longer setup instructions, source pins and limitations.

Reviews are internal and bounded, not external audits. A signed receipt, key trust, freshness and permission to act are separate questions.