Skip to content

Builder guide

Get your project right on HEY. HEY reads what your project publishes and says what it can confirm. Nothing here is paid for, and nothing you do changes a score directly: you make your work readable, and HEY measures it the same way for every project.

  1. Get researched

    HEY finds most Robinhood Chain tokens on chain by itself. If yours is missing, submit it with one thing HEY can check: a contract on Robinhood Chain, a public repository or a live website. Check there first whether it already has a page.

  2. Get linked

    Link your repository, changelog or release feed, docs and your product contracts (as their page on robinhoodchain.blockscout.com or robin.etherscan.io) from your own website, and name your token’s contract there. HEY reads your site and maps only what it vouches for; a link from your own domain is what makes a source official. Contracts can also be linked from your docs page, when it lives on your own domain.

  3. Read as shipping

    Shipping means a meaningful, source-backed ship in the last 7 days; active one in the last 30. A release, a deployment, a dated changelog entry or a week of commits that change code counts, and a repository’s releases of one day count once, as do contracts your deployer puts up in one run (each within 60 seconds of the last); a deployment within 24 hours of your token’s creation is launch provenance, not building. A merged pull request, a week of only docs, CI or other upkeep files, a commit that only bumps dependency or package versions, commits from bots or scripts, or a rolling build tag does not; a week of 25 or more commits counts when 3 of a 10-commit sample change code. The full rule.

    “Not measured — activity not measurable” means HEY has a ship on record but nothing it can keep reading: step 2 fixes it.

  4. Become a Verified Builder

    HEY holds evidence of shipping from the project’s own sources. HEY awards it when an official source carries a meaningful ship and the project has evidence on Robinhood Chain. It says what you shipped, not who runs the page — that is the claim, step 5 — and not whether you are shipping this week; your activity status says that.

  5. Claim your page

    On your project page, press “Claim this project”. Prove control with admin of the registered GitHub repository (about a minute, nothing to publish), a signature from the key that launched, owns or deployed the token (or the fee recipient its Pons launch names), a DNS TXT record, or a file or meta tag on your site. Sign in with GitHub or a wallet; only the GitHub proof needs GitHub. Proving ownership changes no status, score or order on its own.

    Or install the HEY GitHub App on your repository from the claim page or your share pack: GitHub confirms you installed it, so the claim is proved with nothing to publish, and HEY then reads your releases and pushes a little sooner. It is read-only by default, never posts for you, and a delivery is never a ship by itself.

    Once you have proved control, your account lists the page under Your projects, with its share pack — the GitHub App, your badge and a post that states only what HEY recorded.

  6. Keep it accurate

    Once claimed, “Submit an update” posts what you shipped, dated up to 14 days back; it is self-reported until a HEY moderator checks it against the evidence you link, and only then counts. You can also edit your description, website, sources and product contracts: a repository, docs page, changelog or feed you add counts once something ties it to the project — your GitHub claim names it, it names your token, or a moderator confirms it. Every change is recorded. Anyone can report an error from the page; a moderator checks it against sources. Anything else: hi@heyresearch.xyz.

  7. Show it

    Every published project has a badge image at /api/badge/your-project for a README or site — the same address your share pack and the GitHub App’s badge pull request use; its page, /badge/your-project, hands out the snippets. A live widget is in the embed kit. Both state only what HEY checked — status, last ship, Verified Builder when held — never a price, a score or a rank. What the badge gives you is the backlink and the readers who click it: every click lands on your page labelled as a badge visit, and /badge/your-project shows how many arrived that way in the last seven days. When HEY finds the badge on your own site or README, your project also joins Badge placements — a thank-you list, alphabetical, and not a benefit: it changes nothing else on HEY.

Open-source tools

HEY publishes open-source tools for builders: a project manifest (/.well-known/hey-project.json), a GitHub Action that writes ship evidence, a chain marker check (chainprint), a registry of Robinhood Chain infrastructure, and the embed as an npm package. They help you describe your project in one consistent format.

HEY’s research does not read the manifest, the ship evidence or the registry yet: what counts today are the steps above. A file you publish is your declaration, never a check HEY made.

Every definition in full, with its version: Methodology. Sponsored placements are a separate, labelled row and never change research: how they work.

Builder guide: get your project right on HEY | HEY Research Lab