Robinhood Chain token discovery methodology
Token "discovery" on Robinhood Chain means the process by which a newly deployed ERC-20 becomes visible in a screener or watchlist. This page documents the exact inputs Nock Terminal uses to see a token for the first time, how quickly a discovery propagates to product surfaces, and which categories of tokens the method is expected to miss.
The discovery pipeline is intentionally biased toward tokens that are actually tradable on chain 4663. A token that is deployed but never paired against a base asset in a live pool is technically on-chain, but from a trader's point of view it is not discoverable until liquidity exists. Nock Terminal is an independent product with no affiliation to, and no partnership with, Robinhood Markets, Inc. Everything below describes how our own indexers compute the numbers; the underlying network is defined by the Robinhood Chain docs and its public Blockscout explorer.
In this article, see also: new pairs methodology · trending methodology · what counts as a liquidity pool · compare discovery coverage and verification boundaries.
Definitions
A "discovered token" is an ERC-20 contract on chain 4663 that (a) has at least one pool with non-zero reserves against a supported base asset and (b) has emitted a Uniswap v4 pool-initialisation event we have indexed.
"First-seen" is the timestamp of the earliest indexed pool-initialisation event for the token. It is not the token's contract-deployment timestamp; a token can exist for a long time before its first pool is created.
Inclusion and exclusion rules
Discovery only considers tokens whose bytecode implements the ERC-20 interface as documented at ethereum.org. Contracts that mimic ERC-20 events but do not implement the standard are excluded from screener surfaces because their balances and transfers cannot be interpreted safely.
Tokens with a verified contract on Blockscout are preferred inputs. Unverified contracts are still discoverable, but they are surfaced with an explicit "unverified" flag downstream so the reader knows the source has not been checked against readable code.
Sampling window and freshness
Pool-initialisation events are polled continuously from the indexer's tip of chain. Under normal conditions the delay between event finality and screener visibility is on the order of a block; longer delays can occur during indexer reorgs or upstream outages, in which case the affected time window is republished once caught up.
Calculation
For each pool-initialisation event we emit, the token addresses are cross-referenced against previously discovered tokens; new addresses become new discoveries. No pricing, ranking, or trending weight is applied at discovery — those steps live in the trending and volume methodologies documented separately.
Known blind spots and caveats
Tokens that live on chains other than 4663 are not discovered here, even if they share a name with a Robinhood Chain token. Bridged wrappers whose canonical asset is on another chain are surfaced with an explicit provenance note.
Tokens deployed but never paired into a pool remain invisible to discovery. This is intentional — an untraded token has no market price, no liquidity, and no honest way to be ranked.
Correction policy
If a definition, filter or calculation on this page is wrong, out of date, or contradicts a primary source, the primary source wins and we correct the page. Report errors via the contact channel linked from the Nock Terminal footer with the URL, the disputed statement, and a citation to the correct value.
Methodology changes that materially affect any published number are noted in-page with the effective date so historical readings remain interpretable.
Frequently asked questions
How fast does a new token appear after its pool is created? Typically within one block after the pool-initialisation event finalises. Longer delays are possible during indexer reorgs or upstream outages and are logged as gaps in the affected window. Does discovery imply the token is safe to buy? No. Discovery means the token is on chain 4663 and has at least one live pool. Contract safety, holder concentration, and honeypot risk are separate checks documented under Nock Terminal's safety guides. Why is a token I know about missing from the screener? The most common reasons are no live pool yet, a non-standard ERC-20 implementation, or a pending indexer catch-up. Sending us the contract address helps us verify each of these.
Sources and verification
Last verified: July 14, 2026
Network and contract facts are checked against first-party Robinhood Chain documentation and the chain's canonical Blockscout explorer. Product-specific claims are attributed to the relevant vendor source.
- Robinhood Chain — official documentation — Chain ID, RPC, gas token and canonical contract references.
- Robinhood Chain Blockscout explorer — Public block explorer used to verify every on-chain reading.
- Ethereum ERC-20 standard — Reference for the interface we require during discovery.
- Uniswap v4 overview — Pool-initialisation events used as the primary discovery signal.
Related
Nock Terminal is an independent product and is not affiliated with Robinhood Markets, Inc. Research and product documentation are informational and are not investment advice.
Continue with Nock Terminal
Turn this guide into a Robinhood Chain workflow
Use Nock's screener for current market context or browse the research library for the next verification step.