Report mode

Public example

generic new-chain evidence workflow

Live adapter

Not live

no Robinhood Chain live quote feed attached

Action boundary

Read-only

Routescore reviews evidence; execution happens elsewhere

Report conclusion

The opportunity is the decision-evidence gap.

New-chain activity can move faster than the evidence around route quality, liquidity, quote assumptions, and source freshness. Routescore turns that evidence into a reviewable report before users, bots, or agents act in another interface.

Evidence map

Generic review surfaces

Route and venue

Which venue, path, or pool would the user or agent touch?

Route record, venue caveat, observable-vs-opaque source state.

Review field

Liquidity and price impact

At what notional size does the route move into a wider impact band?

Depth snapshot when available, modeled price-impact band, unsupported-state flag when unavailable.

Review field

Quote and slippage

What quote assumptions are visible, and where can the fill drift?

Expected-vs-worst-case band, user slippage setting, quote timestamp.

Review field

Source freshness

Which inputs are fresh, stale, partial, or unsupported?

Per-source freshness labels and caveats before the report is treated as actionable context.

Review field

Token recognition

Is the token recognized, unverified, or unsupported by Routescore?

Token-state label with no safety clearance implied for unverified assets. On Robinhood Chain, a self-removing scam-token class was disclosed as observed in the wild (Relay Protocol, 2026-07-09); recognition does not rule it out, and the dated caveat rides with every recognized or unverified token state.

Review field

Token privilege surface

Do deployer-retained privileges (mint authority, blacklist or whitelist, trading pause, transfer taxes, upgradeable proxy) exist that can change what a holder has after purchase?

Reserved for a future privilege-surface scan, which would report observed privilege surfaces at the contract level as observed or not-evaluated states, never an all-clear — not evaluated today, and no claim about what such a scan would conclusively catch. Until it ships, the honest state is "not evaluated" plus the dated caveat.

Reserved

Agent or bot action

Can an agent inspect the route evidence before it signs elsewhere?

Read-only MCP/tool response: route, caveats, source state, and policy notes.

Available now

Trust contract

What this page knows - and does not know

Source Cached

Coverage

This page covers the Routescore report format for Robinhood Chain-style new-chain activity. It is not a live chain adapter, venue endorsement, or official integration registry.

Freshness

Created 2026-07-06 as a public example using public launch context; token-state rows updated 2026-07-09 with the Relay Protocol disclosure of an observed self-removing scam-token class on Robinhood Chain. It does not fetch live Robinhood Chain quotes, pool reserves, or venue parameters.

Source status

Cached — Served from a recent cached read, not a fresh fetch.

Confidence

Qualitative workflow example only. Live scoring requires supported route, source, and quote inputs.

Methodology version

new-chain-evidence-map v0.3 - generic-workflow

Excluded risks

Live Robinhood Chain quotesVenue-specific parameter verificationOfficial integration registryWallet-specific reconstructionExecution outcomesToken privilege-surface / can-sell evaluation (reserved, not evaluated)

Commercial neutrality. Routescore does not take payment, commissions, fees, or referral rebates from any protocol, router, relay, or venue to influence these results. Rankings reflect modeled route quality only.

Modeled, point-in-time decision support — not execution instructions, a quote, or investment advice.

What to review

Evidence before action elsewhere

-Which pool or route would the user or agent touch?

-What notional size changes the price-impact band?

-Which source is fresh, stale, partial, or unsupported?

-Which dependency can change the outcome outside the swap UI?

-Is the token recognized, unverified, or unsupported by Routescore?

Routescore function

What Routescore makes reviewable

Route recordVenue or pool path, observable inputs, and caveats.

Liquidity bandModeled depth and price-impact band when supported; explicit unsupported state when not.

Slippage bandExpected vs stressed fill band with the assumptions shown.

Token stateRecognized, unverified, or unsupported. Unverified is a caveat, not a clearance.

Source freshnessEvery input marked fresh, stale, partial, or unsupported.

The same checks are available to agents as one call via the Routescore MCP, so a bot can review the evidence before it signs elsewhere.

Run it

Run a route evidence check.

Routescore is a read-only evidence layer, not another execution surface. Run a route check, read the caveats, then act wherever you already trade.

Run a current route check