CAPPZ Replicator + Transporter
Keep sovereign copies aligned and observe how signed, checksummed frames move through replayed channels and sessions to verified receipts.
Core value 2 of 7: Verified delivery — Encrypted, resumable, checksum-proven transfer (Transporter).
BizTalk receives a message, maps it, runs the process, and routes it through a central box. CAPPZ does the same job as copies that reconcile with each other. The central box is optional.
Replicator keeps every sovereign copy aligned. Transporter is the named view of how signed frames move across a selected channel and session, resume, verify, and reach convergence. Message sync is peer-path. Behind firewalls, copies dial out to a relay node an operator runs; it carries sealed frames it cannot read. Sign-in/admin may still be hosted. This live view uses account-linked records; for a public, same-device sample, try the two-copy demo. Every figure here is replayed from replication records — nothing is sample data.
Network
All the copies and clones of one wallet that replicate with each other.
Channel
A lasting peer-to-peer link between two parties. Open it once and keep it for months.
Session
One flow inside a channel, such as “Q3 payments” or “Contract review”. Start as many as you need; each one stays in step on its own, like chat sessions.
Every copy stays current.
Replicator finds what each copy of a document is missing and reconciles it, so both sides of a business document are always on the same version — with the history of every change kept.
Verified movement, end to end.
Transporter is how Replicator physically moves data: it frames and encrypts the payload, picks the channel, resumes after interruptions, and proves arrival with a checksum receipt. It is part of Replicator, not a second engine.
Operate Replicator and Transporter from CommandBridgeZ — one bridge with Captain, Helm, Comms, Science and Engineering stations over the same wallet context.
LIVE LIFECYCLE ROUTE
Replicator → Transporter
Source copy
head announced
Channel
capability replayed
Transporter
frame · encrypt · resume
Receipt
checksum verified
Destination
heads converge
Transporter is the named view of existing channel, capability, frame, session, failover, checksum, and receipt evidence—not a second engine.
Follow a verified corridor.
LIVE PATTERN · CAPPZ REPLICATOR
The middleware hub just became optional. Parties synchronize directly. Contracts, applications, data, and shared multi-master state bilaterally replicated, peer to peer.
- 1 WHISPER (UDP BEACON · PAIRING CODE)
- 2 PUBLISH HEADERS
- 3 DISCOVER MISSING STATE
- 4 SYNCOFFERED ↔ SYNCREQUESTED
- 5 ENCRYPTED A2A BLOCKS
- 6 HASHES VERIFIED
- 7 HEADS CONVERGED
- 8 HIGH QOS CHECKSUM DELIVERY · HASH-PRINT RECEIPT
REAL-WORLD DEMO
Two wallet copies, two tabs. Create an ISO 20022 payment in one and watch it verify and converge in the other.
EXPLAINER · THE CAPPZ REPLICATOR IN 97 SECONDS · TEMPORARY NARRATION
Whisper to find. Connect to move.
Discovery whispers on the LAN; across firewalls, copies ask. Peers find each other by UDP beacon, a TX bid/ask rendezvous with a relay node, pairing code or wallet breadcrumbs, then move the same checksummed frames over TCP, QUIC, a WebSocket bridge, an outbound relay ladder (WebTransport, WebSocket, HTTPS keep-alive, long-poll) or a USB bundle; nodes pull missing bodies by content hash. No inbound port behind a firewall, no browser required.
- UDP beacon LAN multicast, Ed25519-signed by the node key, rate-limited. Announces heads only — never state; a verified beacon makes the node dial. Routers and corporate networks drop it.
- TX bid/ask The copy sends ReplicaConnectRequested with a signed hello to the peer's node — or to a relay only if the peer is unreachable; the node verifies it, decides, and answers with a ticket and its own member record. Works through reverse proxies.
- Pairing code QR, typed, or spoken (sound-pairing). Short-lived, speakable.
- Member table Each copy's devices record where they accept connections (CopyEndpointRegistered, signed, amended on change); every copy holds the table and dials peers directly from it.
- Transport
- Runs on
- NAT
- Offline
- TCP Bitcoin-style sessions: verified signed hello, inventory, headers-first, pull bodies.
- Standalone node
- Needs a reachable port
- LAN
- QUIC Reliable and encrypted over UDP. Same frames as TCP.
- Standalone node
- NAT-friendly (UDP)
- LAN
- WebSocket bridge The browser rides the node’s TCP/QUIC sockets.
- Browser → local node
- Localhost only
- Yes
- Relay ladder (WebTransport · WebSocket · HTTPS) Fastest first: WebTransport over UDP, WebSocket, a receiver-initiated chunked HTTPS stream, then long-poll — each step down automatic where a network blocks the one above.
- Browser or node → relay node
- Outbound only
- No
- USB bundle Signed file carried by hand. Same manifest-first protocol.
- Anywhere
- n/a
- Air-gap
A read-only XRPL connector watches validated ledger headers and checks anchoring proofs itself — no hosted verifier, and it never submits transactions.
Borrowed from Bitcoin: the peer pattern. Left behind: proof-of-work and global broadcast.
# standalone Replicator edge node (Deno) git clone https://github.com/CAPPZ-ai/cappz-sdk cappz && cd cappz && npm install # CAPPZ_NODE_KEY (PKCS8 base64) / CAPPZ_NODE_PUB (raw hex): Ed25519 key that signs hellos, beacons and TXs CAPPZ_POW=<your POW> CAPPZ_NODE_KEY=<pkcs8> CAPPZ_NODE_PUB=<hex> \ CAPPZ_TLS_CERT=cert.pem CAPPZ_TLS_KEY=key.pem \ deno run --allow-net --allow-read --allow-write --allow-env --unstable-net \ packages/cappz-edge-node/main.ts --tcp 41441 --quic 41443 --ws 41442 --relay 41445
My wallets
How safe each wallet is, and where its copies live. You control the dial.
No wallets yet — unlock your wallet to see yours.
Escrow targets
Pick your drive once. After that the Replicator copies your wallets to it whenever it is available, and tells you when it does.
No escrow target yet.
Escrow history
Every copy made, with its content hash. This log is yours.
Nothing escrowed yet.
Farm load balance
0 node(s) · 0 delivered · all reachable copies converged
No copies have announced a head yet.
Flow traffic routing
Per-flow state on the live ledger: offered → delivered → receipted → converged.
No flows recorded yet.
Flow replay
2 of 2 events match. Step through a flow or export the slice.
{ "copyId": "this-device:models", "walletAddress": "m/44'/144'/0'/cappz/models", "role": "edge", "bpmn": "m/44'/144'/100'/bpmn/substrate/a2a-sync-standup" }
How sync works
A copy that lacks records posts a sync request to its own in-queue. The source copy answers over an encrypted channel derived from both wallet keys; only hashes are recorded, never the data itself. Sign in to see your copies.