Skip to content
HEY Research Lab
Menu

Distribution Contracts

Integration record: HEY holds no Robinhood Chain evidence for this project (no token, contract or registry listing on the chain), so its ships are recorded here but it is not a Verified Builder.

Is this your project? Claim it →

distribution-contracts

What HEY knows

Development

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

Build Momentum 20How it is measured

Latest: Code changes, week of 2026-10-26 – 2026-11-01 · 1 commit

Token

No token tracked
Follow
MoreCreate alertTerminal preview
View latest ship
Share

Get updates

Follow puts Distribution Contracts 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 Distribution Contracts

No account? Email me Distribution Contracts’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
Unknown3 gaps: Official docs (no source), API description (no source), Official site changes (no source). No official website on record.
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-10-26.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.ReadRecordsCode changes, week of 2026-10-26 – 2026-11-01 · 1 commitCode changes, week of 2026-09-21 – 2026-09-27 · 1 commitv2.1.0 — V2 security audit 2026-08What 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".
Research coverage: HEY can answer 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 2h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 3mo ago.
  • TimelineMeasured

Official site

  • Official docsNo sourceNo official website on record.
  • API descriptionNo sourceNo official website on record.
  • Official site changesNo sourceNo official website on record.

Code and packages

  • Repository detailsMeasuredRead 3d ago.
  • Published packagesMeasuredRead 3d 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
LinksGitHub (opens in a new tab)Sources

Latest ship

Checked

Code changes, week of 2026-10-26 – 2026-11-01 · 1 commit

Code activitySource-backed

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

What changed, in the repository’s own words:

1 active day in dobprotocol/distribution-contracts.

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

Record ship:5c64c9d7… · 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-10-26; HEY first knew on 2026-10-27.
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.

View evidence ↗ (opens in a new tab)

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: 4 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-09-21 – 2026-09-27 · 1 commit

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in dobprotocol/distribution-contracts.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-21 – 2026-09-27 · 1 commit (opens in a new tab)

  2. v2.1.0 — V2 security audit 2026-08

    GitHub releaseSource-backed

    Security audit of the V2 stack (August 2026) and the Base mainnet deployment that carries it. Every fix carries an AUDIT 2026-08 ( ) comment stating what was possible before, so it does not get "simplified" back, plus a test that now requires the attack to fail.… Show all
    • Security audit of the V2 stack (August 2026) and the Base mainnet deployment that carries it. Every fix carries an AUDIT 2026-08 ( ) comment stating what was possible before, so it does not get "simplified" back, plus a test that now requires the attack to fail. DistributionPoolV2
    • B-1 — createDistribution was owner-gated only on Reward pools. On Treasury and Payroll anyone could pick the moment of the snapshot, and with it who got paid. It is now owner-only on all three; opening it is an explicit setPublicDistribution(bool) opt-in by the owner, false by default.…
    View evidence: v2.1.0 — V2 security audit 2026-08 (opens in a new tab)

Other changes on HEY’s record

5 changes on HEY’s record for Distribution Contracts: 1 release · 1 new Verified Builder or owner proof · 1 new project on HEY · 2 weeks of code pushed.

All 5 changes for Distribution Contracts →

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

Sources

1 place HEY reads for Distribution Contracts