ALIBI ALIBI

Bureau file · client-side only · no prompt stored

Prove it ran.
Reveal nothing.

A blockchain-style transaction receipt — but for AI. You get evidence of what ran, instead of taking the operator’s word for it. This page inspects that receipt in your browser. It never sees the private prompt.

Verify a receipt Ask ALIBI

The coin

$ALIBI

Venue
pump.fun
Role
backs the project

Desk

Ask ALIBI

Role
explain the project
Note
chat ≠ receipt

Ask like a trader. What it is, why it matters, what the coin is. This desk talks to xAI. Receipts you paste in the inspector stay in this tab.

Start here

Receipt inspector

Case file

File
ALB-2026-1011-04
Scope
local / browser

Paste an alibi/1 receipt. Nothing leaves this tab. A well-formed JSON object is not a verification. Only recomputed hashes and supported signatures can move the stamp.

Simulated exhibits

Trader terms

What’s the actual tech?

Forget “cryptography” for a second. A Solana tx gives you a signature and a slot. You don’t trust the bot — you check the explorer. ALIBI is that, for an AI run.

  1. 01 / Prompt gets locked

    You send a private request. It’s encrypted so the server guy can’t just read it. It only unlocks inside a sealed hardware box (an enclave).

  2. 02 / AI hands you a receipt

    A small file. Which model ran. A fingerprint of the request and the answer. Same idea as a tx hash — not the whole story, but proof something specific happened.

  3. 03 / You check the proof

    This site checks the signature and the evidence. Pass means it came from the expected protected box. It does not mean the AI’s call was smart.

Why it matters

What’s the use?

Picture an AI trading agent that can move your bag. That’s the whole point.

Without

The agent says it followed your strategy. You just have to trust it. Same as a closed bot with no tx history.

With this

The agent can hand you evidence: which approved software ran, and what it processed — if the provider actually issues receipts.

The benefit

Less blind trust when AI touches money, wallets, or private data. You verify. You don’t take the operator’s word.

Same story for agents managing wallets, shops handling confidential files, and people building autonomous AI that shouldn’t be a black box.

$ALIBI

What about the coin?

$ALIBI backs the project. The product is this desk: paste an AI execution receipt, see VALID / INVALID / UNVERIFIED. Like a block explorer, but for AI proofs. The coin is the bet that this gets built and used.

  • $ALIBI is the coin of the Alibi project — it stands behind the work.
  • This site is the explorer. Providers still have to issue real receipts for the stamp to matter in the wild.
  • In one sentence: ALIBI is trying to make AI execution checkable, so you don’t have to take the operator’s word for it.

Procedure

How it works

  1. 01 / Submit

    Paste the receipt JSON. The bytes stay in memory on this page.

  2. 02 / Inspect

    ALIBI reads model id, output hash, timestamp, signature, and attestation.

  3. 03 / Verify

    Web Crypto recomputes hashes and checks ECDSA P-256 when a public key is present. The stamp is VALID, INVALID, or UNVERIFIED.

Evidence

What the receipt proves

Hash

If the output is included, SHA-256 is recomputed here. A match means that exact output produced that hash. It does not mean the output is true.

Signature

A P-256 signature over the canonical fields binds those fields to a public key. You still have to decide whether you trust that key.

Attestation

A hardware quote, if present, is shown. ALIBI does not invent a TEE verifier. Simulated examples are labelled simulated.

Limits

Trust boundaries

  • ALIBI cannot prove an answer is correct, useful, or unbiased.
  • ALIBI cannot prove a prompt stayed private on someone else’s machine.
  • A hash in a JSON file is a claim until it is recomputed or signed.
  • You trust this page’s code, your browser’s Web Crypto, and any key you accept.
  • Optional hardware attestation requires a verifier ALIBI does not pretend to be.

Architecture

Where the work happens