Your browser wallet
Balance
…
Reading this wallet's coins…
Amount
On another device, scan with SpiffyVault on testnet. It pays this page live, the way it pays another phone, and the payment shows here as it happens. If this page is closed, SpiffyVault can pay by PeerPay instead.
On this device, tap Open in SpiffyVault. It pays by PeerPay, and the coins show here when you come back to this page.
Any BRC-100 wallet: send by PeerPay to this identity key
Connecting to the Ricochet relay…
Send testnet coins to
In SpiffyVault on testnet: Pay, then A BSV address, and paste it. 10,000 sats is plenty.
Activity
This browser keeps no storage for this page, so the wallet is gone when you leave. Don't send it more than you need.
Wallet key, backup and housekeeping
This wallet lives in this browser's storage and nowhere else. A backup holds everything: the key, the coins paid by PeerPay and the activity. The key alone spends only the address coins.
Choose what to pay
Pay
How this page pays
The page starts a libp2p node, reaches the SpiffyVault Ricochet server over secure WebSockets, and calls pay(). The SDK checks the link's signature and the shop's payee file, then tries the payee's phone live through the server's relay, and falls back to the payee's mailbox. The page's wallet only builds the transaction. The payee checks it and puts it on the network.
const { node, privateKey } = await createPaymentNode()
const ricochet = new RicochetClient(node, { servers: [{
peerId: SPIFFYVAULT_RICOCHET.peerId, addrs: [SPIFFYVAULT_RICOCHET.wss] }] })
const result = await pay({ link }, {
funder, // builds a signed transaction for the payee's outputs
network: 'testnet',
libp2p: node, relays: [SPIFFYVAULT_RICOCHET.wss], // live
ricochet, identityKey: privateKey, // mailbox, sealed from the node's key
onProgress: p => show(p.path, p.step)
})
Developer guide: spiffyvault.net/developers.