Skip to content
HEY Research Lab
Menu

Robinhood Feed Bench

No known affiliation with Robinhood — HEY holds no evidence of one.The name borrows Robinhood’s brand; a builder HEY verified is not Robinhood.

Is this your project? Claim it →

Latency benchmark for Robinhood Chain feeds: connects to the official Nitro feed, Eira Pulse gRPC and any JSON WebSocket feed from one host, stamps every message on arrival and reports who was first per block and per transaction (p50/p90/p99, pairwise, by block size).

Read more

What HEY knows

Development

Last shipped 26 days agoActive: 3 counted ships in 30 days; latest ship 26 days ago. Evidence Source

Build Momentum 26How it is measured

Latest: v0.2.0

Token

No token tracked
FollowCreate alertTerminal preview
Get updates

Get updates

Follow puts Robinhood Feed Bench 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 Robinhood Feed Bench

No account? Email me Robinhood Feed Bench’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.

View latest ship
Share
More detail
Not yet known
Unknown4 gaps: Brand (not confirmed), Official docs (no source), API description (no source), Official site changes (no source). Its name or ticker uses Robinhood’s brand. HEY holds no evidence that Robinhood is involved with it; it is researched like any other project.
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: 3 counted ships in the last 30 days, the newest 2026-10-09.
SourceRepositories, changelogs and feeds HEY reads for this project, and the ship events recorded from them.Read · staleRecordsv0.2.0Code changes, week of 2026-10-05 – 2026-10-11 · 12 commitsv0.1.3+2 moreWhat 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.
Source3 registered sources, 2 of them context only.ReadRecordsv0.2.0Code changes, week of 2026-10-05 – 2026-10-11 · 12 commitsv0.1.3+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 7 of the 10 research questions that apply.
7 of 10 applicable dimensions measured.

Identity

  • IdentityMeasuredRead 45d ago.

Building

  • Building activityMeasuredRead 5h ago.
  • RepositoriesMeasured
  • ReleasesMeasuredRead 26d 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 1d ago.
  • Published packagesMeasuredRead 1d 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

v0.2.0

GitHub releaseSource-backed

Why it matters: One of a run of ships in the 30 days to it: building continued, not a one-off.

Full Changelog: https://github.com/qskateboard/robinhood-feed-bench/compare/v0.1.3...v0.2.0

Record ship:d146bddd… · 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: “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. 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-10-09 21:05 UTC; HEY first knew on 2026-10-09. HEY indexed it later, as history.
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. 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.

View evidence ↗ (opens in a new tab)Post this ship on X

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-10-05 – 2026-10-11 · 12 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    3 active days in qskateboard/robinhood-feed-bench.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-10-05 – 2026-10-11 · 12 commits (opens in a new tab)

  2. v0.1.3

    GitHub releaseSource-backed

    Full Changelog: https://github.com/qskateboard/robinhood-feed-bench/compare/v0.1.1...v0.1.3

    View evidence: v0.1.3 (opens in a new tab)

  3. Code changes, week of 2026-09-21 – 2026-09-27 · 4 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    2 active days in qskateboard/robinhood-feed-bench.

    How HEY read this week

    This week HEY looked inside 4 commits to see what changed: 1 changed code, 3 documentation or maintenance only.

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

  4. 2 releases in qskateboard/robinhood-feed-bench on 19 Sep

    GitHub release

    Show all 2 releases

    1. v0.1.1

      GitHub releaseSource-backed

      Full Changelog: https://github.com/qskateboard/robinhood-feed-bench/compare/v0.1.0...v0.1.1

      View evidence: v0.1.1 (opens in a new tab)

    2. v0.1.0

      GitHub releaseSource-backed

      Full Changelog: https://github.com/qskateboard/robinhood-feed-bench/commits/v0.1.0

      View evidence: v0.1.0 (opens in a new tab)

  5. Code changes, week of 2026-09-14 – 2026-09-20 · at least 2 commits

    Code activitySource-backed

    What changed, in the repository’s own words:

    1 active day in qskateboard/robinhood-feed-bench.

    How HEY read this week

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

    View evidence: Code changes, week of 2026-09-14 – 2026-09-20 · at least 2 commits (opens in a new tab)

Sources

3 places HEY reads for Robinhood Feed Bench