Skip to main content
These diagrams document WalletWall’s product boundaries and security posture using the terracotta, cream, and stone visual language used across the app. They show how surfaces hand off to one another; the data layer underneath them — live provider reads, WalletWall-owned BigQuery snapshots and scheduled Dune caches — is documented in Data Serving Architecture.

Product Boundary Map

Stable Seer is the stablecoin and token/pool market intelligence surface (previously Market Radar). Holder Wall is holder and wallet analytics where supported. Stable Seer results must not be treated as holder analytics.

Holder Wall Preflight Flow

Holder Wall checks whether a usable wallet graph exists before navigating into Coinstellation. Provider and configuration failures should remain user-safe.

Stable Seer Provider Flow

Stable Seer normalizes DEX Screener token and pool search results into WalletWall metadata. Success carries low confidence because the data is partial market data. Provider failure carries unavailable confidence. The API route is /api/stable-seer.

CORS and API Security Posture

Production APIs stay same-origin by default. Future cross-origin browser read access requires an exact allowlist, never wildcard CORS or broad Vercel preview-domain trust.

Where to go next

Data Serving Architecture

The data layer under these flows: which class of data each surface reads and how responses are labelled.

Data Quality and Observability

The observability metadata, provider roles and confidence states behind the Wallet Graph and Stable Seer.

Privacy & Security (MCP)

The trust boundary of the local MCP server, a separate surface with no network access.

Vault Boundaries & Disclosures

The custody, testnet and quantum-security boundaries of the Vault surfaces.