Finalized credit batch and project metadata for the VCS credit class. The only major changes was moving the 'additional certifications' from the project metadata to the credit batch metadata to align with Verra's representation of credit batches as well as removing monitoring and verification reports from the credit batch data to allow for easier automation in the future.
The current batch metadata structure only supports a 1:1 metadata mapping for credits bridged directly from the Verra, but not other bridges such as toucan which supports different data(toucan vintage metadata here). While this might have been more difficult to address at a certain point in time, our new strategy to allow for dynamic minting of batches allows us to circumvent the need for an exact metadata mapping for credit batches by introducing a BatchOriginTx parameter which allows us to determine the credits source bridge. This means that in the future, we will likely have two sets of metadata in the future to support batches coming over from toucan and batches coming directly from verra.
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...
[ ] provided a link to the relevant issue or specification
[ ] reviewed "Files changed" and left comments if necessary
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...
[ ] confirmed all author checklist items have been addressed
Description
Finalized credit batch and project metadata for the VCS credit class. The only major changes was moving the 'additional certifications' from the project metadata to the credit batch metadata to align with Verra's representation of credit batches as well as removing monitoring and verification reports from the credit batch data to allow for easier automation in the future.
The current batch metadata structure only supports a 1:1 metadata mapping for credits bridged directly from the Verra, but not other bridges such as toucan which supports different data(toucan vintage metadata here). While this might have been more difficult to address at a certain point in time, our new strategy to allow for dynamic minting of batches allows us to circumvent the need for an exact metadata mapping for credit batches by introducing a BatchOriginTx parameter which allows us to determine the credits source bridge. This means that in the future, we will likely have two sets of metadata in the future to support batches coming over from toucan and batches coming directly from verra.
For more info on dynamic minting, check out the github dynamic minting strategy conversation and implemented solution.
Author Checklist
All items are required. Please add a note to the item if the item is not applicable and please add links to any relevant follow up issues.
I have...
Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add your handle next to the items reviewed if you only reviewed selected items.
I have...