Short answers.

A risk interface for Robinhood Chain. It shows where capital is moving across DEX pools, builds a report for any token address, and scores risk from measurable inputs only. Reading is the whole point; the swap and portfolio pages exist so that what you learned on a report can be acted on without leaving for a venue that shows you none of it.

Because it is new and under-served. Aggregators, yield indexes and safety scanners that exist on Ethereum or Base mostly do not cover chain 4663 yet, so a tool that reads it directly is useful now. Serving one chain also keeps every number traceable to a single RPC and a single set of indexers.

Only to move funds. Markets, Analyze, the sell simulation and the API work with no wallet connected at all, and nothing on those pages asks you to connect. A wallet is needed for exactly two things: signing a swap, and signing a revoke of a token approval. Connecting is always your action, never a page load.

No, and it cannot. Routa never asks for a seed phrase or a private key, never generates one, and has no server-side signer. Every transaction is built by Routa, simulated from your own address, then handed to your wallet, which is where it is signed and sent. If a page claiming to be Routa asks for a seed phrase or a private key, it is not Routa.

No. Scores are informational summaries of observable data. They are not an audit, a recommendation, or a guarantee. Use them to decide what to look at more closely, not as a reason to buy or sell.

Twelve inputs each carry a fixed weight, 130 points in total. Each input awards between zero and its full weight in risk points based on what was measured. The score is points awarded divided by the weight of the inputs that could be measured, scaled to 0 to 100. Low Risk is below 25, Moderate below 50, Elevated below 75, High Risk from 75. The full table is in the docs.

Coverage is the share of input weight that could actually be measured. When a source has no data, for example holder distribution for a brand-new token, that input is marked unknown and left out of the arithmetic instead of being guessed. A score with 70% coverage is built from 70% of the evidence.

The newest pools on the chain, each put through a simulated buy, approval and sell as it appears on the page. Every row gets a verdict: sellable with its round-trip cost, a costly exit, a trap, a reverted sell, or not testable yet. Nothing is stored and nothing is sent.

Robinhood issues tokenized equities of its own on this chain. Routa leaves them out of every market list on purpose: they are listed securities rather than the launches Routa is built to read, and they all share the issuer’s logo. They can still be opened directly by address on the Analyze page.

Cards are scored from market data only, so five inputs are unknown there. The report page adds holder distribution, contract verification, on-chain metadata, the identity check and the sell simulation, which usually moves the score and always raises coverage.

Fewer than 20 points of input weight could be measured, which happens when a token has no indexed pool yet or every upstream call failed. Routa would rather show nothing than a number built on almost no evidence.

Yes. The score only reflects what is observable on-chain and in public indexers at that moment. A deployer can keep liquidity deep and holders spread for weeks and still pull the rug later. Low Risk means nothing measurable looked wrong, not that the asset is safe.

Because the inputs changed. Liquidity, volume, buy and sell counts, price moves and holder counts are live, and the market-age input ticks over thresholds on its own. Cached values are refreshed every 30 to 60 seconds, so two refreshes a minute apart can differ by a few points.

The token uses the name or ticker of a known asset, such as USDG or WETH, but its contract address is not the canonical one. The report shows the real address next to the warning. Impersonators get a score of at least 60 regardless of how healthy their pool looks.

Routa asks the chain to simulate a buy, an approval and a sell of the token in one simulated block, using a stand-in wallet funded by a state override. If the sell reverts, 90% or more of the proceeds vanish as tax, or the round trip hands back less than 25% of the stake, the token is flagged as a honeypot. It also reports buy tax, sell tax and the total round-trip loss. Nothing is signed or broadcast.

The token sells, but the round trip costs 25% or more of the stake. This is separate from high tax because the contract may take nothing at all: a Uniswap V4 pool can set its own fee, and an 80% fee reads as zero tax while still keeping most of your money on the way out. A round trip always pays two legs of pool fee and price impact, so ordinary pools land between 0.02% and about 10%. Past 25% of the stake lost, Routa treats it as a honeypot: you can sell, but the outcome is the same.

