How it works

Two parts

The browser demo is a standalone page. Wallet setup, balances, routing and payments all run in memory inside your tab. Its network calls are intercepted by the page itself, so nothing it shows is sent to the hosted API as a payment.

The public API is hosted separately. It handles signed handle registration, payment links, report shares, verification, screening and a waitlist. It is not a wallet and never holds your keys.

The demo flow

1. Set up a walletThe onboarding screens create a simulated wallet in memory. Never enter a real recovery phrase.
2. Pick a handleA handle such as @name stands in for a long address. In the hosted API, the server retains which owner a handle belongs to.
3. Send privately (simulated)A send is split into scheduled notes and routed with delays to illustrate the idea of breaking the link between payer and payee.
4. Receive through linksA payment link carries an amount, a destination and a status. Recipient addresses can be one-time, and their usage is tracked.
5. Disclose selectivelyA signed report lets you show a counterparty only the payments you choose, and anyone can verify the signature.

The hosted API

Everything the API keeps is deliberately narrow. It keeps public handle-owner and address mappings, one-time recipient addresses and their usage, payment link amounts, destinations, status and reference, shared signed report payloads, and a hash of each waitlist email.

Wallet private keys and seed phrases are not in the hosted database. The Security page lists the data and its limits in detail.

Not done yet

• No independent audit has been verified.
• The complete wallet engine is retained as local-device source and is not exposed by the hosted app.
• The hosted app is not a live-money client. Do not use it with real funds.

For definitions and answers, read the FAQ. For deeper write-ups, read the Blog.