Closed blockchain-biopharma closed 1 year ago
There are two approaches to this that initially come to mind. One is a labeling system. For example, Verra has a labelling system where VCUs may be labeled with additional standards and certifications on the Verra registry where both the VCS Program and another standard are applied. One interesting label they are currently working on is to show conformance with the requirements of Article 6 of the Paris Agreement, finalized at COP26. In that case, Project Proponents would submit additional documentation showing conformance with Article 6’s requirements, generally prior to VCU issuance.
So perhaps our solution could have a similar functionality, where offset tokens can have additional labels. The labels would having their own requirements and schema (like a sub-policy), with redundancies removed. These labels could be sort of modules of the main policy/methodology. Users could sort of construct customized policy variations, with variations such as VCS-REDD-APD-Article 6, with VCS being the main standard, REDD being the specific methodology, APD being the project activity, and Article 6 being the label.
Another approach could be separate merged policies. For example, there could be the option to select a Verra policy, a Gold Standard policy, or a Verra-Gold merged policy that covers both. If the project proponent wishes to show compliance with both, they would select the Verra-Gold merged policy.
One potential issue I see with combining Verra and Gold standard is that if a project is processed and issued VCUs through Verra as the root authority, the project VVBs and Verra may not have the authority to also verify the project against Gold Standard, unless perhaps the VVB has both Verra and Gold standard credentials.
Under constraint of using 'multi-sig' for the implementation of this functionality only the following design seem to be feasible: in the current guardian model multi-policy compliant tokens are only possible when there is one 'main' Standard Registry (SR) and (multiple) other 'secondary' SRs such that:
The implications of the above on business case are that:
Problem description
Currently in Guardian there is a 1-to-many relationship between Policy and projects. If a project wants to conform to two or more policies such as Verra and Gold Standard REDD+ from separate "Methodologies" to increate the attractiveness (e.g. 'higher quality') of the minted token. There is no way to avoid double counting.
Requirements
Introduce the ability to define projects compatible with multiple 'active' policies in the same or different guardian instances such that when tokens are minted both of their 'trust chains' are verifiable.
The following design is acceptable:
Definition of done
Acceptance criteria
Minted tokens can contain references to multiple 'trust chains' owned/managed by multiple SRs hosted by the same of different instances of Guardian.