Test hooks.Get paid for verified work.
PROBE runs reproducible tests for Uniswap v4 hooks. Teams fund the scenarios they care about. Operators earn when the verifier reproduces their result, paid from escrow on-chain.
- Verifier
- checking…
- Accepted results
- 0
- Paid out
- 0
See a run, start to finish
An operator runs probe work against a dynamic-fee hook. Three cases pass locally. The verifier reproduces each one, and accepts one.
Run it againprobe work demo-dynamic-fee-withdrawal
Demo- Load jobLoad
- Run casesRun
- VerifyVerify
- PayoutPayout
probe work demo-dynamic-fee-withdrawal
A scripted session against a fixed snapshot. The agent proposes cases, they run locally, and the verifier decides what counts.
Sample session, about 10 seconds
Passing locally is not enough.
Every case is replayed by a deterministic verifier on the job's exact snapshot. Each one gets a single verdict, and only one verdict pays.
Accepted
Reproduced on the snapshot and new on this job.
Reaches the payout step
Duplicate
Same execution path as a case already accepted.
No second reward
Failed verification
Did not reproduce, or broke a job rule.
No reward
How paid work happens
Every reward traces back to a funded job and a result someone else could reproduce. Nothing is paid for a claim the verifier cannot repeat.
Scroll to follow one job
A test that finds no bug can still pay.
Jobs that pay for coverage accept new, reproducible paths through the hook, even when nothing breaks. The job page says which kind of result it pays for before you start. See a coverage job
For hook teams: pay for the scenarios you worry about
You decide what gets tested and what counts as a valid result. You pay for accepted work, and the results stay reproducible after the job closes.
Plan a testing jobReproducible tests, not reports
Every accepted case re-runs on the job's chain snapshot. You can replay it in your own CI.
Your scope, your acceptance rules
You approve what is in scope and what earns a reward, including whether coverage pays.
Private delivery of sensitive failures
At launchA failure trace that shows a vulnerability is encrypted to your team and the verifier. The public record shows the job status, not the exploit.
Testing unreleased code in an attested environment
LaterRun jobs against code you have not deployed, inside an environment that proves what it ran.
Token and rewards
The token makes you eligible. Accepted work is what earns. Every reward is paid from a budget a job sponsor funded before the work opened.
- What do I hold it for?
- Eligibility for funded work, subject to the rules each job publishes.
- What do I do?
- Run the CLI, complete a job, and submit your result.
- When do I earn?
- After your result is accepted under that job's rules. Duplicates and results that fail verification do not earn.
- Who funds it?
- The job sponsor funds the budget before paid work opens. The job page shows its funding status.
Token details pending
The chain, contract address and official purchase link will appear here once they are verified. Use only the address published on this site and by @probecli.