Skip to content
Rex St. John
demoin development

Verafy Harness

An AI validator anyone can run. One model in a harness judges contracts written in words for Verafy Chain, a concept chain with no token, and the harness holds its own keys and pays for its own inference in whatever token it is paid in.

DeepSeek Harness / Node.js / OpenRouter / vLLM / Ed25519

Problem

A smart contract can only enforce what someone can write as code. Most of what people want enforced is a policy, a claim or a condition about the world, and today those decisions leave the chain and come back as someone's word.

Solution

Two changes. Contracts are written in words: context, a question, a payment and a short list of exits. And a validator is an AI model wrapped in a harness that takes requests in, checks every pinned source, deliberates, commits and reveals a signed vote, and runs the contract's exit. A jury of harnesses from different labs rules, and a ruling only counts when their agreement clears the contract's bar.

Each harness also carries a routing agent: a keyblock that keeps API and wallet keys encrypted and hands out scoped keys, a banker that accepts any token and swaps between them, an API router that plugs into and pays AI APIs and cloud hosts, and a payment wallet. It is built on DeepSeek Harness, with juror mode as a plugin.

Analysis

There is no token, on purpose. Escrow stays on the chain where the requester paid, in their asset, and harnesses are paid in the same asset. That removes the usual reason to build a network around a coin, and it leaves two problems open: how to weight nodes without stake, and how to compare bonds posted in different assets.

Security is economic, not mathematical. Commit and reveal stops copying and lab diversity stops one lab's blind spot deciding, but forged evidence fooled every model in testing, and a hosted model can't prove which model served a vote. Proofs of inference would close that gap; today they exist for one open model and run to about 18.78 MB each.

Result

A working prototype, not a network. Five contracts ruled live on five labs' models through OpenRouter, 5.9 to 30.1 seconds each and $0.0163 in total (measured Nov 6). Five DeepSeek Harness processes on five labs' models sealed a block from their reveals, with every other tool locked. The live forecast fell below its bar, which is the escalation path working as designed. Built without venture capital and MIT licensed.

It ships three ways as of v0.0.2-alpha (Nov 6): an MCP server on npm, @verafy/mcp, with plugins for seven agents including Claude Code, Codex, Cursor and Gemini CLI; single-file binaries for Linux, macOS and Windows; and a Docker image. The agent is a client of the harness, never a juror, and live calls stay off until a spend cap is set.

Screens

  • The verafyHarness logo, four corner brackets holding a blue core, beside the words Harnessed AI validators for Actually Smart Contracts. No token.
  • Block diagram of a harness. Requests, pinned context and live sources flow through intake, a context loader and a tools sandbox to the AI model, then a signer, contract runtime and outbox. A routing agent row holds a keyblock, banker, API router and payment wallet, paying AI APIs, provers and cloud hosts.
    The model judges. The harness does everything else a validator does, including holding the keys and paying the bills.
  • Terminal output of one ruling, with propose, commit, reveal, rule, pay and seal stages, five harnesses voting NO and a block sealed
    One ruling on the command line, from a funded contract to a sealed block.
  • Anatomy of an Actually Smart Contract, with context, question, payment and exits, ruled NO by five harnesses at 94 percent against an 80 percent bar