Wallet copies in conversation

Create wallet copies, send text, files, voice notes or a sample payment in one and watch the others catch up, on this device or through a relay node. A demonstration, not production settlement.

Core value 1 of 7: Synchronized copies โ€” Every side holds the same version (Replicator).

Press Create Copy for each party โ€” every copy opens in its own small window and can create more copies. Create a payment, upload a file, record a voice note, or type text in one โ€” watch the other catch up. Download a wallet, then open it again as a live peer. Windows exchange checksummed frames on this device; between machines the same frames ride TCP, QUIC, a relay node (WebTransport, WebSocket or HTTPS) or a USB bundle. This is not a production payment or settlement.

Replication stream (both copies)

Create two or more copies to watch the multiparty exchange here.

What the Replicator demo shows

The Replicator demo shows wallet copies exchanging a sample ISO 20022 payment, text, files and voice notes. Press Create Copy for each party (each opens in its own small window), create the sample payment in one copy, and watch the others receive the missing document. With a relay node URL, the copies reach each other over an outbound HTTPS keep-alive stream instead of the same-device channel. This demonstrates reconciliation between copies, not a live bank payment, partner integration or settlement.

Each document carries a content hash. The copies exchange checksummed frames, compare their document IDs and heads, request missing content, verify its hash and acknowledge receipt. When both copies contain the same set, their heads converge. The demonstration uses a same-device browser channel; between machines, copies connect over TCP or QUIC through an edge node, through a relay node (WebTransport, WebSocket or HTTPS) from behind firewalls, or by portable bundle. Account sign-in and hosted functions are separate from the peer message path.