Configuring Multi Policy using UI
It is possible to ‘join’ multiple independent policies, which are hosted/ran by different Guardian instances, into a group in which one policy would be ‘primary’ and the rest ‘dependent’ or ‘secondary’.
In this setup (only) ’primary’ policies are responsible for minting tokens, which thus can be certified to be compliant with other (‘secondary’) policies via links to VPs issued by the ‘secondary’ policies.
The tokens are only minted when the necessary quorum of approvals (by the ‘secondary’ policies) are reached. This enables the creation of tokens for projects which are compliant with multiple policies codifying different methodologies, issued independently by different Standard Registries.
- 1.Synchronization of the policy ‘approvals’ and mints is performed through the Header topic of the ‘primary’ policy.
- 2.Guardian instances check the topic for the synchronization message on schedule.
Step 1: Need to click on the linking icon for the policy, which you wanted to be a primary one as shown below:
Step 2: We get a policy linking pop up to create a link for the primary policy or joining an existing policy:
After the ‘primary’ policy is registered a special ‘link’ becomes accessible which can be used to ‘connect’ additional ‘secondary’ policies.
Step 1: We click again on the linking icon for secondary policy and will get a linking pop up as shown below:
Step 2: In order to make the policy as secondary, we will click on Join button and link with the primary policy.
Step 3: Once, linking is performed successfully, you will get below message:
Synchronization topic contains two types of messages:
3.1 Messages on linking the policies:
3.2 Token mint messages