KernelCode Request Access
<p>09</p>Roadmap

Shippingin this order.

Four priorities, built in sequence: a verification engine first, then distribution to agents, then formal proofs, then onchain evidence.

Request AccessExplore the Platform
<p>01</p> MVP priorities

Four phases.

01

Verification engine

  • GitHub URL scanning
  • Contract scanning
  • JSON findings
  • Report pages
02

Agent distribution

  • MCP server
  • x402 payments
  • Asynchronous verification jobs
03

Formal verification

  • Aristotle integration
  • Property tracking
  • Machine-checked results
04

Onchain evidence

  • Robinhood Chain attestation contract
  • Immutable report hashes
  • Public registry
<p>02</p> Principles

Rules that don’t change between phases.

<p>01</p>

A scan is not a proof

Static analysis finds known classes of problems. A clean scan is reported as a clean scan — never as a mathematical guarantee.

<p>02</p>

Every proof states its scope

Formal results list exactly which property was proved, under which assumptions, and what was left out of scope.

<p>03</p>

Attestations record, not endorse

An onchain attestation proves a report existed and hasn’t been altered. It is not a safety rating.