Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Chain of Custody Models #253

Merged
merged 4 commits into from
Jan 29, 2025
Merged

Chain of Custody Models #253

merged 4 commits into from
Jan 29, 2025

Conversation

harleytrustprovenance
Copy link
Contributor

@harleytrustprovenance harleytrustprovenance commented Jan 22, 2025

This PR introduces a new document titled "Chain of Custody," which has been renamed from "Mass Balance" to avoid confusion, as "Mass Balance" refers specifically to one of the four chain of custody models.

Work Produced:

  • Identification of the four chain of custody models:
    • Identity Preserved
    • Segregated
    • Mass Balance
    • Book and Claim
  • Documentation of the evidence required for each chain of custody model.
  • Explanation of the role of third-party attestations in supporting these models.
  • Outline of a potential methodology for the "Book and Claim" model.

@nissimsan
Copy link
Contributor

This is excellent, @harleyjackthomas. Can't wait for this to get mode concrete and implementation-focused.

Don't be shy to push ahead with a merge. Something is much better than nothing.

@harleytrustprovenance harleytrustprovenance changed the title Draft: Chain of Custody Models Chain of Custody Models Jan 28, 2025
Copy link
Contributor

@onthebreeze onthebreeze left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi Harley. This is great work. I'm approving this PR for draft release so that we have a published baseline to talk about. Some observations.

  • The idea of a third party attestation of mass balance or other chain of custody model (except book & claim) is on the mark. I agree it's the only practical way to manage confidentiality and achieve some confidence.
  • I think that references to schema in your code snippets are too coarse - probably should be more like criteria and related regulation or standard - similar to the existing assessment model in the DCC.
  • we might need to extend this model to cover a standard for the confidential information exchanged between member and auditor as well as the standard for the more public attestations issued by the auditor.
  • an entity like an industry association doing the chain of custody accounting as a service for their members seems like a great business pattern that is worth a mention - because each member has a trusted relationship with their peak body and every member wants the peak body to keep the other members honest.
  • A good discovery pattern might be to link the chain-of-custody attestations to the identified facility, grouped by product class produced by the facility, and discoverable as an IDR linkset from the facility ID?

@harleytrustprovenance
Copy link
Contributor Author

Thank you for the positive feedback @onthebreeze , is the appropriate workflow here to get this feedback documented as issues for the group to collectively tackle?

@onthebreeze
Copy link
Contributor

Yes, why dont you create a few issues, reference them here, then we'll merge this PR ;)

@peirens-bart
Copy link

Hi Harley. I do have some question:

  • What happens to the sold credits if the certifier is no longer there, can other certifiers take over credits?
  • How then do we get proof of retired credit if the selling certifier is no longer there?
  • Can credits be purchased from a certifier that falls under different legislation?

@harleytrustprovenance
Copy link
Contributor Author

@peirens-bart I don't have a concrete answer to those questions, I believe this is an issue that isn't concretely defined or solved yet. @onthebreeze is this getting into durable storage, when I believe it mentioned briefly in the DAC docs?

@onthebreeze
Copy link
Contributor

Merging this PR to re-baseline this excellent discussion - recognising that Harley has created five issues to reflect team feedback to date.

@onthebreeze onthebreeze merged commit 6415a4a into main Jan 29, 2025
1 check passed
@onthebreeze onthebreeze deleted the chain-of-custody branch January 29, 2025 21:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants