Skip to main contentSkip to data table
Pharos
PHAROSlive stablecoin signals

About Pharos

Most trackers show price. Pharos shows risk.

We monitor 369 stablecoins with honest classification, live reserve feeds, forward-looking depeg warnings, and the only public blacklist tracker covering 35 coins across 9 chains — because knowing what a stablecoin is worth means knowing what could make it fail.

Reference pages

Reference Pages

Every stablecoin makes two promises at once: that it will redeem at par, and that it can be redeemed at all. Pharos watches both across 369 live tokens and the chains and reserves beneath them so that desks, treasuries, and researchers can read the peg the way navigators read weather.

Edited by TokenBrice · Engineered with Claude & Codex · MIT

Watching the peg.

Why it exists

Why Pharos?

The data needed to evaluate stablecoins is scattered, inconsistent, or buried behind paywalls. Worse, marketing claims rarely match reality: a "decentralized" stablecoin may rely entirely on centralized collateral, an issuer can freeze balances without warning, and a major stablecoin's failure transmits stress to dozens of derivatives that looked safe in isolation.

Pharos tracks 369 live stablecoins, 28 upcoming launches, and 88 dead ones, then scores the live universe with honest governance classification, transitive dependency scoring, and live reserve composition where available. Real-time depeg detection, freeze monitoring across 35 stablecoins, and a 30-minute ecosystem-wide stability index give you the full picture before a crisis makes the headlines.

When a tracked stablecoin effectively dies — issuer abandonment, supply trending to zero, irrecoverable depeg, regulatory shutdown — Pharos freezes it rather than deletes it, and surfaces it in the cemetery with an obituary and an archived detail page.

Pharos is a public good. The dashboard stays free, the code is open source, and sustainability comes from community support plus future paid API access for heavy programmatic usage. See the funding ledger or get started and make the most of it.

For architecture, methodology, and design references, use the documentation archive.

Operating stance

Principles, AI Policy, and Corrections

Independence is a precondition, not a marketing line.

Pharos has no token, takes no issuer money, sells no paid placement, and accepts no editorial trade. Sustainability comes from community support and, eventually, paid API access for heavy programmatic users. The code is MIT-licensed and the inbound funding ledger is published in full at /funding/.

Risk over price.

Most trackers show what a stablecoin is worth right now. Pharos shows what could make it fail: backing, governance, freeze authority, dependency exposure, peg behavior, and exit liquidity. Price is the consequence; risk is the cause.

Dependency is contagion.

Safety grades cap composite scores at the upstream asset the coin depends on. A stablecoin backed by a stablecoin backed by a money-market fund inherits the worst grade in that chain, not the best. The dependency map exists because the 2023 USDC depeg showed that derivative coins move with their collateral, whether they want to or not.

Methodology is versioned and dated.

Every score Pharos publishes carries a methodology version and a changelog link. When a formula changes, the version increments and the change is documented before the new number replaces the old one. The project changes its mind in public so that anyone who cited an earlier reading can verify what changed between then and now.

Open code, open data, published curation.

The dashboard, the worker pipeline, the scoring engines, and the data exports are MIT-licensed and reproducible. What is tracked is a curatorial decision, and the curation is published — additions land with explicit rationale, exclusions are documented when contested, and the inbound funding that supports the work is logged at /funding/ for inspection.

On AI-authored content.

Narrative summaries on coin pages and the daily digest are drafted by a large language model against the same data the dashboard renders, then reviewed by a human editor before publish. The numeric outputs — scores, peg deviations, supply, liquidity, freezes — are computed by the worker pipeline, not by the model. AI ships in the narrative panels only, and every such panel carries a disclosure chip naming the model and the reviewer.

On corrections.

Pharos publishes data that other people will cite, which means it has to be wrong in public when it is wrong. If a number is off, a classification is wrong, or a methodology choice does not survive scrutiny, the correction path is the same as for every Pharos data point: a GitHub issue, the on-page feedback link, or a message via Telegram. Verified corrections are applied and dated. See the funding ledger for the inbound side of the same accountability.

The team

Who Is Building Pharos?

TokenBrice
Creator
Ike
Champion
Claude
AI Brainstormer
Codex
AI Engineer

TokenBrice created Pharos and leads product direction, scoring methodology, and the data pipeline. Ike drives growth and communications. Most of the codebase is written and maintained by Claude and Codex, from the worker pipeline and scoring engine to the frontend and daily digest.

In the wild

Live Walkthrough

TokenBrice walked through Pharos live on Leviathan News — the motivation behind the project, the data pipeline, and how the main risk signals should be read in practice.

Watch the Leviathan News broadcast

Coverage

What Pharos Tracks

The raw monitoring layer — live supply, peg behavior, blacklist activity, liquidity depth, and chain-level flow data pulled from 50+ sources into one operating picture.

