Skip to main content
WalletWall publishes research alongside a production product, and the two are easy to confuse. This page states the status of every documented surface as of 1 November 2026. It is the canonical maturity map: each feature page shows only its own status cue and links back here, and this is the one place they are all side by side.

How to read a status cue

A status cue such as Available · Read-only · Research interface describes up to three independent things: whether you can use a surface, what it asks of you, and how much weight it can bear. One never implies another. A surface can be available and still be a research interface; a public package can be installable and still be pre-release.

Wallet intelligence

Vault and readiness

Two vault surfaces carry different statuses on purpose: the hosted Stablecoin Vault journey is available and read-only, while the Vault Simulator’s connected dashboard is a testnet prototype. WalletWall has no production or mainnet custody path.

MCP, integrations and disclosure

The server and both plugins are pre-release (installable): their own code labels them pre-release, and neither the engine nor its evidence profile has had an independent security review.

Accounts and payments

As of this page’s date, no user accounts, sign-in, subscriptions or payments are live. Every surface above is used without an account.

What else a boundary can tell you

  • Scheduled or snapshot data carries the instant it is true for and is never labelled live; see Data Serving Architecture.
  • Live provider reads are request-time observations served through a short provider cache that marks stale values as stale.
  • Research prototype means not audited, not production custody and not a protection guarantee; see Public and private repositories for what you can and cannot infer from the published repositories.

Where to go next

What is WalletWall?

The product thesis, audiences and the scan → assess → recommend → report → monitor workflow.

Vault Boundaries & Disclosures

The custody, testnet, audit and post-quantum limits behind the vault rows above.

Data Serving Architecture

How each data class above is served and labelled.

Public and private repositories

What repository visibility does and does not tell you about a surface.