Wallet copy A

Change a sample payment in one same-device copy and watch the other catch up. A demonstration, not production settlement.

Change a sample payment in one copy. Watch the other catch up. Open copy B in a second tab, then create a sample payment here. Both tabs exchange checksummed frames on this device; this is not a production payment or settlement.

Documents (0)

None yet.

Frame log

Demo scope: both tabs share one device, so the transport is a same-device channel. Between machines the same frames ride TCP or QUIC via the standalone edge node, WebRTC between browsers, or a USB bundle.

What the Replicator demo shows

The Replicator demo shows two wallet copies exchanging a sample ISO 20022 payment on one device. Open copy B in another tab, create the sample payment in copy A, and watch the second copy receive the missing document. 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; the Replicator product also describes peer paths over TCP or QUIC through a local node, WebRTC between browsers and portable bundles. Account sign-in and hosted functions are separate from the peer message path.