Pharos — Stablecoin Analytics Dashboard
Pharos is an open-source stablecoin intelligence dashboard covering active, pre-launch, frozen, retired, and methodology-only shadow assets. The current inventory is owned by the stablecoin registries and generated datasets rather than duplicated in prose. It is a pure information site: no wallet connectivity, no trading, no custody, and no user accounts.
Pharos is research infrastructure, not financial advice. Data can be delayed, incomplete, or degraded when upstream providers fail; public surfaces include freshness and status signals so users can judge whether a snapshot is current enough for their use case.
What Pharos Tracks
- Peg health: 15-minute peg monitoring, Peg Score, depeg detection, direction tracking, and historical depeg timelines.
- Issuer controls: FreezeWatch covers freeze/blacklist, release, and seize or wipe events for supported issuer-controlled assets across major chains.
- Liquidity quality: DEX Liquidity Score combines pool TVL, volume, durability, pool quality, and pair diversity.
- DEX price corroboration: on-chain and aggregator DEX inputs — Curve, Uniswap, and Raydium among others — help suppress false depeg alerts.
- Market structure: USD, non-USD fiat, commodity, and CPI-linked stablecoin cohorts with chain and peg distribution views.
- Risk context: safety report cards, Bluechip ratings, redemption backstops, dependency mapping, mint/burn flows, live reserves, and yield intelligence where coverage exists.
- Lifecycle coverage: upcoming stablecoins, frozen archives, and the Stablecoin Cemetery for retired or failed assets.
- Public integration: authenticated public API keys, OpenAPI/Postman artifacts, static dataset mirrors, and RSS feed routes.
Data And Methodology
Pharos combines market, oracle, exchange, on-chain, DEX, reserve, issuer, and editorial sources behind a Cloudflare Worker. The frontend never calls third-party providers directly.
The live source roster is rendered at pharos.watch/about from DATA_SOURCE_GROUPS in src/lib/about-content.ts rather than duplicated here. As anchor examples only, it spans market and aggregator data (DefiLlama, CoinGecko), exchange and oracle feeds (Kraken, Chainlink), on-chain, RPC, and DEX reads, FX and benchmark rate feeds, and protocol-specific reserve or redemption endpoints.
Reliability guardrails include:
- structural validation before cache publication
- compare-and-swap cache writes for concurrent sync safety
- source-specific circuit breakers and retry policy
- DEX price cross-validation before severe depeg publication
- BigInt-safe issuer-control amount handling
- cross-currency FX normalization for non-USD totals
- freshness metadata and status surfaces for public consumers
Start with:
Repository Map
src/ Next.js 16 static frontend, route pages, components, hooks
functions/ Cloudflare Pages Functions for same-origin site/ops proxying
shared/ Runtime-neutral data, types, endpoint registry, scoring helpers
worker/ Cloudflare Worker API, cron jobs, D1 persistence, admin routes
docs/ Verified product, architecture, methodology, and runbook docs
.github/ CI, security scanning, dependency policy, issue templates
Detailed architecture lives in docs/architecture.md; route ownership and the agent workflow live in docs/process/agent-start-here.md.
Local Development
Use Node 24 LTS. The repo pins the current release-parity version in .nvmrc.
nvm use
npm ci
npm run dev
npm run dev starts Next.js plus the local API proxy. The frontend shell runs without credentials, but authenticated live site-data requests need SITE_API_SHARED_SECRET in the environment or root .env.local; without it the proxy exits and Next.js uses an unauthenticated public-API rewrite. Full Worker work also needs Cloudflare bindings and provider credentials:
cd worker
npx wrangler dev
For local tunnel or cross-origin next dev testing, set NEXT_ALLOWED_DEV_ORIGINS=host1,host2 in .env.local; next.config.ts appends those hosts to the built-in dev allowlist.
Local Next.js and scripts that explicitly load credentials use the ignored root .env.local; .env.example is generated from the env contract and documents variable names plus non-secret defaults, never secret values. Check only whether a required name is present, and never print or copy its value. Worker runtime secrets remain in Cloudflare/Wrangler-managed bindings rather than local environment files.
For focused authoring checks, use Testing: Smallest adequate check per area.
Use npm install instead of npm ci only when intentionally changing dependencies.
Contributing
Good public contribution lanes are data corrections, source coverage improvements, docs/API examples, bug reports, accessibility fixes, and small UI quality improvements that preserve the existing Pharos design language.
Read CONTRIBUTING.md before opening a pull request; ROADMAP.md records the current directional priorities. Data corrections should include source links and timestamps. Feature ideas usually belong in Discussions before implementation.
Security
Please do not report vulnerabilities in public issues. Use the private vulnerability reporting instructions in SECURITY.md.
License
Pharos code, data and data exports are MIT-licensed. Editorial content, including profile prose, methodology and case studies, is licensed under CC BY 4.0, including when included in a Markdown export. Third-party material retains its original terms.
