A custody integration layer for institutions signing Canton transactions with keys they already control. Built so the customer’s custodian holds the key and Havona never does.
Counterparties face the ledger directly with their own keys. Havona operates the validator, not the vault.
Custody actions are proposed, approved and executed as separate steps with distinct authority.
With signing disabled the gateway degrades honestly — it cannot fabricate a signature.
There is no retail wallet interface and no browser key handling. Signing happens server-side through the customer’s custodian.
DFNS is the implemented custody gateway, with additional custodians to follow behind the same interface.
A signing request goes to the custodian’s policy engine and returns by callback, matching how institutional approval actually works.
Propose, approve and execute are distinct choices, so no single operator moves a record alone.
A disabled or unreachable custodian produces a refusal that names itself, never a silent success.
The integration targets the Canton Wallet Gateway and CIP-0103 rather than a single vendor’s SDK.
External-party signing has been driven on Canton DevNet with each party’s key held in independent custody, and a real defect was found and fixed that way — a signature was being spent before the party lookup that made it necessary.
We walk a real contract of yours through the module rather than a demo dataset.