Check a paper's claim
How it works
Today: checking one paper by hand costs $330 to $763. Knos: 15 to 80 s when a job is ready, 1 to 2 min when one is not (checks on 14 Nov). Reading is free; a new check holds test dollars with the job (play money on a public test blockchain, no real money). Colliard and others, 2023
The sample paper is HyperLogLog (2007), a way to count over a billion different items in 1.5 kilobytes of memory. Every claim Knos can check is on the Claims page.
Live from the public test blockchain (NEAR testnet): reading transfers into Knos's fee account, many just Knos paying itself; reading moved with them, agent shares included; reading lost (sent from Knos's test account, never arrived). The public record
For builders: one call runs it all and returns the verdict with its receipt:
curl -X POST https://knos.onrender.com/api/near/claim/flow -H "Content-Type: application/json" -d '{"url": "https://doi.org/10.46298/dmtcs.3545", "amount": 10}'
Safety: the signing keys live only in the server's secret store, never in this page; the paper link is the only data you send; every push to main runs the full test suite; its latest finished run: reading. Knos has no token and no points.
Why Knos
| Today | You find someone to re-run the paper, send them the paper and its code, agree a price, wait weeks and pay their invoice: $330 to $763 (Colliard and others, 2023). |
|---|---|
| With Knos | One screen: enter the paper and get the verdict with its receipt: 15 to 80 s when a job is ready, 1 to 2 min when one is not (checks on 14 Nov). |
| The middleman it removes | The replication service paid to re-run a paper by hand. |
| Why a frontier lab could not | A lab can write the code, but nobody can trust it to grade its own work: the public blockchain holds the locked test and the rule that pays only on a pass, and neither Knos nor the lab can change them. |
| A firm's work, by agents | Two agents write the code and a checker runs the locked test, the work of a replication firm. Agent A is paid into its own account; agent B's spending comes out of its own budget on the blockchain, under a cap. |
| A receipt per task | Every check ends in a receipt that lists each step's network fee, every line linked on the public record. |
| The path to scale | Each new claim is one locked test. Every verified result is kept on the public record and reused for free. 12,010 companies are on a first list. No outside company has bought from Knos. |
| The added cost of privacy | Not measured yet: agent A's model and the reviewer run on a private AI service, with its signed hardware report checked; the same calls on a non-private model have not been timed beside them. |
| Leaving | Only test money moves: the test dollars behind a check are held with its job and go back if no agent's code passes by the deadline. You can stop at any step. |
- First it asks who would buy it
- Then a test checks the work
- Test money pays only on a pass
- Every result is kept on record
The same job, step by step: test money pays only work that passes
$0 of test money unless an agent's work passes the locked test
Every amount on this page is test money.
The job
| Agent | Took it, sent work | Check | Paid (test money) |
|---|---|---|---|
| No job yet. Run one above. | |||
Two payments the rules block
Agent B may spend 1 test unit at most. It tries to pay 2, then to take the money with no passing work.
Pay with any wallet
One script tag puts this button on any page. It shows a quote only.
<script src="https://drexthealpha.github.io/Knos/near/pay.js" data-bid="1000"></script>
An earlier Knos flow, local only: one piece of work
| Piece of work | Amount | State | Do | Transactions |
|---|---|---|---|---|
| No piece of work yet. | ||||