BLINDBENCH
connecting…
NEAR HACKATHONSealed evals · TEE scoring · onchain certificates

Private AI evals that pay their authors.

Public benchmarks leak into training data. On BlindBench, experts commit a secret test set to NEAR as a hash. Anyone pays to get a model scored. The questions run only inside NEAR AI Cloud enclaves, every answer is enclave-signed, and the score lands onchain as a certificate anyone can verify.

Private sets–committed as Merkle roots
Certificates–scores posted onchain
Signed answers–each one enclave-signed
Paid to authors–in NEAR, per run
Questions revealed–nobody sees the questions
LIVE
01 / Protocol

Four steps. Zero questions revealed.

Every step leaves something checkable: a root before the run, a signature on every answer, a certificate after.

01

Commit

An expert writes a secret test set. Only its Merkle root goes onchain, with a price per run.

commit_dataset(root)
02

Pay

Anyone pays to get a model scored, in NEAR from a wallet or from any chain through NEAR Intents. It sits in escrow.

request_run(set, model)
03

Score in a TEE

Questions go only to models in NEAR AI Cloud enclaves. The enclave signs every answer, then a TEE judge or hidden tests grade it.

attest · sign · grade
04

Certify

The score and an evidence hash land on NEAR as a certificate. Escrow pays the set's author.

fulfill_run(evidence)
02 / Private sets

Sealed sets. Public leaderboards.

Loading…

Reading the ledger…
03 / Proof

What a certificate proves

And, just as important, what it doesn't prove yet.

The questions were fixed first

The set's Merkle root was onchain before any run. Each certificate copies it, so a set can't be swapped after the fact.

The answers came from the named model

Every response is signed by a key bound to Intel TDX and NVIDIA hardware by NEAR AI's attestation. model enclave means the model's own enclave signed. gateway + TEE means NEAR AI's attested gateway signed after verifying a third-party enclave.

Nobody saw the questions

Only TEE models are scored. The evidence holds hashes and signatures, never questions or answers in the clear.

Still trusted today

The set's owner runs the grader, and checklist and rubric sets are graded by a TEE judge model named on the certificate. Next step: the grader in its own enclave.

04 / Use it

Three ways in. One command each.

Everything here runs against the live testnet contract. Reading and verifying need no account and no key.

Eval authors

Publish a private set

Write your questions as a JSONL file and commit it. Only the Merkle root, the item count, the grading mode and your price go onchain. You are paid each time someone has a model scored on it.

node blindbench.mjs commit myset.jsonl --price 0.5
Model builders and buyers

Get a model scored

Press Run a model on any set above and pay from a NEAR wallet, or pay from the command line. The payment waits in escrow until the certificate is posted. If none arrives within 24 hours, you can take it back.

node blindbench.mjs request 4 Qwen/Qwen3.8-27B --deposit 0.5
Anyone

Verify a certificate

Click any leaderboard row and press Fetch and verify the evidence, or recheck it yourself: every enclave signature, the Merkle root and the score, compared with what is onchain.

node blindbench.mjs verify --cert 10

Set up once. Clone the repo and point the CLI at the live contract. Committing and paying sign with your own NEAR testnet account (NEAR_ACCOUNT_ID, NEAR_PRIVATE_KEY). npm run demo runs the whole flow offline with no keys.

Read the docs
git clone https://github.com/yfarmxdev/blindbench && cd blindbench/cli && npm install && export BLINDBENCH_CONTRACT=blindbench-hnxot5.testnet