369 stablecoins

Coverage across supported chains, classified by governance, backing, and peg currency.

28 upcoming stablecoins

Pre-launch projects tracked from announcement to launch, with milestones, timelines, and featured content.
View upcoming

88 coins in the Cemetery

Algorithmic failures, rug pulls, regulatory shutdowns, and the quiet abandonments worth remembering.
Open cemetery

FreezeWatch

Live view of issuer-intervention events (freeze, unfreeze, pause, block, and wipe) across supported contracts and chains, with chain-specific amount provenance where available.
Open FreezeWatch

Peg Tracker

Composite peg scores, depeg event detection, heatmaps, and four years of depeg history on the dedicated tracker.
Open depeg tracker

Bluechip safety ratings

Independent SMIDGE (Security, Management, Insurance, Decentralization, Governance, Escrow) coverage for rated stablecoins, pulled in as an outside reference signal.
Review source

DEX liquidity

Pool depth, volume, quality-adjusted TVL, durability, and pair diversity scored 0-100.
Open liquidity tracker

Chain Analytics

Per-chain stablecoin supply totals, 24h/7d/30d trends, composition breakdowns, and a Chain Health Score across quality, chain environment, concentration, peg stability, and backing diversity.
Open chain leaderboard

Mint and burn flows

Configured issuance-chain mint and burn monitoring via Alchemy JSON-RPC, including the Bank Run Gauge and flight-to-quality detection.
Open flow tracker

Portfolio Audit

Analyze your stablecoin holdings against Pharos safety, liquidity, and peg data to spot concentration risk.
Open route

Signals

What Pharos Computes

The analysis layer — models, scores, and forecasts you cannot find anywhere else: a VIX for stablecoins, dependency-capped safety grades, and forward-looking depeg pressure.

Telegram alerts cover DEWS state changes, depeg events, and safety grade changes.

Open @PharosWatchBot

Immersive data visualization

Companion Experiences

Sibling surfaces hosted at separate origins. They consume the same Pharos data through the public API but run on their own, so they can experiment with presentation without crowding the dashboard.

Governance lens

Classification

Pharos classifies stablecoins into three governance tiers: CeFi (fully centralized), CeFi-Dependent (decentralized infrastructure but reliant on centralized collateral or peg mechanisms), and DeFi (fully on-chain, no centralized custody dependency). The classification reflects actual infrastructure dependency, not marketing claims.

Source flow

Data Pipeline

All data is fetched server-side by a Cloudflare Worker and cached in D1. The browser never calls external APIs directly.

Source groups

