DAR Relay: Cross-Organization and Automated DAR Distribution and Deployment
Needs ChampionPR- SIG
- dar-app-management
- Champion
- —
- Author org
- Ask
- source pending
Abstract
A developer who wants a validator provider to run a new Daml release sends the DAR over chat, an operator uploads and vets it per participant, and the developer keeps track of who has finished, because Canton propagates package vetting metadata but never the package itself. DAR Relay is an Apache-2.0 Rust service that each validator provider runs beside its nodes: developers submit releases through the provider's portal or canton-deploy and follow approval and per-host deployment status, while the provider's operators review each submission with its automated checks attached, approve it under their own policies, and let the service upload and vet the package on the participants hosting the affected parties. When a party is hosted by more than one provider, an approved release can be forwarded to the other providers' Relay instances for their own review, and a deployment report names the hosts that still need it. This delivers the review, approval, installation and upgrading that RFP 3 asks for, requires no changes to Canton or Splice, and consumes the funded registry, metadata and analysis work rather than repeating it.
Milestones
No milestones recorded.
- % of approved-to-date
- —
- % if all RFV pass
- —
RFV scenario unavailable — using approved-to-date as denominator (degraded mode).
- Ask (CC)
- amount pending
Comments by org
5 comments · 2 orgs · last activity Sep 22, 2026
| Organisation | Comments |
|---|---|
| Digital Asset | 3 |
| 2 |