Uniswap V2, Uniswap V3, Uniswap V4 (including pools with hooks, and pools quoted in USDG, which are reached by buying USDG on V3 inside the same simulated block) and Pons V2 bonding curves. Tokens whose only market is one of those last two used to come back as not simulated; they are simulated now, and the round trip runs on the token’s deepest pool.

Because no route of any supported kind could be quoted, or every attempt reverted for a reason other than a blocked sell. That happens for tokens with no pool at all, for pools behind a hook the simulator could not quote, and while an upstream is rate limited. The sellability input then falls back to GeckoTerminal’s honeypot flag or stays unknown, and the report says which. Base assets like WETH and USDG are not simulated either, because the round trip would pass through the token twice.

From GeckoTerminal’s token info. The top-ten share includes liquidity pools, vesting and locked supply contracts, so a high number is a prompt to check who the top wallets are, not proof of insiders.

You pick a pair and an amount. Routa quotes every venue it supports, ranks the routes by what you actually receive after estimated gas, and shows the losers too, with the reason each one had no route. Picking a route builds the exact transactions: an approval when one is needed, then the swap. Each one is simulated from your own address immediately before it is sent, and a failing simulation stops the send rather than letting you pay for a revert.

Four checks, all on your side of the wire. Every transaction target and approval spender must be on a hard-coded allow-list of routers, Permit2 and the token itself; a Pons curve is only allowed after it has been confirmed on-chain as created by the registered Pons factory. Every swap must carry a real minimum output derived from your slippage; a quote with a zero or incoherent minimum is refused. Every approval’s calldata must match the approval it claims to be. And the pre-send simulation must pass. Any of these failing blocks the send and says why.

Not by default. Approvals are for the exact amount of the trade. Unlimited is a toggle you have to turn on yourself, and it is off every time the page loads. For Uniswap V4 routes a sell needs two approvals — the token to Permit2, then Permit2 to the Universal Router — and the second one is given a 30-minute expiry.

The buy token’s score and flags are shown next to the amount before you can review anything. A honeypot or impersonator flag, or a token whose risk could not be established at all, disables the button until you tick a box saying you have seen it. The full report is one link away.

No. There is no fee, no referral cut and no order flow arrangement. What the route shows is what the venue pays; the fees listed on a route are the pool’s own, plus a bonding curve’s curve fee and creator tax where those apply.

Balances for any address you paste, or for your connected wallet: token, price, value, 24h move and a market-data risk score, with dust separated out. Below that, every open ERC-20 approval and Permit2 allowance it could find for that address, labelled by spender, with unlimited allowances and unknown spenders called out. It is read-only until you revoke something.

Revoking sends one transaction from your own wallet: approve(spender, 0) to the token, or lockdown to Permit2. Routa re-decodes the calldata and checks the target, the function and the arguments before it offers it, simulates it from your address, and reports success only after a receipt confirms it. It is enabled only when the connected wallet is the address being viewed.

Because discovery reads the address’s own transfer and approval logs from a shared public RPC, which rate limits and times out on busy wallets. Rather than pretend, the page prints how much of the block range each scan actually covered. A first lookup of a busy address can be slow and incomplete, and a second one usually finds more.

Pool lists refresh every 45 seconds, token reports every 30 seconds, and simulations every 60 seconds. Holder and verification data are cached for 5 to 10 minutes. Every report shows its fetch time.

Yes. The JSON endpoints that power the interface are open on this origin and need no key: markets, token, search and simulate for reading, plus quote for routing a swap and portfolio for balances and approvals. Parameters and response shapes are in the API section of the docs.

Routa has no token and will not announce one. Any address claiming to be a Routa token is unrelated to this project. Verify every contract address against an official source before interacting with it.