A browser-made key
The account key is created in the browser. The recovery step is required before the first on-chain write.
01 / 06The product
Everything on Starknet, from one private account.
Hold, send, mail, swap, bridge out, bet, launch a token, and run a House without beginning with a wallet extension or a seed phrase.
02 / 06The front door
One page load01 02 03
No wallet. No email. No seed phrase.
A funded first run
Registration arrives with shielded STRK and a small public gas balance instead of an empty screen.
Three covered transactions
The relayer pays registration and two more transactions while showing the remaining count.
03 / 06The boundary
Privacy described before action
Public in. Private through. Public out.
Public in
A deposit address and amount are visible when value enters the pool.
Inside the pool
The account spends notes and builds proofs in the browser. Pool activity is still observable.
Public out
A withdrawal exposes its destination, amount, and timing. The app says that before confirmation.
The relayer sees network and timing metadata. StarkWare’s auditor receives an encrypted viewing key during registration. These are product facts, not footnotes.
04 / 06The breadth
Status from the deployment record
Seven surfaces. One account.
01WalletLive
02MailDeployed
03ChatRelayed demo
04SwapLive
05EarnLive
06BridgeOutbound only
07MarketsLive
08LaunchLive
09HousesLive
No balances are combined. Unknown values render as —. Bridge remains outbound only.
05 / 06The evidence
Built and checkable
Mainnet is the record.
The submission manifest, deployment evidence, and public documentation point to the chain rather than to a dashboard counter.
06 / 06The next click