Data sources
Protocol coverage starts from structured upstream data and is then filtered, ranked, and stored locally so the public site reads from SQLite instead of a large front-end JSON blob.
Editorial Policy
How Radar handles data, automated content, and trust signals
Radar uses a mix of upstream protocol data, SQLite-backed page generation, and recurring editorial updates. The goal is useful discovery content that helps people compare what they are seeing.
Automated publishing
Some recurring posts and micro blocks are generated automatically around Radar updates, but they are constrained to the site’s discovery niche and tied back to actual tracked chains, categories, and protocols.
Human oversight
Automated content is meant to support research workflows, not replace judgment. Titles, navigation, positioning, and larger site decisions should be reviewed and improved over time.
External links
Radar links out to project websites and public social profiles for convenience, but those destinations are external. Wallet connections, signatures, and transactions do not happen on Radar pages.
Corrections and updates
Pages are refreshed as upstream data and local content change. When protocol metadata improves, the corresponding page and sitemap timestamps should improve with it.
Not investment advice
Scores, rankings, and posts are informational. Radar is built to help with discovery and comparison, not to provide guarantees or financial advice.
Support pages
Pages that explain the site
Useful sites do not just ship lists. They explain how those lists are built, what users can expect, and where the boundaries are.