ZKsync co-sponsors SODA's 2026 "Tokenization at Investment Banks" Report
ZKsync co-sponsored SODA's 2026 "Tokenization at Investment Banks" report, surveying 16 of the world's largest sell-side institutions on wholesale tokenization.
ZKsync Blog > Private atomic DvP on Prividiu...
Published Jun 23, 2026
Private atomic DvP on Prividium: How it works
Delivery and payment coordinated together across two independently governed Prividium zones, with Ethereum as the shared record both institutions verify against and the trade kept private.
Cross-institution settlement has always carried a gap between the two legs of a trade. One side releases its asset before the other arrives, and the exposure inside that window is principal risk. Tokenization alone does not close that gap. Binding both legs into a single event does: the trade either completes in full or does not happen at all.
Private atomic DvP interop on Prividium delivers that in one instance. That one instance consists of seven steps. Let’s break that down.
1. Agree and record.
The two institutions agree the terms of the exchange directly and record them within their zones. Nothing is written to Ethereum at this stage, and the commercial terms stay inside each zone.
2. Anchor to Ethereum.
Only a cryptographic hash of the agreement is anchored to Ethereum. The assets, amounts, and counterparties never leave the zones, so the public record holds a commitment to the trade rather than the trade itself.
3. Lock assets.
Each zone locks the asset it is giving up. Before locking, each zone reads the anchored record on Ethereum to confirm it is committing against the correct trade.
4. Link and confirm the locks.
Both locks are linked to the agreement, and their hashes match the record on Ethereum, which confirms the trade. The two zones now hold a pair of matching, verified locks, ready to settle. That matched, verified state is the finality signal.
5. Mutual verification.
Each zone confirms that the other has locked by reading Ethereum's record, rather than by trusting the counterparty or a central coordinator. Neither institution depends on the other's word for the trade to proceed.
6. Execute and finalize.
With both locks verified, each zone executes its own leg. The assets change hands, both legs reach the settled state, and the proof of finality of the transaction is recorded on Ethereum.
7. Expiration, assets unlocked.
Every flow carries a deadline. If either side fails to lock in time, or verification does not complete, the flow expires. Each zone reads the expired state from Ethereum and releases its lock, and each asset returns to where it started. Nothing moves unless both sides commit.
Atomic settlement as a single event.
Delivery and payment coordinated as a single event across institutional boundaries. Principal risk inside the settlement window is removed by design, because partial completion is never a reachable state. Neither institution exposes its positions, and neither has to trust the other for the trade to clear.
Share the article
More from ZKsyncView all
Prividium Now Extends to Hyperledger Besu
Matter Labs brings Prividium to Hyperledger Besu: institutions gain ZK-proven privacy and Ethereum interoperability without replacing existing infrastructure.
Build Sovereign Infrastructure. Then Ask If It Can Talk to Anyone.
When Washington forced Anthropic to cut off its top models worldwide, banks relearned an old lesson, and why sovereignty and interoperability stop being a trade-off.