Technical overview
Private by contract.
Atomic by transaction.
Converge models each provider relationship as a bilateral Daml contract, then settles accepted commitments through one package-level transaction.
Commercial terms stay bilateral.
A CommitmentRequest is signed by the buyer and observed by one provider. When accepted, it becomes an AcceptedCommitment signed by that provider and observed by the buyer. No other provider is an observer.
signatory buyer observer provider choice Accept controller provider
Consent becomes executable.
Buyer proposes private terms.
Provider delegates activation.
Buyer activates the package.
The valid states are zero or three.
Settlement.Settle exercises every accepted commitment within one Daml transaction. If any referenced leg cannot activate, the transaction fails and no reservation is created.
What is verified today.
- Current Daml source compiled on the Linux VPS with SDK 3.4.8
- Atomic success, rejection, and provider privacy tests pass
- 13 Node tests pass
- A temporary Canton sandbox JSON API settlement created three active reservations
Three reservations, one settlement update.
On September 30, a temporary loopback Canton sandbox returned three active reservation contract IDs from settlement update 122066aa225fe1eecae31902d5799ae60ecdcbbaca2f3c533f36e2693a4264703ce9. A separate provider rejection returned no accepted commitment, and no settlement was submitted for that package.
Inspect the JSON API receipt. The sandbox was stopped after verification. The public Converge app remains in reference mode; a persistent Canton participant and public buyer/provider transaction are still pending.