About HoodTape

HoodTape is an independent directory and data service for Robinhood Chain. It exists because the chain moved fast, the tool listings that followed were mostly affiliate pages, and nobody was writing down what could actually be verified.

Last verified: 2026-08-25

What we do

Two things. First, we run our own indexer against the chain and keep the results. Second, we publish comparison pages for the tools people use on the chain, with a stated fee, a stated custody model, and a date beside every claim.

The indexer polls the public RPC over HTTP, decodes Uniswap v4 pool and swap events and the launchpad's token creation events against verified contract ABIs read from Blockscout, and writes them to a local database. From that we derive the numbers a chart site does not show: how many tokens launched in a day, how many cleared their launch, how many still had a trade twenty-four hours later, how many distinct wallets traded, and which wallets keep appearing in the first minutes of launches that later went somewhere. That is the material behind the nightly tape.

The pipeline is read-only by design and in code. It signs nothing. It holds no keys. It has no wallet. It cannot custody, route, or execute anything, which means the worst outcome from a bug on our side is a wrong number on a page rather than a lost balance in your wallet. We consider that a design constraint, not a limitation.

The publishing rules

Every page on this site follows the same three rules. They are short enough to check us against.

1. A claim carries its source or it does not appear

Each page lists the URLs it was built from, in the page source, and shows the date the page was last checked. Where a fact comes from a vendor's own marketing rather than from an independent check, the page says so in the sentence that uses it. Where two sources disagree, the page names the disagreement rather than picking the more convenient number.

2. "Not verified" is a publishable answer

A fee we could not confirm is written as "not stated publicly". A referral rate we could not confirm is written as "terms not published". We do not fill a table cell with a plausible guess to make a table look complete, and every comparison page ends with an explicit list of what we could not verify. That list is the most useful part of the page, because it tells you where to do your own work.

3. Ranking is not for sale

Tools are ordered by how useful they are for a stated job, never by commercial relationship. There is no paid placement, no sponsored row, and no "featured" tier. A tool that pays us nothing sits above a tool that pays us something whenever it is the better answer.

How referral links work here

This is the part most directory sites are vague about, so here is the whole mechanism.

Every outbound tool link on this site is written into the HTML as the plain, public URL for that tool, with a data-tool attribute naming it. A single file, /refs.js, holds a map called REF_LINKS with one entry per tool. Every entry starts as an empty string. An empty entry means the link stays exactly as written in the HTML: no referral code, no redirect, no tracking parameter.

If we later establish a real referral relationship with a tool, we fill in that entry, and the browser swaps the href when the page loads. You can read that file yourself, at any time, and see precisely which links are referral links and which are not. Nothing is hidden in a redirect chain, and the swap happens in your browser without any request leaving the page.

Two commitments go with that. A referral link never changes the price you pay. A referral link never changes a tool's position in a table or the words written about it. If a tool we earn from has a bad fee, a custodial key model, or an unverifiable claim, the page says that, in the same plain terms it uses for everyone else.

What we do not do

Corrections

Facts go stale, and this subject moves faster than most. Fees change. Tools add and drop chain support. A referral programme opens or closes. A vendor quietly rewrites a docs page. If you find something on this site that is wrong or out of date, tell us and we will fix it and re-date the page. A correction is a normal event here, not an embarrassment.

Two things speed a correction up considerably: the exact page and sentence, and a link to a source we can read. Corrections that arrive with a source are usually live the same day. Corrections that arrive as an assertion take longer, because we still have to go and check.

Where to start

If you are building on the chain, start with RPC and explorer, which has the network parameters, the API record caps, and the provider list. If you are trading on it, start with how pools.trade works, then the screener comparison. Before you buy anything launched by a stranger, read scams and safety. It is the shortest path to not losing money to a pattern that is already well documented.