Skip to content

PROBE

AI Agents · Infrastructure

AI-written tests for Uniswap v4 hooks, replayed twice by a verifier and paid on-chain once per new execution path.

What HEY knows

Development

Shipped this weekShipping: 2 counted ships in 30 days; latest ship today. Evidence Source

Build Momentum 38How it is measured

Latest: probe 0.2.0: write your own cases

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts PROBE on your private watchlist; its changes then lead “Since you were last here” when you come back. Following needs an account; browsing never does.

Sign in to follow PROBE

No account? Email me PROBE’s changes

No account and no password. HEY stores the address and what you asked for, sends one confirmation, and nothing else until you confirm. Every email has a one-click unsubscribe that deletes the address.

Or read its RSS feed.

More detail
Product usage
UnknownThe project has a contract, but HEY does not count its calls yet: a token joins the watch once it takes calls in a thirty-day window, and any contract the project’s own sources name is watched. Unknown, not zero.
Contracts
Fact1 contract on record for code changes, 1 with published source code; no implementation or interface change recorded.
Not yet known
Unknown1 gap: API description (no source). Its website links no API description.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Shipping.
“Shipping” by the activity rule: 2 counted ships in the last 30 days, the newest 2026-11-19.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsprobe 0.2.0: write your own casesCode changes this week (since Mon 16 Nov) · 17 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Shipping”.Not concludedIt says what HEY can read of the building, not how good the project is, who is behind it, or what its token will do. Quiet or unknown is not "abandoned".
Verified Builder.
The quality gate found counted building from the project's own sources.
Source15 registered sources, 1 of them context only.Recordsprobe 0.2.0: write your own casesCode changes this week (since Mon 16 Nov) · 17 commitssource:9566321f-346a-490c-978b-6b079c2a77ac+4 moreWhat HEY derivedThe quality gate’s stored decision: “Verified Builder”.Not concludedA verified builder is one whose shipping HEY confirmed from public evidence. It does not say who runs the project — that is the ownership claim, a separate check.
Research coverage: HEY can answer 9 of the 10 research questions that apply.
9 of 10 applicable dimensions measured.

Identity

  • IdentityMeasured

Building

  • Building activityMeasuredRead 1h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 8h ago.
  • TimelineMeasured

Official site

  • Official docsMeasuredRead 6h ago.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 8h ago.

Code and packages

  • Repository detailsMeasuredRead 8h ago.
  • Published packagesMeasuredRead 8h ago.

Not applicable here: Package advisories, Contract creation, Contract activity, Published source code, Contract interface, Current market, Market history, Supply distribution, Locks, Market checks, Protocol economics.

A count of what HEY has read, never a score: projects are not compared or ordered by it. Unknown is never zero. The same states: coverage API.

Market figures are context only and never change activity status. Methodology

Latest ship

Checked

probe 0.2.0: write your own cases

GitHub releaseSource-backed

Why it matters: The first release HEY has recorded for this project.

Operators can now work a job without an AI key, by writing cases themselves. Added · probe case new writes a case that already meets the job's structural rules, with the fixture's helper functions and their docs listed in it. · probe case check <file...> runs the rule check and… Show all
  • Operators can now work a job without an AI key, by writing cases themselves. Added
  • probe case new writes a case that already meets the job's structural rules, with the fixture's helper functions and their docs listed in it.
  • probe case check <file...> runs the rule check and a local run on your case files, says which test failed and why, and exits 1 when a case would be rejected, so it can gate CI.
  • probe work --case runs and submits your files instead of the agent's or the seed cases.
  • probe job prints a job's brief: chain and contract…

Record ship:58364439… · HEY counts it as building; it does not judge the release’s quality.

Release, read from the team’s GitHub · no deployment linked
What it names
The team’s release names it: “probe 0.2.0: write your own cases” (v0.2.0).
Stage
A release is code the team published; HEY has not observed it deployed unless a link below says so.
Reported by
Read from the team’s GitHub. Reported in the team’s own source. No independent record HEY holds corroborates it.
Release and deployment
Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.
Activity
No contract is tied to this change, so no product activity is attributed to it. Product usage is read on its own.
When
The source dates it 2026-11-19 12:02 UTC; HEY first knew on 2026-11-19.
Not known
  • HEY does not hold the commit the release was cut from.
  • HEY has not observed a deployment of this change.
  • Not established: the text HEY holds names none of the project’s contracts (HEY holds the first 600 characters of it). Timing alone never links a release to a deployment.

Evidence: ship record

A ship says what was shipped and where HEY read it. It is not a judgement of quality, of the team, or of what the token will do.

Builder activity

2 meaningful, source-backed ships in the 1 week since HEY began reading this project’s sources; earlier weeks are not yet read, not zero.

1-week shipping streak

Build timeline

A code week counts as building when a commit HEY looked inside changed code; one is enough, so HEY stops there.

  1. Code changes this week (since Mon 16 Nov) · 17 commits

    Code activitySource-backed

    3 active days in probecli/probe.

    How HEY read this week

    This week HEY looked inside 1 of 17 commits to see what changed: 1 changed code. One code change is enough for the week to count, so HEY stopped there.

Other changes on HEY’s record

4 changes on HEY’s record for PROBE: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 1 week of code pushed.

All 4 changes for PROBE →

The full change record holds 1 more, of kinds this list leaves out — new locks, unlock reminders and HEY’s own research bookkeeping among them. Full record (JSON)

Sources

15 places HEY reads for PROBE
7 more sources (docs)