Use Routescore as decision support, not advice.
Product education, methodology notes, and practical workflows for route scoring, modeled MEV exposure, supported-holding stress tests, hash-recorded journals, and public detector signals.
Every article must teach a workflow, name its coverage limits, and keep scenario outputs modeled, point-in-time, user-controlled, and not investment advice.
Ready tutorials
Test Routescore with one wallet before connecting your own
Use one saved wallet or paste a public EVM address to inspect supported-token coverage without custody or transactions.
The safest first-use story is read-only: start with one wallet, learn what is covered, then decide whether Pro is worth it.
Open dashboardUse Routescore JSON exports before you need a full API platform
Start with read-only public snapshots, account export, journal CSV, and scenario JSON artifacts before API keys exist.
This pulls ODW/API value forward without creating custody, execution, or contractual support guarantees.
Open developer exportsPlanned feature education
What route scoring can and cannot tell you about MEV exposure
A plain-English guide to modeled MEV exposure, route quality, and why no score guarantees execution quality.
Teach users to compare route scenarios without treating Routescore as an execution oracle.
Try route scorerModel a trading pattern without building a spreadsheet
Move notional, frequency, loss, horizon, and threshold assumptions to understand modeled scenario cost.
The what-if simulator is the education bridge from public route scoring to paid stress scenarios.
Open simulatorWhy supported-token coverage starts with ETH, WBTC, stables, and ETH staking risk
Routescore starts with high-volume base assets and major ETH staking/restaking exposures before long-tail tokens.
Coverage honesty builds trust: supported-token pricing is valuable because it is explicit about what it does not cover.
Check wallet coverageHow to write a hash-recorded DeFi decision journal entry
Record assumptions, scenario outputs, and final reasoning without turning Routescore into advice.
The journal is a decision-memory moat: the more often users record reasoning, the harder Routescore is to replace.
Open journalHow to stress-test supported holdings without forecasting the future
Use historical shocks as scenarios for supported priced holdings, not predictions about what will happen next.
Stress scenarios are the cleanest Pro paid feature because they reuse wallet pricing and stay firmly in decision support.
Open stress testHow to compare yield scenarios without treating them as investment advice
Understand modeled, point-in-time yield scenarios and why execution stays outside Routescore.
Power value comes from disciplined comparison, not recommendations or guaranteed outcomes.
Open yield scenariosUse public detector thresholds as monitoring rules
Set threshold rules for public detector snapshots while understanding they are not wallet-specific alerts yet.
Custom thresholds make a public signal personal without overpromising real-time wallet monitoring.
Open accountWeekly public detector notes
A recurring public explanation of what changed in detector snapshots, coverage, and methodology.
The digest should remain free because it compounds trust, distribution, and market context.
Join newsletter