Wallet
The owner's wallet. Balance, send, receive, connected applications, and a recovery alarm that refuses a request it did not expect.
Scan with your phone's camera, or type
wallet.9500.cash
BCH Blaze 2026 · running on chipnet
No seed phrase to write down. Someone you trust, your bank or a person you know, can move the wallet to a new phone. They can only do it in the open, on chain, and after a waiting period in which the old phone can say no.
Coins, tokens and positions in applications come along: a savings jar and a ParyonUSD loan survive the move.
Everything here uses chipnet, Bitcoin Cash's test network. Its coins have no value.
Each link opens in a new tab, so this page stays open as your guide. Ctrl-click (⌘-click on a Mac) or a middle click opens it behind this one.
The owner's wallet. Balance, send, receive, connected applications, and a recovery alarm that refuses a request it did not expect.
Scan with your phone's camera, or type
wallet.9500.cash
The page of a bank, or of a friend or family member. It sets up wallets from its own coins, keeps each wallet's recovery kit, and moves a wallet to a new phone when the owner asks.
Open recovererSavings locked until a date. The jar's key is a token in your wallet; whoever holds it can empty the jar after the date. The same contract works with any wallet.
Open Savings JarBorrow PUSD against BCH with Paryon's public contracts, unchanged, on their test deployment. The loan's key is a token in your wallet.
An independent front end made for this demonstration. It is not Paryon's site and is not affiliated with or endorsed by Paryon.
Open loan pageThe wallet is made for a phone; the other pages are made for a desktop. The pages talk to each other through QR codes and an encrypted relay, so they work across devices.
The wallet. It scans the codes the desktop pages show.
The recoverer, the Savings Jar and the loan page, side by side in tabs.
For trying a recovery: the wallet in another browser on the desktop, or in a private window. Instead of scanning, it can paste the code as text.
Each browser, and each private window, keeps a wallet of its own. Closing a private window erases the wallet in it, which is a quick way to "lose a phone": your recoverer can bring that wallet back.
About half an hour from start to finish, most of it the waiting period. Start the recovery (step 4) early and try the applications while it runs.
Open the recoverer on your desktop and choose I'm helping someone I know
, or I'm a bank
to set up wallets without approving each one. Send test coins from a chipnet faucet, such as tbch.googol.cash, to the address under Your balance
.
Every wallet starts with a small balance from the recoverer. Raise it under Settings
if you want to try the applications without sending more coins later.
On the recoverer, open Set up
to show a code. On your phone, open the wallet, tap Someone I trust is setting it up
and scan the code. Approve on the recoverer. The wallet is ready the moment the network has the transaction that creates it; there is no wait for a block.
Open the Savings Jar and scan its code from the wallet's Apps
tab. Open a jar that unlocks a few minutes from now. The wallet shows what the transaction does before you approve it, and the jar's key arrives in the wallet as a token.
The loan page pairs the same way. A loan of 100 PUSD needs about 0.6 test BCH of collateral, so send more test coins to the wallet's Receive
address first.
Close the wallet on your phone. Then open the wallet in a private window, or another browser, on the desktop: this is the new phone. Tap I lost my phone
.
On the recoverer, open the wallet under People
and press name lost their phone
. Paste the code's text into the new wallet (or scan it). The recoverer then asks the network to move the wallet to the new key, and the waiting period starts. The recoverer shows how long is left; the new wallet waits.
Close the old wallet first. While it is open, it refuses any request by itself. That is the protection working, and it is step 5.
Leave the old wallet open and make a request: the wallet refuses it on chain, at once, and the recoverer's page says that the owner's phone refused the request. Under Recovery
you can turn off Refuse requests without asking
to decide yourself.
When the waiting period is over, press Complete the move
on the recoverer. The new wallet takes the hand-over and moves every coin and token to addresses of its own: your balance, the jar's key, the loan's key. Empty the jar or close the loan from the new wallet.
Open the old wallet again: it says that the wallet now belongs to another key.
The waiting period is the owner's protection: the recoverer can ask to move a wallet without proving anything, and the old phone has this long to say no. On chipnet the recoverer offers about 9 minutes, the shortest the network can measure. In practice a move can complete about 11 minutes after the request is sent.
The network measures the wait itself, in steps of 512 seconds. One step, about 9 minutes, is the shortest wait that exists. Nobody can shorten a wallet's waiting period, not even the recoverer.
The wait is measured by the chain, which no one can bend, not by a clock someone claims. A request that is not in a block has no age yet. This is one of the very few waits for a block in the wallet; everything else works without one.
Nodes compare against the middle time of the last eleven blocks. It moves only when a block comes, and trails the real time by a few minutes on chipnet. The same reason makes a jar open a few minutes after its date.
Nine minutes is for trying it out. The recoverer also offers about an hour, a day, or a week, long enough for a phone that is sometimes off to notice a request. On mainnet, blocks come every ten minutes and every wait is longer.