Skip to content
LogoLogo

Open questions

  1. J construction. ClientIVC fold versus independent recursions; this decides N and proving time on FI hardware.
  2. Actor party ids in the manifest. Listed publicly for immediate revocation. Moving the check into K under a party-root window would hide actors from the chain at the cost of window-length revocation lag.
  3. Private calls. A method that needs another program's record in the same fragment (Daml's cross-template exercise). Candidate: a call-stack in K as in Aztec's private kernel, at the cost of kernel complexity.
  4. Arity and gas. 2/2/2/2 with 8 envelopes fits DvP and invoice; a payroll batch does not. Per-program arity classes would break function privacy across classes. Decide after W2 measurements.
  5. Contention. Shared control records (order books, treasuries) are serialized by consumption, as in Canton. Sharded records per party are a pattern, not a protocol feature; document it.
  6. Registrar view. Whether the asset-issuer slot should ship before W4, since it is what makes the Canton DvP example's registrar privacy literal.
  7. Data availability. Calldata cost for eight envelopes per fragment times N; blobs need the equality proof of §6.
  8. Auditability of function privacy. The disclose flow for programs mirrors the one for policies; regulators may want a standing view.