Capability 2 of 4
Reliable Distribution
The record reaches every authorised destination, including the disconnected ones, and stays synchronised.
Replicate
Updates reach every authorised node.
- New entries are replicated to authorised nodes as they are written
- Changes cascade through intermediate nodes and backup paths keep them moving
- One node can replicate to several other nodes in parallel
- Each node appends the update and can verify its authenticity
Delivery does not depend on a single route. If a link is gone, another node keeps the update moving.Reliable Distribution works on the network you have.
Synchronise
Connected or not, every node ends up in step.
- New entries flow to connected nodes automatically
- Synchronisation can be one-way or two-way
- Push or pull, you control which node starts the connection
- Disconnected nodes can keep working on their own
- On reconnection, they catch up and reconcile automatically
When cut off, each node keeps working with no connectivity.On reconnect, they reconcile to one state.
Aggregate
Many sources, one verifiable picture.
- Combine records from many sources into one big picture
- Every original authenticity mark stays intact
- You can prove every source update is present
- Individual records can still be separated back out
- Snapshot or replay any moment. After-action review, built in
Many sources become one picture.You can prove every update is present.
Opportunistic
Designed for the worst day, not the demo.
- Denied, degraded, intermittent, and limited (DDIL) is the working assumption
- It sends when a window opens, and waits when it does not
- Multi-hop across nodes and nations
- The same record can reach a coalition partner
- No central server to lose
What this gives you
Reliable Distribution
- Works on the network you have
- Offline-first
- Reconnects automatically
- Completeness you can prove
- Coalition-ready
- Verifiable on receipt
- No single route
- No central server
Frequently asked questions
Reliable Distribution questions, answered directly.
Do we need shared servers to exchange data with partners?
No. Every nation or ally stays in charge of its own servers, infrastructure and nodes. They remain sovereign. NxChain is a protocol for reliably distributing updates. It is not a hosted service and not a stack you have to join. Each party runs its own nodes and decides what they distribute.
What happens to updates while nodes cannot communicate?
They stay local, and each node keeps writing on its own while waiting for the network. When the nodes can communicate again, they exchange what the other is missing and reach consistency. Divergence while disconnected is expected to keep nodes working, while reconciliation is automatic when the link returns.
Who controls the direction of connections or updates?
You do. Synchronisation can be one-way (read-only copy) or two-way (read-write copy). A node can push updates out or pull them in, depending on your needs. You choose which node starts the connection and which way updates travel.
Can a coalition share one picture where every nation contributes?
Yes. NxChain can synchronise across nations. Updates from several nations can be aggregated into a single chain and distributed to every participant. Each nation still runs its own nodes. The combined record can be proven complete, to make sure no information is lost.
If a copy reaches a partner, do they see everything?
Not unless you decide they should. Distribution gets the record where it is needed. What each recipient is authorised to see is a separate decision. Selective Redaction is the next step: need-to-know views, with the record still verifying as authentic.