KernelCode Request Access
<p>04</p>Kernel Prove

Proofs, withtheir fine print.

Formal verification with Aristotle for supported code and properties. Every result identifies the actual proof scope, assumptions and verification outcome.

prove_property referenceRequest Access
<p>01</p> Supported today

Honest about what can be proved.

Kernel Prove uses Aristotle’s official SDK. Aristotle’s documentation currently lists C and SystemVerilog verification, so that’s what Kernel Prove supports at launch. Solidity contracts are covered by Kernel Scan or a specialized verification backend — not presented as proved.

Engine
Aristotle, via its official SDK
Languages
C and SystemVerilog (per Aristotle’s documentation)
Solidity
Kernel Scan or a specialized verification backend
Pricing
Quoted per job, approved before it runs
<p>02</p> Every result

Scope. Assumptions. Outcome.

A proof is only as good as what it covers. Each result says exactly that.

<p>01</p>

Proof scope

Exactly which property, which functions and which files were verified.

<p>02</p>

Assumptions

Every assumption the proof depends on, stated explicitly — nothing implied.

<p>03</p>

Outcome

The machine-checked verification outcome, recorded alongside the commit hash.

<p>03</p> Job lifecycle

Runs take minutes to days.

Formal verification is asynchronous and can be expensive, so every job is quoted and explicitly approved before compute is spent.

  1. <p>01</p>Submit

    Send code and the property to prove with prove_property.

  2. <p>02</p>Quote

    Kernel estimates the job and returns a quote.

  3. <p>03</p>Approve

    You — or your agent, within its limits — explicitly approve the spend.

  4. <p>04</p>Run

    The job runs on an asynchronous queue. Poll get_verification for free.

  5. <p>05</p>Result

    Scope, assumptions and outcome — ready to attest onchain.