Skip to content

Pay for tests you can rerun

Operators run your scenarios against a pinned snapshot of your hook. You pay only for results the verifier reproduces under rules you approved.

From objective to results

  1. 1

    Define a test objective

    You

    Name the hook, the callbacks, and the scenarios that worry you.

    You get

    A draft job with a pinned chain snapshot and a plain-English objective.

  2. 2

    Approve the scope

    You

    Confirm what is in and out of scope and what counts as a valid result.

    You get

    Acceptance rules the verifier applies to every submission, including whether coverage pays.

  3. 3

    Fund the job

    You

    Fund the budget and set the reward per accepted result.

    You get

    A job page that shows its funding status. Paid work opens only after funding.

  4. 4

    Receive results

    You

    Review accepted cases as they arrive.

    You get

    Reproducible tests you can replay in CI. Sensitive failures are delivered privately to your team.

Sensitive failures stay with your team

A failing case can be a working exploit. Its trace is encrypted to your team and the verifier. The public job record shows status and what was verified, not how the hook failed.

How private reports work
  • Encrypted delivery of failure tracesAt launch
  • Public job status without exploit detailsAt launch
  • Testing unreleased code in an attested environmentLater

Post a job

Sign in with a wallet, email or X, describe your hook, and submit. We reply with a draft scope and acceptance rules, and you can follow the status of your request in the app.

Post a job