Supply & Price
DefiLlama, CoinGecko, GeckoTerminal, CoinMarketCap, DexScreener, DexPaprika, Alchemy Prices API, Moralis Token Prices, Birdeye, Jupiter Price API, Pyth Network, Binance, Kraken, Bitstamp, Coinbase, RedStone, Curve on-chain, Chainlink NAV reserve telemetry, Superstate NAV/liquidity telemetry, Fluid, Balancer, Curve, Uniswap V3, Uniswap V4, Raydium, Orca, Meteora, PancakeSwap, Aerodrome Slipstream, Velodrome Slipstream, Zephyr Scanner, direct protocol redemption or FX-par quotes, and curated fail-closed on-chain supply-gap repairs
Reserve Transparency
Issuer and protocol reserve APIs, dashboards, proof-of-reserve portals, issuer attestation indexes, and direct on-chain vault/accounting reads (including live reserve composition feeds from providers such as Anzen, Ethena, Falcon, Frankencoin, Hashnote, infiniFi, M0, Mento Reserve / analytics API, OpenEden, Origin, Blast, Nest Credit, Re, Resupply, Reserve Protocol, USDD, USD.AI, USD1 Chainlink bundle oracle, Accountable, Hyperbeat, Tether, Frax, Circle, First Digital Labs, Ripple, SG-FORGE, Paxos, Sky/MakerDAO, Chainlink PoR/NAV oracles, StraitsX, Kinesis, Quantoz, Yamato, Aave GHO, BIMA, SMARDEX, f(x), Asymmetry, JupUSD, USDGO, Yield Optimizer, Yuzu, Solstice, River, Alloy, Zephyr Scanner, and Curve/Yield Basis reserve reads where available)
On-chain Reads & Events
Etherscan v2 (freeze events), TronGrid, Alchemy, dRPC, selected public chain RPCs (including MegaETH public RPC, EVM RPCs for configured mint/burn flows, direct Liquity/B.Protocol branch debt reads, and Frankencoin's ZCHF -> CHFAU StablecoinBridge balance probe, plus Solana mainnet RPC reads for tracked mint-supply validation), and reconciled freeze-ledger bootstrap rows from kyc.rip / stables.rip for major ETH and TRON blacklist coverage
Ratings & Reference
Bluechip, Chainlink Data Feeds, ECB via Frankfurter, Open Exchange Rates (real-time FX cross-validation), fawazahmed0/currency-api (CNH and non-ECB FX), ExchangeRate-API (tertiary full-set FX fallback), gold-api.com, FRED DGS3MO, FRED DFF, Treasury.gov yield curve XML fallback, the ECB Data API for 3M compounded €STR, SIX delayed SARON compound-rate downloads via public guest access, Bank of England IADB IUDZOS2 (GBP SONIA Compounded Index), Bank of Japan Time-Series Data Search STRDCLUCON (JPY call-rate proxy), Banxico SIE SF43936 (MXN CETES 28d, token-gated), BCB SGS series 11 (BRL SELIC), Reserve Bank of Australia F1 money-market CSV (AUD cash-rate target), Bank of Canada Valet V122530 (CAD CORRA proxy), and CBRT EVDS BIST TLREF TP.BISTTLREF.ORAN (TRY overnight reference rate)
Regulatory Registers
ESMA MiCA registers, EBA EMT/ART issuer and significant-token registers, national competent authority registers such as ACPR REGAFI, DNB/AFM, BaFin, MFSA, CBI, and the Bank of Lithuania where relevant, plus U.S. GENIUS Act implementation sources such as OCC bulletins, FDIC rulemaking notices, FinCEN/OFAC AML rulemaking materials, Treasury state-regime comparability materials, OCC charter/decision materials, Federal Register notices, and issuer reserve or disclosure pages
DEX Data
DeFiLlama Yields & Protocols, protocol-native yield APIs and deterministic on-chain yield readers (Hashnote, Ondo, Midas NAV oracles, Morpho, Pendle, Royco Dawn, Yearn Kong, Beefy, Aave V3, Compound V3, BIMA Earn, Curve scrvUSD current-rate, B.Protocol LQTY-only, Zephyr Scanner), Curve Finance API, The Graph, Fluid API + DexReservesResolver, Balancer API, Raydium API, Orca API, Meteora API, PancakeSwap subgraphs, Aerodrome and Velodrome Sugar view contracts, GeckoTerminal, DexScreener; dead or deprecated DEX slugs such as Bunni are blocked from runtime pricing and liquidity inputs rather than treated as live venues
AI Generation
Anthropic Claude (daily digest and Monday weekly recap)

Processing path

  1. Sources

    Market, on-chain, ratings, FX, commodity, and digest inputs are collected on a fixed schedule.

  2. Cloudflare Worker + D1

    Staggered 5-minute, 15-minute, 30-minute, hourly, multi-hour, daily, and monthly lanes normalize the data and cache the results for the public API.

  3. Static dashboard

    Next.js pages on Cloudflare Pages consume the worker outputs and render the stablecoin view without direct third-party calls.

Scoring details

Methodology

Pharos grades every stablecoin across four weighted base dimensions, with peg stability acting as a multiplier on top. The methodology page covers the full grading formula, peg score computation, DEX liquidity scoring, and contagion stress-test design.

Read the full methodology

About Pharos FAQ

Why does Pharos exist?

Pharos is a project by TokenBrice, Ike, Claude, and Codex. It puts the stablecoin data you want to monitor in one place: honest classification, freeze tracking, and a graveyard for the ones that didn't make it.

What does Pharos track?

Pharos tracks 369 active stablecoins across supported chains, classified by governance, backing, and peg currency. It documents 88 dead stablecoins in the cemetery, monitors issuer freeze and blacklist events on-chain for supported centralized stablecoins, provides composite peg scores with depeg detection and heatmaps, integrates independent Bluechip SMIDGE safety ratings, scores DEX liquidity depth 0-100 across decentralized exchanges, computes a 30-minute Pharos Stability Index for ecosystem health, and issues report cards from four weighted base dimensions plus a peg-stability multiplier, including an exit-liquidity input that blends DEX liquidity with protocol or issuer redemption backstops when a direct exit path exists.

How does Pharos classify stablecoins?

Pharos classifies stablecoins into three governance tiers: CeFi (fully centralized), CeFi-Dependent (decentralized infrastructure but reliant on centralized collateral or peg mechanisms), and DeFi (fully on-chain, no centralized custody dependency). This reflects actual infrastructure dependency, not marketing claims.

Where does Pharos get its data?

Pharos aggregates data from DefiLlama, CoinGecko, on-chain RPC nodes, Etherscan, TronGrid, protocol-native APIs, public regulatory registers, and curated sources like Bluechip. Details on all data sources are available on the About page.

Reach out

Get in Touch

Pharos is MIT-licensed open source. If you spot a bad data point, want a stablecoin added, or want to understand how something is computed, open the code or reach out directly.