← SYLIRIResultBond

More products and projects are on the SYLIRI home page.

All products and projects

Early access

ResultBond

Pay for fixes that really work.

Turn the pages: arrows, click or swipe

01 / 04

The problem

An AI agent says “fixed” — and that is only its word

An agent's report that the code works is self-assessment. A code review is an opinion, not a record of a specific check. Payment often comes before any independent check.

ResultBond issues a signed proof receipt.PASS, FAIL or INCONCLUSIVE — with reasons. Payment is tied to a fix that actually passed the tests.
Signed proof receipts for code
02 / 04

How it works

Job → freeze → check → receipt

The parties agree on the code, acceptance rules and hidden tests. The patch is frozen by its digest. The check runs in an isolated sandbox, the evidence is recorded and the receipt is signed.

  • Hidden acceptance tests
  • Isolated sandbox
  • GitHub extension
Four steps from a patch to a receipt
03 / 04

Know-how

A receipt cannot be forged and can be checked in a browser

Each receipt is bound to one immutable version of the code. Hidden tests are first qualified on known-good fixes. Evidence is sealed with SHA-256 and signed with Ed25519. An unclear case is honestly marked INCONCLUSIVE.

  • 570 runs: 560 correct verdicts
  • 0 good fixes marked FAIL
  • 10 misses published
Every check leaves a trace
04 / 04

What it can do

The pilot is open

Python only for now. On-chain settlement is shown on a testnet with test tokens.

  • Signed receipts
  • Audit of the work and tests
  • In-browser signature check
  • Receipts in GitHub pull requests
  • Published limitations

Thank you for looking through.