Roadmap
Building the research layer for understanding who’s actually shipping.
Market tools answer “what is pumping?”. HEY answers “who is actually building, what changed, is the repository really theirs, did they ship something that matters, and can that be turned into a signal a person or a program can trust?”. Market data is context here. Builder activity, corroborated and sourced, is the product.
What makes HEY different
A DEX screener sees a pair. A launchpad sees its own launches. A GitHub dashboard sees commits with no idea which token they belong to. HEY joins the three and refuses to guess: a repository counts only when the project’s own site or code ties it to the token, a commit alone means nothing, and every claim carries the source it came from. The record grows every hour it is kept.
The order of the product
- 1Research — find every project on the chain, from every public source
- 2Discovery — connect a token to a site, a repository, a contract
- 3Verification — prove the token exists and the site names it
- 4Corroboration — prove the repository belongs to the project
- 5Meaningful activity — count only building, from corroborated sources
- 6Signals — turn activity into dated, explained, machine-readable events
- 7Alerts — deliver a signal to a person or a program that asked for it
- 8Agents — let programs read and watch the same evidence
Research → Signals → Agents. Each quarter below climbs one rung, and none can be built before the one under it holds.
- LIVE
- running in production, producing data
- SHIPPED
- deployed, but off, unused or without a user path — the note says which
- IN PROGRESS
- partly built; the note says what exists and what is missing
- PLANNED
- a committed direction; nothing built
- RESEARCH
- being worked out; may change shape or not happen
Q4 2026
Build the research layer
Make attribution trustworthy: a repository on a page belongs to that project, or it is context.
Starts from
The platform as it runs today. Most of this quarter is already live; the rest closes the gaps the audit found.
Unlocks · Q1 2027
Signals can only be as honest as the attribution under them. Everything in Q1 reads what this quarter proves.
19 items: 13 live, 4 in progress, 2 planned
Project discovery across the chain
Launchpad factory logs, DEX and market listings, ecosystem directories, GitHub code search over chain markers and the explorer’s published-source sync feed one candidate table; nothing reaches a page without the quality gate. Since 2026-09-27 a block window the chain would not answer is recorded and read again rather than skipped (8,681 missed launches recovered), new tokens are named within the hour, the trading lane runs hourly, a new project meets the gate within a quarter hour, and an operator can look up any contract to see whether HEY saw it and why it is not public.
LIVEThe quality gate
A launch record becomes a page on evidence only. A website several projects share is nobody’s; a deployer that launched several projects’ tokens attributes nothing. Re-run daily, and it demotes as readily as it publishes.
LIVERepository corroboration: declared, context, corroborated
A repository a launchpad merely declared is context until the site names the token or the code carries a chain marker. A borrowed repository’s commits never set a status. Name similarity alone never maps a repository.
LIVEVerified Builder
Published, and at least one meaningful ship from a corroborated source. A bare deployment is a launch, not building. The catalogue is the one writer of the label.
LIVEBuilder activity from public sources
Releases, weekly commit summaries, changelog and RSS entries, contracts with published source, follow-up deployments and upgrade watches are read on a schedule and recorded as ship events, each with the source it came from. Commits are read file by file: a week that only touched documentation, lockfiles, dependency or version updates, generated files, assets, data files or whitespace is shown and does not count as building.
LIVEResearch provenance on every ship
Every ship event carries an evidence row with its URL and content hash; retracted and disputed claims stay on the record and leave the feeds. The API and the MCP return the same provenance the page shows.
LIVEContracts, deployers and deployment dates
Creation transactions and blocks, follow-up deployments from the same deployer, shared-deployer detection, EIP-1967 proxy checks, chain and site verification of the token.
LIVEMarket context, kept in its place
Seven market sources behind one sanity guard and one precedence; market status, liquidity, pool depth, daily history, 15-minute and hourly candles for the Terminal chart, and the distribution map, all behind the builder story and never an input to a status or a score.
LIVEIs anyone building this? — the scanner
Paste a contract; HEY answers the builder question and nothing about risk, from the chain and its own tables. The same scan runs inside the Research Terminal too — from the ⌘K palette, which offers it for any address HEY does not track, or from More.
LIVEPublic API, feeds, badges
Read endpoints on the same query layer the pages use, each described in the OpenAPI document at /openapi.json; a by-contract lookup, RSS, an embeddable badge, llms.txt and sitemaps. No key needed.
LIVEScout tasks from HEY’s own gaps
A token whose site names another contract, or a repository HEY could not corroborate, opens a research task automatically and retires it when the gap clears.
LIVEContributor activity
Every weekly commit summary already stores commit count, active days, day-by-day commits and a distinct-contributor count — never a name. Missing: a per-project time series, counts beyond one page of commits, and any surface that reads them.
IN PROGRESSPost-launch development detection
Follow-up deployments and upgrade watches are live, but a few dozen projects carry a follow-up and no upgrade has ever been recorded. Missing: coverage across the catalogue and a link from a release to the deployment it produced.
IN PROGRESSHuman review of attribution
Moderators can approve, refuse, merge, retract and disown. Missing: a reviewer surface for the repository matches held for review, and a path for checking published source — the services exist and nothing calls them.
IN PROGRESSFork and template re-checks on a schedule
Forks and templates are refused at intake and penalised when mapped. A weekly job re-reads mapped repositories in bounded batches and demotes one that turns out to be a fork or a template: its ships stop counting, and the record keeps them with the reason.
LIVEProject flag and report from the page
A signed-in reader presses “Report an error on this page”, picks what is wrong — a repository, a site, a token — and may add a line. The report goes to HEY’s moderation queue as a data correction; a moderator checks it against sources, and a correction is written to the record. Reports are private and never read by scoring.
LIVERepository ↔ contract linkage
Which repository deployed which address. Today deployments attach to the project, never to a repository; a release and the deployment it produced cannot be joined.
PLANNEDRepository fingerprinting: mirrors, re-uploads, monorepos
Detect one codebase under several names, a vendored copy, and the package inside a monorepo that actually targets the chain; record a private repository that went public rather than counting its whole history as new.
PLANNEDUpstream multi-chain repositories
Since 2026-09-28 HEY reads Electric Capital’s open developer taxonomy each week: a repository it attributes that the taxonomy files under another project’s ecosystem, or under many ecosystems, goes to a reviewer, and nothing changes on its own. Whether upstream activity by a multi-chain wallet or protocol counts as building here is still a definition to settle.
IN PROGRESS
Q1 2027
Turn research into signals
Make what HEY already stores readable as dated, explained events — for people and for programs.
Builds on
Q4: corroboration and contributor data are the inputs; a signal built on uncorroborated activity is noise with a timestamp.
Unlocks · Q2 2027
A signal a reader can subscribe to, a program can poll, and an agent can quote with its reasons. Q2 delivers these; it does not define them.
18 items: 11 live, 1 shipped, 5 in progress, 1 planned
The signal engine
Hourly rules over HEY’s own tables: releases, deployments, development spikes and slowdowns, resumed and dormant builders, liquidity moves, graduations, verifications. Each signal carries its figures before and after and its source.
LIVEScore history and the Builder Radar
Every rescore that changes a status or a score is kept with its version; the Builder Radar ranks daily and keeps its inputs. What is missing is anything that reads the history as a trend.
LIVEWeekly report and This Week
What shipped, who became a Verified Builder, who came back, still building, under the radar — as a page, an API and a feed. A closed week is never rebuilt: a final reads exactly as it was published, and a rule change applies from the next week that closes.
LIVEHEY Today: what changed since your last visit
The Research Terminal opens on what changed since a reader last came, today, in 24 hours or in 7 days, read from the one change ledger, ranked by meaning rather than volume, with true counts for the window. Every row opens its evidence; a signed-out reader gets the same chain-wide view.
LIVEThe Research Summary
Every project opens on one answer per question — building, usage, market, contracts, security, the latest change and what HEY does not know yet — each tagged Fact, Derived or Unknown and linked to its evidence. The same lines reach the project page, the Terminal, the API, the MCP server and agents.
LIVEProduct usage, its own dimension
Whether what a project shipped is used: calls to its watched contracts, active contracts and distinct caller addresses per day — addresses, never people — from HEY’s own daily rollup. It sits beside building and market and never feeds a status, a score or a rank.
LIVESecurity context, never a verdict
Audit reports and where each is published, bug bounty programs, security.txt contacts, package advisories and repository checks, each with its source. There is no safety score and never will be; a missing reading says what was not read.
LIVEAsk HEY, everywhere in the Terminal
Press ⌘K and ask in English or Malay — what changed this week, compare two projects, why a figure is an FDV, follow a project, make an alert. Answers come only from HEY’s records, every line marked and linked; an action waits for the reader to confirm it. No view on price or trading.
LIVERelationships, peer context and research boards
What a project is connected to and why HEY thinks so, with evidence on every edge and no account ever a node; each figure placed among comparable projects one dimension at a time, never one score, saying so when there are not enough peers; and private boards of projects and panels a reader keeps.
LIVEResearch Terminal early access
The Terminal’s preview is open to everyone. The full research opens by request — connect a wallet (one signature, no transaction) and ask, and the team reviews each request by hand — or by holding: $HEY worth the team’s dollar minimum at the time of HEY’s daily check, valued at HEY’s own market reading, opens it without a request and is checked again each day. Holding never changes what the research says.
LIVEWatchlists, updates and the digest
Follow a project, read what changed — ships, status moves, contract changes and its signals — take a private feed, opt in to email by double opt-in. Built and deployed; almost nobody uses it yet.
SHIPPEDComparative windows
The signal engine compares seven days against the seven before and thirty against thirty for ship counts. Project intelligence adds meaningful development over the last thirty days against the thirty before, and Build Momentum, release cadence and liquidity now against thirty days ago, in the API, the MCP server and the Terminal. Missing: the same windows over contributors and contract usage, and a history endpoint beyond that one thirty-day step.
IN PROGRESSMeaningful Shipping Signal
Designed, not built: a signal that fires on corroborated, non-fork, multi-source activity that accelerated against its own past — and explains why it fired. The design, its inputs and their coverage today are in the architecture plan.
IN PROGRESSSignals everywhere the evidence already goes
Signals already reach the watchlist updates, the digest and the private watchlist feed, the MCP server’s get_changes tool, and the API, which returns one project’s signals with /api/signals?slug=. Missing: a public signals feed.
IN PROGRESSNew builder and first-repository detection
A Verified Builder signal exists; a first public repository, a first release and a first deployment do not. Contributor growth as a signal needs the time series from Q4.
PLANNEDAlerts: rules, webhooks and Telegram, alert-only
Webhooks are live: an account subscribes a URL to releases, deploys, status moves or site changes and receives each event signed, with its sources, through a delivery ledger — tested end to end on 2026-09-27. Alert rules followed (2026-09-28): a reader picks a sentence — a release, an implementation change, an unlock due within seven days — for a project, their watchlist or any project, and sees each match in HEY with its evidence, by email at most hourly, or at their own webhook. Telegram is built and switches on once HEY’s bot is registered. Missing: delivery of signals rather than ledger events. Nothing here fires on price.
IN PROGRESSCommit significance
Every human commit HEY reads is classified by the files it changed — source, tests, configuration, documentation, lockfiles, generated output, assets, data, whitespace — read once and kept. A week of documentation or maintenance only is shown as that and no longer counts toward a status, a badge or Build Momentum; Still Building needs more than commit summaries.
LIVEPull requests and release significance
HEY now reads merged pull requests — the number, the merge time and whether automation opened them, never who or a title — and draws them beside commits and exact-time releases on the Terminal chart’s code lane. Whether a merged pull request or a release is more than a version bump is still being worked out; a merged pull request alone is never a ship or an input to a status.
IN PROGRESS
Q2 2027
The Shipping Signal Agent
A Telegram agent that tells a subscriber when meaningful shipping was detected — and lets them decide what to do with it.
Builds on
Q1: the Meaningful Shipping Signal, its explanation, and the subscription model. The agent is a delivery surface for a signal that already exists; it computes nothing of its own.
Unlocks · Q3 2027
The first channel where HEY reaches a person before they open the site. Alert-only is the only mode: HEY holds no keys, trades nothing and never tells anyone to buy or sell.
4 items: 1 shipped, 1 in progress, 2 planned
Telegram today
One outbound bot that alerts the operators when the platform is degraded. No inbound commands, no subscriptions, no product messages. The client is the only piece the agent reuses.
SHIPPEDChat binding and subscriptions
Built (2026-09-30), not yet switched on: a signed, expiring link binds a private Telegram chat to a HEY account, the way an email address is confirmed, and alerts can be sent there; one place to unlink. It switches on once the bot is registered.
IN PROGRESSUser-defined rules
Signal threshold, minimum project confidence, minimum contributors, a recent release or deployment, allow and block lists, cooldowns. Rules filter; they never change the signal.
PLANNEDAlert-only mode
Project, token, what changed, sources and confidence, with market context labelled as context, and two buttons — research and watch. No button to trade: HEY holds no keys and never tells anyone to buy or sell.
PLANNED
Q3 2027
HEY for agents
Make HEY an intelligence layer other programs run on: hosted, subscribable, and explainable in the same words everywhere.
Builds on
Q2: a signal that has been delivered, argued with and corrected in the open. Q1: the endpoints those agents read.
Unlocks
Humans, bots and agents reading one evidence graph, with HEY’s own agent as one client among many.
12 items: 8 live, 2 in progress, 2 research
The MCP server
13 tools over the canonical API since 2026-09-26 (14 where Market Integrity is published): snapshot, changes, coverage, explain, evidence, contracts and diff, each answer tagged FACT, DERIVED or UNKNOWN and linked to the JSON it came from, with resources and research prompts. On npm since 2026-09-27: npx -y @hey-research-lab/mcp. Listed in the Official MCP Registry as io.github.hey-research-lab/hey-research since 2026-09-28.
LIVEA hosted MCP endpoint
POST /mcp since 2026-09-26: the same tools over stateless Streamable HTTP, reading the public API as the caller, so the API’s limits, keys and quotas apply unchanged.
LIVEThe SDK
A typed client over the public API, held to the API by a contract test: npm install @hey-research-lab/sdk, since 2026-09-27.
LIVEStructured feeds and webhooks
One change ledger with stable ids and a cursor (/api/changes) that every surface reads, and webhook delivery of the same events, signed, with a ledger of every attempt. Missing: signal subscriptions as their own API.
LIVEResearch interpretation, AI-assisted
In the Research Terminal a reader asks in English or Malay; a model reads only HEY’s own evidence packet, cites every statement, and a guard holds back any answer that invents a record, claims intent or talks trading. It is an interpretation beside the evidence answer: it changes no status, score, badge or rank, and it is evaluated against fixed cases before each change.
LIVEDiscovery by agents that have never heard of HEY
An agent finds HEY through the Official MCP Registry, llms.txt, an A2A Agent Card with six read-only research skills, an OpenAPI description and an agents guide; one identity — name, domain, chain, $HEY contract, endpoints — is held equal across all of them by a test. Discoverability is not promotion: HEY’s own project gets no ranking advantage.
LIVEAgent research receipts
A neutral receipt format for any project: an agent states its claims, risks, unknowns and the HEY evidence ids behind them, and HEY checks that the cited ids exist and are public. HEY stores nothing, fetches nothing a receipt names and never endorses a conclusion.
LIVEFirst integrations
Orus, an autonomous desk on Robinhood Chain, reads HEY research as optional entry filters in its strategies since 2026-09-28: every HEY filter starts off, missing data refuses rather than passes, and HEY never controls an exit. HEY supplies the research; the operator chooses the rules.
LIVEAgent watchlists and research workflows
An agent can already watch projects through alert rules and webhooks over the API, keep research boards, and hand research tasks to HEY over A2A. Missing: an agent asking for research through the same request path a person uses.
IN PROGRESSMachine-readable provenance
Every published claim has a stable typed id (ship:, source:, abi:, lock: …) that resolves to its receipt at /api/evidence/{id}, and the explain engine says why a figure reads as it does; each project’s relationships are a graph whose every edge carries its evidence and observed time. Missing: the whole record exported as one graph of claims with their sources and checked-at times.
IN PROGRESSReputation: builders, projects, researchers, reviewers
Scout credits and review outcomes are recorded; nothing scores a person yet, and the platform never will across wallets. What a reputation can honestly be built from is the question.
RESEARCHCross-chain builder discovery; StockFi and RWA builders
Every table is chain-keyed and one chain exists. Stock Tokens have an adapter that is switched off and no published page. Both are decisions before they are work.
RESEARCH
$HEY
Where the token sits
The token pays for research work and prices the things that would otherwise be spammed. It never buys a status, a score or a rank, and a test fails the build if it could. As signals and alerts arrive, the same tiers govern how much, how fast and through which channel — never whether a signal exists. Basic evidence stays free so the platform’s value is visible without a token.
Research bounties, tranches and the holders-first window
Bounties fund evidence work from the treasury or a requester; payouts in two tranches; holders may claim first for a day and then anyone may. The one $HEY gate that has changed who could do something.
LIVEBonds against spam
A refundable deposit to claim a task or submit a project, quoted in dollars and paid in $HEY. It has caught unmined and invalid deposits already.
LIVEResearch requests, free and paid
Paid requests move a project up the research queue; they never touch a status, a score or a rank, and a test enforces it.
LIVELinked wallets, tiers and entitlements
The identity spine every gate hangs on: one address per account, a daily balance check with hysteresis, editable thresholds.
LIVETreasury ledger and balances
HEY’s ledger records every HEY payment its research economy handles — research requests, bounty funding and payouts, bond deposits and refunds — with its transaction, and HEY reads the treasury’s balance from the chain every day. The creator tax is paid to the treasury by the Pons pool hook when fees are swept; HEY has not yet recorded which asset each payment arrived in, and none of it is in the ledger yet, so no monthly statement has been published. Missing: a writer for the creator-tax sweeps.
LIVEAPI tiers and monthly allowances
Keyed access with per-tier monthly allowances runs on every read endpoint, and keys are in use. The same tiers will govern alert volume, channels and agent access — never whether a signal exists.
LIVEMonthly holder vote
One balance weighs a round once, at the closing block; advisory only. No round has been opened yet; the first one is a decision, not code.
SHIPPEDEarly access to research notes
Holders read a note before it is public. No note has been written yet, so the gate guards an empty room until research notes exist.
SHIPPEDSponsored placements
Labelled, priced, confirmed on chain, kept out of every ranking. Switched off; whether it opens is a product decision.
SHIPPED$HEY, readable by machines
One public profile an agent can read like any project’s: contract, supply, locks, market facts with the valuation labelled as what it is, and every utility marked live, planned or retired. Researched by the same rules as every other project.
LIVEScout staking and evidence challenges
Designs behind flags the configuration refuses to enable. They stay refused until reviewer throughput, not token design, is the bottleneck they solve.
RESEARCH
What is not on this roadmap
Wallet analytics, smart-money or whale labels, and anything that follows a wallet. Price predictions, trending lists, and scores that cannot be explained from evidence. Ranking that can be bought. A commit read as a buy. Any suggestion that continued building says anything about price. Trading, paper or real, and any network that executes. These are not later; they are out.
How the statuses and rules are decided is on the methodology page. The audit behind this page is the roadmap audit, and the plan for the signal and the agent is the architecture document.