CCPEDIAby Unity Nodes
Documentation/DamlView on Daml ↗

Registrar Onboarding

After the Provider Configuration has been created, parties can request to onboard as registrars. A registrar is responsible for creating instruments and managing asset lifecycle workflows such as minting, burning, and transfer controls.

​
Workflow

  1. A party requests a Registrar Service from the Provider.
  2. The Registry App checks whether the party satisfies the Provider Configuration requirements.
  3. If credentials are required, the party must hold the required credential contract.
  4. The Provider reviews the request.
  5. The Provider accepts or rejects the request.
  6. If accepted, a Registrar Service is created.
  7. The Provider and Registrar both become signatories to the Registrar Service contract.

​
Credential Issuance

If a credential is required for onboarding, it can be issued through the Registry App. A Provider can issue a credential offer to the relevant party. The credential defines the claim required by the Provider Configuration.
In simple onboarding setups, the credential issuer may also hold the credential on behalf of the party the claim is about. This avoids requiring the target party to separately interact with the credential app.

​
Cancellation, Rejection, and Termination

A Registrar Service request may be cancelled by the requesting party before acceptance. The Provider may reject a request during review. If rejected, no Registrar Service is created. A Registrar Service can also be terminated later by either the Provider or the Registrar. Termination archives the Registrar Service contract but does not remove existing credential contracts.