Skip to content

UMBR is live on testnet. Private payments with test funds on Robinhood Chain and Tempo.

Open the app

Start here

Product status

What is built, what is switched off and what comes next, with no rounding up.

Stage
Testnet
Mainnet
Not configured
SDK and MCP
Preview
Sealed trade
Switched off

Where things live#

SurfaceWhereWhat it is for
Websiteumbr.tradeWhat UMBR is, the whitepaper, legal pages
Docs/docsConcepts, guides, the SDK and agent setup
App/appVault, payroll, proofs and settings, in the browser
SDK@umbr/sdkThe same features from TypeScript, for apps, servers and agents
MCP serverumbr-mcpTools an AI agent can call, with spending limits
Verifier/verifyAnyone can check a proof someone gave them

All of them talk to the same shielded pool contracts on the same chains. Proofs are always made on the user's own device or server, never by an UMBR backend.

Status by feature#

Live means usable today, on testnet where it touches funds. Preview means designed and documented but not released. Off means built or possible, and deliberately not enabled.

FeatureStatusNotes
Shield and unshieldTestnetOn each testnet whose pool is configured.
Private send to an UMBR addressTestnetOptional memo, encrypted for the receiver.
Claim linksTestnetCreate, claim and revoke.
Payroll runsTestnetPasted list or CSV; one private payment per line.
Scheduled payrollPreviewIn the SDK preview; the app runs payroll on demand.
Proofs (four kinds)TestnetAudience and 1, 7 or 30 day expiry.
Proof checking at /verifyLiveNo account or wallet needed.
Gas relayerTestnetOptional; you can always submit from your own wallet.
Key backup and restoreLiveFrom Settings in the app.
Demo modeLive?demo=1; nothing is signed or sent.
Sealed tradeSwitched offBuilt, not enabled. See Sealed trade.
@umbr/sdkPreviewDocumented, not on npm yet; API may change.
umbr-mcp serverPreviewRuns locally over stdio; not on npm yet.
Agent funding with AssayDemoAgents page plays it in demo; waits on UMBR's pool and Assay's escrow address.
Hosted MCP endpointPlannedNot running.
Robinhood Chain and Tempo mainnetsNot configuredHidden until the production gate is passed.

Testnet software

The circuits and contracts have not had an independent security review. Do not treat any of this as ready for real funds.

What comes next#

Roughly in this order, and each only when it is ready:

  1. Publish the SDK and the MCP server as previews on npm, with versioned changelogs.
  2. A hosted MCP endpoint, so agents can connect by URL instead of running the server locally.
  3. Scheduled payroll in the app.
  4. The steps on the production gate: a multi-party setup ceremony, an independent review of circuits and contracts, and operational readiness.
  5. A mainnet, one chain at a time, only after its gate is passed.
  6. Sealed trade, once the conditions in Sealed trade are met.

We do not attach dates to these. A date that slips is worse than none.

Rules we keep#

  • No rounding up. A feature is marked live only when a user can do it end to end. Anything else is preview, planned or off.
  • Testnet means testnet. We do not describe testnet behaviour as if real money were at stake, and we do not point real money at a network that has not passed the gate.
  • Keys stay with users. Proofs are built locally. No UMBR server can spend, see or recover your private balance.
  • No token. UMBR has none and the product does not depend on one.
  • Limits are written down. What UMBR cannot hide is listed in the privacy model and the threat model.
  • Mainnet is opt-in by configuration. A mainnet appears in the app only when its pool is set up, never by default.