Skip to content

Nullfill

Infrastructure

Is this your project? Claim it →

An escrow for Robinhood Chain that doesn't strand your money when a transaction is screened at the sequencer. Settles in USDG.

What HEY knows

Development

Last shipped 11 days agoActive: 1 counted ship in 30 days; latest ship 11 days ago. Evidence Source

Build Momentum 27How it is measured

Latest: Code changes, week of 2026-11-02 – 2026-11-08 · 1 commit

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Nullfill 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 Nullfill

No account? Email me Nullfill’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
Not yet known
Unknown2 gaps: Official docs (no source), API description (no source). HEY read its website and found no link to docs.
Compare with…The same summary, with every line’s evidence: snapshot API
What HEY checked — why it says this
Active.
“Active” by the activity rule: 1 counted ship in the last 30 days, the newest 2026-11-02.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 1 commitCode changes, week of 2026-10-05 – 2026-10-11 · 17 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 23 commitsWhat HEY derivedHEY’s activity rule reads the counted events as “Active”.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.
Source4 registered sources, 0 of them context only.ReadRecordsCode changes, week of 2026-11-02 – 2026-11-08 · 1 commitCode changes, week of 2026-10-05 – 2026-10-11 · 17 commitsCode changes, week of 2026-09-28 – 2026-10-04 · 23 commits+3 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 8 of the 10 research questions that apply.
8 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 4h ago.
  • RepositoriesMeasured
  • ReleasesMeasured
  • TimelineMeasured

Official site

  • Official docsNo sourceHEY read its website and found no link to docs.
  • API descriptionNo sourceIts website links no API description.
  • Official site changesMeasuredRead 6d ago.

Code and packages

  • Repository detailsMeasuredRead 2d ago.
  • Published packagesMeasuredRead 2d 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

Code changes, week of 2026-11-02 – 2026-11-08 · 1 commit iamrobertmoore/nullfill

Code activitySource-backed

Why it matters: First week of code changes after 22 quiet days.

1 active day in iamrobertmoore/nullfill.

This week HEY looked inside 1 commit to see what changed: 1 changed code.

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

Code changes, read from the team’s GitHub · not a deployment
What it names
1 of 1 commit HEY read changed code. A week of code names no capability.
Stage
Code changes are not a deployment: HEY has not observed a release or a deployment of this code.
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 a release or a deployment: code is not 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 to the week of 2026-11-02; HEY first knew on 2026-11-02.
Not known
  • No source HEY holds names what this change does.
  • HEY has not observed a deployment of this change.

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.

Shared change · Published

Nullfill was published on HEY with its sources recorded.

Builder status: Active.

Observed by HEY on 2026-09-29Source: HEY’s research record

Builder activity

Bars: meaningful, source-backed ships per week (count). Weeks run Monday to Sunday, UTC, labelled by their Monday. Commits are aggregated, a code week counted once. Hatched: 5 weeks before HEY began reading this project’s sources — not yet read, not zero.

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, week of 2026-10-12 – 2026-10-18 · 2 commits iamrobertmoore/nullfill-worldsfair

    Code activitySource-backed

    2 active days in iamrobertmoore/nullfill-worldsfair.

    Documentation or maintenance only — not counted as building. This week HEY looked inside 2 commits to see what changed: 2 documentation or maintenance only.

  2. Code changes, week of 2026-10-05 – 2026-10-11 · 17 commits iamrobertmoore/nullfill-worldsfair

    Code activitySource-backed

    3 active days in iamrobertmoore/nullfill-worldsfair.

    How HEY read this week

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

  3. Code changes, week of 2026-09-28 – 2026-10-04 · 23 commits iamrobertmoore/nullfill

    Code activitySource-backed

    3 active days in iamrobertmoore/nullfill.

    How HEY read this week

    This week HEY looked inside 3 of 23 commits to see what changed: 1 changed code, 2 documentation or maintenance only. One code change is enough for the week to count, so HEY stopped there.

Other changes on HEY’s record

5 changes on HEY’s record for Nullfill: 1 new project on HEY · 4 weeks of code pushed.

All 5 changes for Nullfill →

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

Sources

4 places HEY reads for Nullfill