• Start recording
• Welcome & antitrust notice
• Introduction of new members
• Agenda review

• Antitrust Policy Notice: Attendees are reminded to adhere to the meeting agenda and not participate in activities prohibited under antitrust and competition laws. Only members of ToIP who have signed the necessary agreements are permitted to participate in this activity beyond an observer role.
• New Members:

Reports

• Specifications all moved to ToIP GitHub Org, not being announced until license issues are resolved in TSWG
• development branch created in KERIA, SigPy and SigTS and set as the default branch (used for PRs moving forward).  main  branch to be stable for releases moving forward
• W3C - PR 1203 merged into VC-DATA-MODEL which mentions ACDC as an example of a potentially compatible VC specification.
  • Opens the door for defining transforms to the W3C VCDM  for ACDC credential ecosystems.  For example VC-vLEI.
• Credential Transfer semantics discussed last week, details added to issue in PTEL spec:
  • https://github.com/trustoverip/tswg-ptel-specification/issues/4

• Selective disclosure
  • Re: Demonstration of Support for NIST-Compliant Selective Disclosure (SD) for Data Integrity Cryptosuites in VCWG
    • Proposal for SD mechanism that is compatible with RDF and JSON-LD.   In the email announcement, there were references to the ACDC SD mechanisms that were not accurate.  Long email chain with descriptive responses from Sam fully explaining the ACDC SD mechanism.
    • Declaration of "NIST-Compliant" indicates that they are not using "advanced crypto", but just basic NIST-compliant cryptography.
    • Similar to the ACDC approach of using just digests and digital signatures and blinded hashes (and maybe Merkle Trees), makes this approach to SD "easily adoptable".
    • Selective Disclosure (SD) for Data Integrity Cryptosuites, SD-JWT, Gordian Envelopes and ACDC are all similar approaches to SD in the "easily adoptable" concepts.
    • Levels of nesting and amount of "leakage" are differentiators across the approaches.
  • ACDC allows for tuning of SD mechanisms to balance between complexity and security/privacy.  As a result, ACDC has created new terminology for describing the tiered mechanisms.
    • Full Disclosure - Disclosing everything
    • Least Disclosure - Only disclose the minimal amount of data needed to advance the transaction.
    • Partial Disclosure - Nested SD of only parts of the data at any levels
    • Selective Disclosure - Some fields disclosed using the other mechanisms described here.
    • Graduated Disclosure - Increasing the amount of data disclosed over the course of a transaction.
  • Most Compact Version - All fields and nested blocks blinded by SAIDs of the block in place of the actual block in the ACDC.  This describes which "format" of the blinded nested blocks represents the signed credential.
  • Avoidance of the "Soup Model".  AnonCreds and similar technologies were built to support doing credential presentations with fields selectively disclosed across multiple credentials.  ACDC allows for careful creation of credentials with minimally sufficient fields at any given level and chain those credentials together using ACDC chaining to avoid needing the Soup Model.
  • Chaining can enable credential formats that don't require SD because the chains contain data that don't need to be disclosed if the credentials are design properly.

• Review decisions/action items
• Planning for the next meeting 

• Discussion ACDC issuance for IIW