The purpose of the Authentic Chained Data Container (ACDC) Task Force is to help draft and incubate a family of IETF-focused specifications that define the standard requirements for the semantics of Authentic Chained Data Containers. The semantics of ACDCs include both source provenance and authorization provenance or delegation.  The hypothesis is that the W3C Verifiable Credential standard may be expanded to serve as an Authentic Data Container (ADC) with authentic provenance chains (APC) as a super semantic. This may be further expanded to support both a source provenance sub-semantic and a delegated authorization sub-semantic. These are all encapsulated into the semantics with the supporting syntax of an ACDC.


The table below lists all deliverables of the ACDC Task Force:

AcronymFull Name of DeliverableDeliverable TypeLink to
Draft Deliverable
Lead AuthorsStatus/Notes
KERIKey Event Receipt InfrastructureSpecificationhttps://trustoverip.github.io/tswg-keri-specification/Samuel SmithActive Draft
ACDCAuthentic Chained Data ContainerSpecification


Active Draft
CESRComposable Event Streaming RepresentationSpecificationhttps://trustoverip.github.io/tswg-cesr-specification/Samuel SmithActive Draft
SAIDSelf-Addressing IdentifiersSpecificationMerged to CESR
CESR ProofCESR Proof SignaturesSpecificationPending mergeActive Draft
PTELPublic Transaction Event LogSpecificationMerged ACDC
IPEXIssuance and Presentation Exchange protocolSpecificationMerged ACDC

OOBIOut-Of-Band-Introduction protocolSpecificationMerged to KERI
VC-ACDCSecuring Verifiable Credentials using Authentic Chained Data Containers.SpecificationUnofficial draftActive Draft


Please add your name to this list if you wish to be a chair:

2022 - Members

Please add your name to this list in any desired role:

Meeting Schedule

The ACDC TF currently holds a meeting weekly on Tuesdays:

  • NA/EU: 10:00-11:00 EST / 14:00-15:00 UTC 

For all authoritative meeting logistics and Zoom links, please see the ToIP Calendar.


See the latest documentation in the GitHub Repo here:  https://github.com/trustoverip/tswg-acdc-specification

Meeting Agendas and Notes

All meeting agendas and notes are recorded on the ACDC Meeting Page.

Intellectual Property Rights (Copyright, Patent, Source Code)

As a Task Force (TF) of the Technology Stack WG (TSWG), the ACDC TF inherits the IPR terms from the TSWG JDF Charter.

  • The ACDC TF is not expected to produce source code.

Mailing List and Communications

This task force uses the following for communications

  • Slack: This TF has its own dedicated Slack channel: #tswg-acdc-tf
  • Github: This TF will use GitHub issues for substantive conversations on topics, not Slack. This way the conversation is source controlled.

Specification Generation

Specifications use the IETF draft format but may use the following:

  • Markdown: Draft portions spec written in Markdown
  • SpecUP: Final version of spec processed with SpecUp

Use Cases

This table lists the starting set of use cases motivating the ACDC work.

GLEIF use case
Supply Chain use caseSupply chain refers to the overall concept behind the flow of any type of goods and services. https://hackmd.io/vYztT346RC-m34aVmFB7vg
Delegation use case (analog to ZCap usage)A car rental company delegates driving privileges for car X to Alice. Alice delegates to the attendant at valet parking.https://hackmd.io/jDSauX_4RWmTzn8rPijxng
Data graph with verificationBoarding a plane for international travelhttps://hackmd.io/QYlbK-mmTSGKHkpyP_-VSg
Pure data provenanceCiting sourceshttps://hackmd.io/QiOf8YjnT261g8MMAh2yJA

  • No labels

1 Comment

  1. Don't see a link for the github or mailing list.  Have these things been set up?