Skip to main content
RETIRED · STANDALONE SURFACE The standalone Stable Seer page, homepage section and navigation entry were retired. /stable-seer and stable.walletwall.org redirect to the Stablecoin Vault. Stablecoin peg and supply evidence remains available where a surviving feature needs it (token detail, the Watchlist and the wallet activity view).See what you can use today for the status of every surface. This page is kept as a historical record of what the surface did and how its data was handled. It describes functionality that is no longer a destination in the product.
Data handling, as documented while the surface was liveStable Seer combines market-provider reads with scheduled snapshots and labels which is which. Its readings are observations, not predictions. See what you can use today for every surface side by side.

What it does

Stable Seer is WalletWall’s dedicated surface for monitoring stablecoin peg risk, liquidity depth, issuer concentration, and cross-chain flow movement. It provides a focused lens on the stability and utility of the fiat-equivalent ecosystem.

What you can learn

  • Whether a stablecoin is holding its peg — price variance from $1.00 across DEX pairs, with a 30-day peg history from scheduled snapshots.
  • How deep its liquidity is — where pools sit across DEX venues and chains.
  • Where large stablecoin transfers are happening — large flows over the last three days and daily volume over 30 complete days.
  • What backs it — fiat-backed, crypto-backed, or algorithmic.

How to read it

Stable Seer prioritizes depth and stability analysis for:
  • Fiat-backed: USDC, USDT, PYUSD, FDUSD
  • Crypto-backed / over-collateralized: DAI, LUSD, crvUSD
  • Algorithmic / hybrid: FRAX, USDE

Risk Console

The Risk Console is a summary band above the results that aggregates peg deviation status, liquidity depth and issuer concentration risk for a selected stablecoin into a single view.
Risk readings are historical or point-in-time observations derived from scheduled snapshots and market provider data. They are not investment advice and do not constitute a prediction of future peg stability.

Data views

  • Peg check: price variance from $1.00 across DEX pairs, read from market providers at request time and reported with low confidence because pool data is partial market data
  • Historical volatility: frequency and depth of de-pegging events over 24h, 7d, and 30d windows
  • DEX liquidity depth: aggregated ±% depth for stable-to-stable and stable-to-volatile pairs
  • Issuer risk: concentration of supply within specific minting/redemption entities
  • Chain distribution: percentage of total supply deployed across Ethereum, Base, Optimism, Arbitrum, and other EVM-compatible chains
  • Inflow/outflow by protocol: stablecoin migration into and out of major DeFi protocols (Aave, Maker, Curve)
  • Whale movements: source-backed tracking of large stablecoin transfers between CEXs and unlabeled wallets

Sparklines and pool map

Peg sparklines show daily average peg deviation over the last 30 days, from a scheduled Dune query. Volume sparklines show daily transfer volume over 30 complete days, from owned BigQuery snapshots. Both windows are fixed, and both are scheduled data, not live readings. The pool map visualizes liquidity pool distribution for a selected stablecoin across DEX venues and chains. Pool data is sourced from DEX Screener. Filters allow narrowing by chain, DEX venue, and stablecoin type (fiat-backed, crypto-backed, algorithmic).

Stablecoin Vault handoff

Stable Seer links to the Stablecoin Vault readiness assessment (vault.walletwall.org / /stablecoin-vault). The link carries no Stable Seer data, and no Stable Seer signal feeds the hosted recommendation today.

Data freshness and provenance

Stable Seer does not have one data source. Each view below has its own source and its own freshness. See Data Serving Architecture for how the owned snapshots are served.
Scheduled data — owned BigQuery snapshots and Dune results alike — reflects the instant it is complete up to, never the present. The UI labels Dune-sourced data as Scheduled/Cached, and BigQuery-served series carry their watermark. When an owned series cannot be served, its route answers an error and the page hides that section. No Dune result stands in for it.

Important boundaries

  • All scheduled data — owned BigQuery snapshots and Dune results — is labeled as scheduled and cached, never live.
  • Stable Seer does not provide holder analytics. Solana holder analytics are not supported; aggregate market-level data (price/volume) for Solana-based stablecoins may be available via market providers only.
  • Stable Seer observes public market and on-chain data. It never initiates or tracks issuer mint/redeem activity directly.
  • No deanonymization: attribution is limited to public and source-backed labels.
  • No yield ranking, no “best rate,” and no projected return appear in any UI, score, or recommendation.
  • Stable Seer is intelligence-only: it does not initiate vault enrollment, does not suggest financial actions, and does not provide advice. The Stablecoin Vault is the readiness destination.
  • Data is for informational purposes only. Not investment advice.

Technical reference

Data flow

This is the /api/stable-seer route specifically: DEX Screener supplies pool and market data, Frankfurter is consulted only when a non-USD fiat peg is involved, and the durable stable-peg-history snapshot is read — never written — for temporal peg context. That snapshot read never calls Dune and spends no live provider quota. Successful market-provider results carry confidence: low because the data is partial market data; a provider failure carries confidence: unavailable. Scheduled BigQuery and Dune context reaches the UI through the separate surfaces listed below.

Routes and sources

Stable Seer is a product surface with more than one seam, and the seams do not share providers.
The /api/stable-seer route itself calls only DEX Screener and, optionally, Frankfurter. It does not call Dune and does not call CoinGecko. BigQuery- and Dune-backed context reaches the Stable Seer UI through the separate surfaces named above.
Stable Seer API endpoints return a normalized structure. The shape below is illustrative; the live scheduled routes label an owned snapshot with provider: "bigquery" and a queryRunAt watermark, and a Dune-backed route with the Dune run time.
  • The holderAnalyticsSupported: false flag is present on every API response as a hard invariant.
  • Filters operate client-side against the current result set.
  • Stable Seer was previously named Market Radar. All identifiers, routes, and API endpoints were renamed as part of Epic #163.

Quantum Intelligence

Quantum exposure and dormancy facts are stablecoin-scoped — the same stablecoin domain Stable Seer monitors for peg and liquidity risk.

Stablecoin Vault

The readiness destination Stable Seer links to. No Stable Seer signal feeds its recommendation today.

Data Serving Architecture

How the large-flow and volume series are served from owned BigQuery snapshots, and what happens when a snapshot is stale.

WalletWall MCP

Evaluate stablecoin evidence you gathered yourself, locally, under WalletWall’s published MCP registry and policies.