resources
227 rows where evidence = "official" sorted by date descending
This data as json, CSV (advanced)
Suggested facets: last_checked, authors, series, since, has_abstract, has_summary, kind, sector, country, last_checked (date), date (date)
type 8
status 5
level 3
- practitioner 211
- intro 13
- implementer 3
access 2
evidence 1
- a statute, a regulator's document, or a standards body's own page · 227 ✖
| id | type | name | url | maintainer | status | last_checked | date ▲ | year | level | evidence | access | abstract | authors | series | chair | minutes | recording | media | decisions | version | language | license | release | pushed | depends | since | via | summary | note | has_abstract | has_summary | kind | sector | country | products |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| sedi-summit-2026 | Events event | SEDI Summit 2026 (Park City, 17 to 19 November 2026) | https://www.sedisummit.com/ | Utah Office of Data Privacy (sedisummit@utah.gov) | changed within the last six months, or a live service active | 2026-10-16 | 2026-11-17 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The site of the third State-Endorsed Digital Identity Summit, Park City, 17 to 19 November 2026: the six strands of work (state legislation, policy into implementation, the policy gaps, common approaches, learning from each other, moving the work forward), the speakers and the partners. For anyone following the multi-state SEDI effort. | 1 | 0 | |||||||||||||||||||||
| kswg-2026-10-13 | Meetings (one per entry) meeting | KSWG monthly meeting, 2026-10-13 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1240334337 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-16 | 2026-10-13 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered a KERI track at the SEDI Summit, the Mini KERI Conference scheduled for the Monday before the upcoming Internet Identity Workshop (IIW), and an anonymous donation to the KERI Foundation. Reports covered new issues and missing use cases for transferable and non-transferable autonomic identifiers (AIDs) in the did:webs specification, new pull requests on the Dossier work, and a long-open post-quantum pull request on CESR, alongside a pull request reverting the post-quantum codes in the KERI specification that awaits approval. Discussion reviewed a Self-Addressing Identifier (SAID) presentation for the upcoming PIDfest; open action items include moving the 1.1 branches of all three specifications to main and approving the did:webs specification draft. | kswg | Philip Feairheller (Samuel M. Smith absent) | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1240334337 | https://www.youtube.com/watch?v=W92CAjmy79E | 43:02; transcript from auto-captions, quotations unverified; retrieved 2026-10-16 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | |||||||||||||||
| kerione-utah-pro-human-ai-executive-order-2026-08 | Government and policy policy | Establishing Utah's Pro-Human Approach to Artificial Intelligence in State Government (Executive Order 2026-08) | https://governor.utah.gov/wp-content/uploads/2026.10.06-Pro-Human-AI-Executive-Order-1.pdf | Spencer J. Cox, Governor of the State of Utah | changed within the last six months, or a live service active | 2026-10-14 | 2026-10-06 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Utah Executive Order 2026-08, signed by Governor Spencer J. Cox on 6 October 2026, sets rules for the use of artificial intelligence (AI) by state executive-branch agencies under the Pro-Human AI Initiative. It assigns duties to the Department of Government Operations, the Division of Technology Services and each agency, and directs that the State-Endorsed Digital Identity (SEDI) Framework be developed and used, where applicable, as the state's trust infrastructure for AI. It is for readers following state-level adoption of verifiable identity and credentials. | Spencer J. Cox, Governor of the State of Utah | keri.one KERI Resources page keri-one-resources | Establishing Utah's Pro-Human Approach to Artificial Intelligence in State Government (Executive Order 2026-08) research/papers/kerione-utah-pro-human-ai-executive-order-2026-08 | 1 | 1 | ||||||||||||||||||
| didwebs-tf-2026-09-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-09-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1159004224 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-09-15 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Smith's review comments on v0.10.3 of the did:webs specification were discussed: an interoperability-bridge explanation, corrected Direct and Indirect Mode descriptions, a broader permitted AID (autonomic identifier) syntax covering self-addressing transferable and public-key-derived transferable and non-transferable AIDs, a recovery exception to the rule that divergent KERI event streams are invalid, a deactivation path for non-transferable AIDs, and an informative W3C VC (verifiable credential) example. On the open question of complex or nested fractionally weighted thresholds, the group discussed keeping the normative text trim with a worked example in an informative appendix, noting that ConditionalProof2022 supports recursive definitions. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1159004224 | Agreed that the specification supports complex or nested fractionally weighted thresholds | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2026-08-18 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-08-18 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1074331649 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-08-18 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The did:webs specification was reported ready for final review and approval, with the implementation needing to catch up. Discussion covered needed specification changes, restarting the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods process (issue 212), and the history of the resolver's placement in Hyperledger Labs. Action items included a reconciliation of the normative specification language against the Python reference implementation and a version 2 example. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1074331649 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-07-21 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-07-21 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1002373121 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-07-21 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Dossier segment pointed to an edge operators discussion on KERIpy. For did:webs, the final specification review was reported complete with significant revisions (pull request 209), and discussion turned to restarting the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods process. Other business covered ToIP (Trust over IP) stages of development for working groups and task forces, a "Bite Sized Trust" paper on duplicity and impersonation, the Trust Tasks work oriented toward AI, and assigning DOIs (Digital Object Identifiers) to new versions of the KERI specifications. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/1002373121 | Resume the 60-day DIF Recommended DID Methods review period | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| kerione-open-verifiable-communications | Organizations organization | Open Verifiable Communications | https://ovcalliance.org/ovc | GSMA | changed within the last six months, or a live service active | 2026-10-14 | 2026-06-18 | 2026 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The web page of Open Verifiable Communications (OVC), which it describes as a flagship project of the GSMA that defines how verifiable identity, authority and accountability can travel with communications such as calls. It states that the GSMA leads the project and that it is not owned or controlled by any single participant. For readers looking for the governance home of verifiable calling. | GSMA | v1.0 | keri.one KERI Resources page keri-one-resources | 1 | 0 | alliance | Telecommunications telecom | international | the Open Verifiable Communications alliance for verifiable calling | ||||||||||||||
| didwebs-tf-2026-06-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-06-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/914817026 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-06-16 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Dossier segment discussed a pull request adding new group operators, and Smith and Hardman reported a working session on open items in the Dossier specification. For did:webs, a second implementation now exists (a minimal TypeScript implementation for the DIF (Decentralized Identity Foundation) Recommended DID Methods process), the editors were completing a final revision, and there was an update on the DIF process. Zenodo access was also noted. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/914817026 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| cardano-academy-keri-course | Courses and training course | The Future of Digital Identity and KERI (Cardano Academy course, 18 units) | https://github.com/cardano-foundation/cardano-academy/tree/main/courses/Future_of_Digital_Identity_and_KERI | Cardano Foundation (Cardano Academy) | changed within the last six months, or a live service active | 2026-11-04 | 2026-05-13 | 2026 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A free, self-paced course of eighteen units, licensed CC-BY-4.0, that walks enterprise users, decision-makers and developers through self-sovereign identity, autonomic identifiers, the key event log, pre-rotation, witnesses and watchers, OOBIs, SAIDs, CESR, ACDC chaining, the vLEI, agents and wallets, and where KERI sits in the Trust over IP stack, with Veridian as the live reference. The Academy calls it its first AI-assisted course release; the written course is the source, with videos to follow. The live page at cardanofoundation.org/academy/course/digital-identity-keri was rate-limited when read, so the source repository is the page read on 21 October 2026. This is the training Thomas A. Mayfield referred to in the SEDI education thread of May 2026. | Cardano Foundation | 1 | 0 | ||||||||||||||||||||
| sedi-implementation-guide | Government and policy policy | Utah SEDI Implementation Guide, v0.1.0-draft (May 2026) | https://sedi.utah.gov/implementation-guide/ | Utah Department of Government Operations | changed within the last six months, or a live service active | 2026-10-16 | 2026-05 | 2026 | implementer | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The State of Utah's draft guide turning S.B. 275 into requirements for the department, wallet providers, verifiers, relying parties, governmental entities and health care providers, with conformance profiles and a mapping to the TSA mobile driver's license rule. For implementers who need the statute as requirements rather than as law. | 0.1.0-draft | 1 | 0 | ||||||||||||||||||||
| sedi-summit-2026-04 | Events event | SEDI Summit, April 2026 (Utah Valley University, Lehi, 20 and 21 April 2026) | https://sedi.utah.gov/agenda/ | Utah Office of Data Privacy | no change in six to eighteen months; still correct quiet | 2026-10-16 | 2026-04-20 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The agenda of the second SEDI Summit: Utah's legislators and officers on the statute just passed, and panels on finance, child protection, civil liberties, health care, local government, retail, and standards and conformance, closing with the resources offered to other states. The record of the Summit at which the consortium's home was named. | 1 | 0 | |||||||||||||||||||||
| kericonf-2026-conf-page | Documentation and education sites site | KERIConf 2026 (April 2026), the KERI Foundation's conference page | https://keri.foundation/confs/KERI/2026/apr/ | KERI Foundation | changed within the last six months, or a live service active | 2026-10-30 | 2026-04 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Foundation's public page for KERIConf 2026: the Day 1 and Day 2 YouTube playlists (still marked unlisted on YouTube), the transcripts of all 29 talks as HTML pages and one PDF, the interview transcripts, and a search over the transcripts. Read 30 October 2026; the 29 talk cards of this base link here and to each transcript page. | 1 | 0 | |||||||||||||||||||||
| didwebs-tf-2026-03-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-03-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/650608643 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-03-17 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | For did:webs, only a few open issues remained, the repository had been renamed, the did:web to did:webs transformation and resolution rules were clarified, and the editors had revised the specification; a second implementation was now needed for DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) method status. The Dossier segment noted one pull request against the specification and the need for a formal way to bring foreign artifacts into ACDCs. The April 15 ToIP (Trust over IP) Steering Committee meeting remained the target. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/650608643 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2026-02-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-02-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/564068353 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-02-17 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | In the Dossier specification segment, Hardman reported a long-open pull request to be merged unless questions arose and work on joint issuance that is adding edge operators to the ACDC specification. For did:webs, the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) Methods 60-day formal review had begun, the editors reported a review of all normative language, an updated ABNF (Augmented Backus-Naur Form) and repository cleanup, and the specification was described as substantively complete. A pathway to 1.0 was laid out: subcommittee review to March 9 using the ToIP (Trust over IP) review checklist, approval of a final draft by the KSWG co-chairs at the March 10 KSWG meeting with a resolution, public review to April 14, and submission to the ToIP Steering Committee on April 15. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/564068353 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| kerione-keri-suite-of-protocol-specifications-final-lf | Articles, press releases and opinion article | KERI Suite of Protocol Specifications Final (LF Decentralized Trust post) | https://www.linkedin.com/posts/lfdecentralizedtrust_decentralizedidentity-digitaltrust-keri-activity-7422391492561838081-uvzQ/ | LF Decentralized Trust | not checked, or the page gives no date unknown | 2026-10-14 | 2026-01-28 | 2026 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A LinkedIn post by LF Decentralized Trust announcing that the KERI, Authentic Chained Data Containers (ACDC) and Composable Event Streaming Representation (CESR) specifications from the Trust over IP (ToIP) KERI Suite Working Group had completed public review and were moving toward formal standardization. It describes CESR as the encoding layer, KERI as key management and ACDC as credentials, mentions the GLEIF vLEI and a GSMA calling demonstration as uses, and links the three specifications in its comments. | LF Decentralized Trust | keri.one KERI Resources page keri-one-resources | 1 | 0 | |||||||||||||||||||
| didwebs-tf-2026-01-20 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2026-01-20 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/477233177 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2026-01-20 | 2026 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A Dossier specification discussion led by Hardman covered how to express arity for group operators (MGRP, RMGRP) and qualifications for QGRP via an edge pointing to a required credential such as a vLEI (verifiable Legal Entity Identifier), with Smith noting that properties can be added to edges in a labeled property graph. The did:webs portion confirmed the whois section was removed, opened issue 168, and explained that a did:web DID (decentralized identifier) can be trusted only when a designated aliases ACDC in the keri.cesr stream commits to it, with proposed language highlighting that this lets a did:web DID be revoked after a DNS (Domain Name System) hijack. Next steps included listing ConditionalProof2022 as a DID extension and scheduling a second deep dive with the DIF (Decentralized Identity Foundation) Recommended DID Methods Working Group. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/477233177 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-12-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-12-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/401113089 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-12-16 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion of the alsoKnownAs default concluded that a did:web DID (decentralized identifier) should appear in the DID document only when the controller has placed it in a designated aliases ACDC, since only that commitment shows the controller authorized it, and the specification and implementation were to be changed accordingly. The meeting was split with a Dossier specification discussion, whose notes cite an article on evidence-based trust in telecommunications and the notion of preponderance of evidence. The next DID community tasks were restated: W3C registration, passing the W3C test suite and evaluation against the DID traits matrix. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/401113089 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-11-18 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-11-18 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/335052801 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-11-18 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The task force removed the whois section from the specification and adopted grey highlighted boxes to mark informative versus normative language, with excess informative text to move to an annex. Remaining coding tasks were identifier delegation in the DID (decentralized identifier) document services section and default did:keri and did:web entries in alsoKnownAs, and discussion covered referencing the KERI Suite Glossary instead of copying definitions, rewriting section 19.3 to name the five DID attacks, and the "decentralised-internet-identity" tag that links specifications and glossaries. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/335052801 | Removal of the whois section (section 12) from the specification, moved, seconded and passed (four yes, one abstention); use of grey highlighted boxes to indicate informative versus normative language, moved, seconded and passed (four votes) | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| sedi-summit-2025 | Events event | SEDI Summit 2025 (Utah Valley University, Orem, 17 October 2025) | https://www.uvu.edu/herbertinstitute/data_governance/state_endorsed_digital_identity_summit.html | Utah Office of Data Privacy with the Herbert Institute; co-hosted by the Utah House, the Utah Senate and the Department of Government Operations | no change in six to eighteen months; still correct quiet | 2026-10-16 | 2025-10-17 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The program page of the first State-Endorsed Digital Identity Summit: the sessions, speakers, demos and livestream links of the day Utah's program was first argued to other states. For readers tracing how the program was framed before the 2026 statute. | 1 | 0 | |||||||||||||||||||||
| kerione-state-endorsed-digital-identity-protecting-liberty | Government and policy policy | State-Endorsed Digital Identity: Protecting Liberty in the Digital Age | https://privacy.utah.gov/wp-content/uploads/SEDI_ProtectingLiberty.pdf | Utah Department of Government Operations (PDF metadata author: Christopher Bramwell, Chief Privacy Officer) | changed within the last six months, or a live service active | 2026-10-14 | 2025-10-17 | 2025 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A six-page paper (version 1.0, 17 October 2025) from the Utah Department of Government Operations that sets out State-Endorsed Digital Identity (SEDI), a model in which the individual controls a cryptographic identifier and the state endorses, rather than creates, that identity. It lists the model's basic requirements (legal framework, individual control, privacy, parental rights and delegation, security, backward compatibility) and invites other states to join a SEDI Consortium. It is for policy makers and readers following state adoption of decentralized identity. | Utah Department of Government Operations (PDF metadata author: Christopher Bramwell, Chief Privacy Officer) | 1.0 | keri.one KERI Resources page keri-one-resources | State-Endorsed Digital Identity: Protecting Liberty in the Digital Age research/papers/kerione-state-endorsed-digital-identity-protecting-liberty | 1 | 1 | |||||||||||||||||
| govops-sedi-interim-2025-10 | Government and policy policy | State-Endorsed Digital Identity: presentation to the Government Operations Interim Committee (15 October 2025) | https://le.utah.gov/interim/2025/pdf/00004004.pdf | Utah Department of Government Operations | no change in six to eighteen months; still correct quiet | 2026-10-16 | 2025-10-15 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Utah executive branch's own account of the SEDI program to the legislature in October 2025: its values hierarchy, its stakeholders, the input gathered and the services it expects to serve. A primary source for how the program was framed before S.B. 275. | 1 | 0 | |||||||||||||||||||||
| cardano-news-veridian-2025-09 | Articles, press releases and opinion article | Next-generation digital identity platform Veridian (cardano.org news, the Let's Talk Cardano episode) | https://cardano.org/news/2025-09-17-next-generation-digital-identity-platform-veridian/ | Cardano Foundation | changed within the last six months, or a live service active | 2026-10-21 | 2025-09-17 | 2025 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A summary of a Let's Talk Cardano episode on Veridian: quantum-resistant key management and Cardano as a root of trust for a monitoring service. The episode's own page was rate-limited when read. Read 21 October 2026. | 1 | 0 | |||||||||||||||||||||
| didwebs-tf-2025-09-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-09-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/249823297 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-09-16 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion covered the DIF (Decentralized Identity Foundation) Recommended DID (decentralized identifier) method process: its rationale of narrowing more than 200 DID methods to a short list in web-based, ephemeral and fully decentralized categories, the methods in review (did:webvh first, then did:cheqd, did:web+ and did:scid), and that the process makes no quality or security judgment. Independent security audits of KERI (one by Cardano, one by healthKERI, both unpublished) and an eventual security comparison of did:webvh and did:webs were raised. Action items were to arrange the did:webs submission to DIF and to look at migrating to Spec-Up-T. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/249823297 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-08-19 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-08-19 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/239370241 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-08-19 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted the TODO list now at the root of the did:webs meeting pages, the did:webs resolver updated and integrated with the Universal Resolver, and a request to take down the Hyperledger Labs repository so the GLEIF IT repository becomes definitive. Discussion proposed tying the ABNF (Augmented Backus-Naur Form) for the method-specific identifier to the current KERI version and restricting the AID (autonomic identifier) to valid CESR digest strings, and named the next DID (decentralized identifier) community tasks: W3C registration, passing the W3C test suite and evaluation against the DID traits matrix. Formal submission of did:webs to the DIF (Decentralized Identity Foundation) DID Methods Working Group for DIF Recommended status was proposed. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/239370241 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| gleif-hackathon-training-sessions | Events event | vLEI Hackathon support: live training sessions and office hours (GLEIF) | https://www.gleif.org/en/newsroom/blog/vlei-hackathon-all-you-need-to-succeed | GLEIF | changed within the last six months, or a live service active | 2026-10-21 | 2025-07-30 | 2025 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | GLEIF's description of the hackathon's Monday live sessions covering the self-paced training and the one-to-one technical office hours with Kent Bull and Esteban Garcia. Read 21 October 2026. | GLEIF Global vLEI Hackathon 2025 gleif-hackathon-2025 | 1 | 0 | ||||||||||||||||||||
| didwebs-tf-2025-07-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-07-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/220069952 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-07-15 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The task backlog was reviewed and is to be moved to a published did:webs TODO page, with plans to have the Python implementation pass the W3C DID (decentralized identifier) test suite in continuous integration and to make the Universal Resolver driver work correctly. Discussion covered archiving the Hyperledger Labs resolver repository, what it means to resolve a did:webs DID (full resolution requires handling identifier delegation and multi-signature), and difficulties with the restricted meeting link. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/220069952 | Archive the Hyperledger Labs resolver repository; do not return DID resolution metadata in did.json; use GLEIF-IT/did-webs-resolver as the source of truth for the did:webs resolver; rename the package from "dkr" to "dws" | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| kswg-2025-07-08 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-07-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/215842817 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-07-08 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the ToIP five-year symposium on 15 and 16 October 2025, which invited KSWG presentations, and a State of Utah identity summit on 16 October. Discussion covered a proposal for a URN namespace for Self-Addressing Identifiers (SAIDs), of the form urn:SAID:, which needs help with its ABNF grammar and was offered a home in this working group, possibly with a task force, and the blindable state Transaction Event Log (TEL) described in the ACDC specification's blindable state registry section. Action items from the June meeting to start the did:webs meetings, announce them and add them to the ToIP calendar were recorded as complete. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/215842817 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2025-06-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2025-06-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/203784264 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-06-17 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A reboot presentation on the did:webs specification reviewed the existing KERI-specific extensions: the provisional application/CESR media type registered at IANA (Internet Assigned Numbers Authority), with a note to wait until the CESR specification is final, and the ConditionalProof2022 verification method, which still needs registration as a DID (decentralized identifier) extension and an updated specification. Open issues listed were identifier delegation as a service, ACDC-based signing, service endpoints, DID document versioning against the KERI event stream, alignment with the ToIP (Trust over IP) glossary, updated examples and compliance with current KERI versions, together with the next steps for finalizing the specification and a request for commit rights on the specification repository. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/203784264 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| kswg-2025-06-10 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-06-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/198606849 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-06-10 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted GLEIF-sponsored verifiable Legal Entity Identifier (vLEI) and KERI training material, the No Phone Home movement, a change in mobile driver's license (mDL) guidance on server retrieval, and Utah privacy panels. Reports listed pull requests due on all specifications for the field order of seals and the version message string. Discussion covered whether to write a joint credential issuance specification for KRAM joint versus true multisig issuance, a proposal for regular did:webs meetings with the aim of DIF recognition and a W3C web-based DID methods group, and Smith's summary of the KERI, CESR and ACDC version message string issue (keripy discussion 1023). | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/198606849 | No separate did:webs task force; add a did:webs meeting to this working group every third Tuesday of the month for the foreseeable future | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | |||||||||||||||||
| kswg-2025-05-13 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-05-13 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/179601409 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-05-13 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements reported on the Internet Identity Workshop (IIW), including a State of Utah session on its privacy bill for state-endorsed digital identities, the Veridian Wallet released under the Apache 2 license, three sessions on KERI security, a KERI Foundation meeting with a healthKERI presentation, and an OpenSSF Alpha-Omega meeting. Reports covered CESR 2.0 parser support in KERIpy, which counts bytes for all codes rather than primitives for some, and Hio changes for multiprocessing with spawn, a hierarchical state machine in the Doer hierarchy, and API changes to enter, exit and recur. Action items to tag the specification repositories at 0.9 and to review open pull requests were recorded as complete. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/179601409 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | ||||||||||||||||||
| utah-sb0260-2025 | Government and policy policy | Utah S.B. 260 (2025), Individual Digital Identity Amendments | https://le.utah.gov/~2025/bills/static/SB0260.html | Utah Legislature | replaced by a named successor; kept for history superseded | 2026-10-16 | 2025-05-07 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The 2025 framework statute that set Utah's digital identity principles and ordered the research year that produced the 2026 program statute. Kept for history; the operative law is S.B. 275. | 1 | 0 | |||||||||||||||||||||
| vlei-dev-community | Working groups and meeting series meeting-series | vLEI Developer Community meeting (GLEIF-IT) | https://github.com/GLEIF-IT/vLEI-dev-community | GLEIF-IT | changed within the last six months, or a live service active | 2026-10-21 | 2025-03-27 | 2025 | implementer | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A Thursday 16:00 UTC developer meeting for the vLEI with a prioritized backlog, kept in a GLEIF-IT repository; the GLEIF hackathon post names dev-portal.vlei.dev as the developer wallet documentation, not opened. Read 21 October 2026. | 1 | 0 | |||||||||||||||||||||
| kswg-2025-03-11 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-03-11 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/127762433 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-03-11 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted Hardman's publication of the Verifiable Voice Protocol draft and several white papers. Reports covered multiprocess support in Hio and its merged Windows support, and a pending Windows support pull request for KERIpy awaiting a Windows build in continuous integration. Discussion covered coordinating an upgrade of Origin to KERIpy 1.1.32 in the short term and 1.2.x after some verifiable Legal Entity Identifier (vLEI) issuances, KRAM implementation with joint versus true multisig issuance, and a code walk-through by Smith of the Hio multiprocess changes. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/127762433 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | ||||||||||||||||||
| kswg-2025-02-11 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-02-11 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/100499457 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-02-11 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The specifications report recorded that the ToIP Technology Stack Working Group (TSWG) had approved the KERI, ACDC and CESR specifications in their 0.9 form at its October 2024 meeting, closed the ACDC Task Force and contributed the specifications to the KSWG. Discussion gave an overview of the working group and its community meetings (this monthly call, the KERI implementers call and KERI Foundation meetings), next steps for the specifications (fixing references and tags, working examples, a pass over open pull requests and issues), simplifying the Trust Spanning Protocol (TSP) wrapper, and a KRAM discussion thread (keripy discussion 934) pending an implementation. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/100499457 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | ||||||||||||||||||
| kswg-2025-01-14 | Meetings (one per entry) meeting | KSWG monthly meeting, 2025-01-14 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/81362945 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2025-01-14 | 2025 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered specification work (splitting out the glossary, making examples cryptographically accurate, fixing tags and references), sub-packaging inside KERIpy before any split into separate repositories, the KERIA 0.2.0-rc1 release candidate and an upcoming SignifyTS (SigTS) 0.3.0 release. Discussion items included a terminology engine built on two glossaries (the ToIP glossary and the KERI main glossary), Discord discussions, encrypt-sender-sign-receiver (ESSR) for HTTP requests between Signify and KERIA, and version compatibility between KERIpy 1.1.x and 1.2.x. An action item records splitting each Spec-Up specification file into head, body and terminology sections for migration to Spec-Up-T. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/81362945 | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | ||||||||||||||||||
| kswg-2024-12-10 | Meetings (one per entry) meeting | KSWG monthly meeting, 2024-12-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/70090753 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-12-10 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The group reviewed its meeting cadence for 2025, setting the KSWG call on the second Tuesday of each month alongside the developer call on the first and third Tuesdays. On the specifications, the notes record that the ToIP Technology Stack Working Group (TSWG) had moved them to the KSWG so it no longer had to approve them; the group planned unit tests that generate the Self-Addressing Identifiers (SAIDs) for every example, set the January meeting as the target for finishing formatting and terminology work, and asked members to review issues and pull requests in the specification repositories. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/70090753 | Proposal to move to a once-a-month meeting cadence approved, on the second Tuesday of each month | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | |||||||||||||||||
| kswg-2024-11-12 | Meetings (one per entry) meeting | KSWG monthly meeting, 2024-11-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/56918017 | Trust over IP (KSWG) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-11-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements reported on Internet Identity Workshop (IIW) sessions: what is needed to hand the specifications to ISO, including proof of implementation and adoption, a call to list KERI implementations on the WebOfTrust/KERI landing page, licensing advice for the Trust Spanning Protocol (TSP), and talks on did:webplus and user experience. Discussion covered pseudocode for computing compact Self-Addressing Identifiers (SAIDs) and the exclusion and Granted Claims terms of the Open Web Foundation (OWF) 1.0 patent mode in Appendix B, Section 3 of the ToIP agreement. Earlier action items on the 0.9 versions of the three specifications, OWF signing and a delegated rotation corner case were recorded as complete. | kswg | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/56918017 | Cancel the 26 November 2024 meeting, making 10 December 2024 the next meeting | KSWG Meeting Pages (index of agendas, notes and recordings) kswg-meeting-pages | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-10-15 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-10-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/43253761 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-10-15 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered publication of the verifiable Legal Entity Identifier (vLEI) as an ISO standard (KERI and ACDC are not yet ISO specifications), a new weekly vLEI developers meeting, the cadence of specification calls after the move to the KERI Suite Working Group, and Digital Identity unConference Europe (DICE) 2025 dates. Reports and discussion covered guidance relayed in the notes that contributors need not sign the Open Web Foundation agreement (OWFa) separately because the working group charter binds participants, set against the OWFa text on signing for a final specification, in relation to the 0.9 versions of the specifications. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/43253761 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-10-01 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-10-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/37584897 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-10-01 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted a Technology Stack Working Group (TSWG) plenary ratifying the KERI decisions. Reports proposed that the task force's final act be a 0.9 release of all the specifications sealed by contributor Open Web Foundation agreement (OWFa) signatures before new work begins in the KSWG, and noted that nearly all specification pull requests were merged, a Python 3.11 branch of KERIpy and Hio for Global Legal Entity Identifier Foundation (GLEIF), and KERIpy 1.2.0 coming. Discussion covered regulatory pilot dependencies, technology readiness levels for the KERI Suite, a suggestion to publish the SAID (self-addressing identifier) specification separately, and peer-to-peer percolation of OOBI (out-of-band introduction) URLs and schemas. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/37584897 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-09-17 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-09-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23012982 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-09-17 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements confirmed that the KERI Working Group was listed by Trust over IP (ToIP), with a plan to cut a 0.9 version of the specifications, seek Technology Stack Working Group (TSWG) approval and move the specifications to new repositories under the working group, and noted completed penetration testing at healthKERI. Reports covered closing the last KERI specification pull requests toward 0.9, the KERIpy 1.2.0 release candidate and migration, and clearing rather than migrating escrows. Discussion covered the state of watcher code in KERIpy, transaction event log (TEL) witnesses and observers and TEL discovery, and a diagram of the Global Legal Entity Identifier Foundation (GLEIF) regulatory pilot repositories. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23012982 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-09-03 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-09-03 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23000127 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-09-03 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted that the KERI Working Group charter had been submitted to the Trust over IP (ToIP) Steering Committee, that Global Legal Entity Identifier Foundation (GLEIF) had moved to a steering committee role, discussion of self-addressing identifiers (SAIDs) in the Overlays Capture Architecture (OCA) specification, and a ToIP wiki platform migration. Reports covered KERIpy refactoring, KERIA operation identifiers for exchange messages and KERI specification typo fixes. Discussion reviewed the proposed charter, questions on how its secure privacy, authenticity and confidentiality (SPAC) scope relates to the Trust Spanning Protocol (TSP) task force, license concerns from the Technology Stack Working Group (TSWG) re-charter, and the F and F* values of KAWA (KERI's Algorithm for Witness Agreement) when choosing a witness pool threshold. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23000127 | No objections to the proposed KERI Working Group charter | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-08-20 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-08-20 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23000069 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-08-20 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the KERI Foundation's GitHub repositories. Reports covered a KERI specification pull request awaiting the submitter's EasyCLA, KERIpy work on technical debt, delegation escrow, superseding rotation and variable-length encryption codes, a KERIA migration from KERIpy 1.1 to 1.2, and a merged Signify-TS IPEX (Issuance and Presentation Exchange) pull request. Discussion centered on a proposal to move the KERI and ACDC work from a task force to a KERI Suite Working Group, keeping the Open Web Foundation license and repurposing the task force charter, with the Technology Stack Working Group (TSWG) considering a return to the World Wide Web Consortium (W3C) license, then on project status for potential investors, promiscuous witnesses and watchers, and KERI's Algorithm for Witness Agreement (KAWA) thresholds. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/23000069 | Proposal to move forward as a KERI Suite Working Group instead of a task force approved in a chat vote (11 in favor, none against or abstaining), with chairs proposed as SS, PF and KG; chair election to take place at the first working group meeting | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-08-06 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-08-06 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999595 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-08-06 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the KERI Foundation's new GitHub organization and planned biweekly members meetings. Reports covered new encrypter, decrypter and cipher classes supporting variable-size encrypted data and a Streamer class for CESR streams in KERIpy, KERIA pull requests for the CESR stream changes and multisig Issuance and Presentation Exchange (IPEX), and a KERI specification pull request. Discussion covered a Trust over IP (ToIP) Steering Committee idea of a KERI working group to unblock the specifications, which were waiting on review of RFC 2119 changes, along with decentralized identifier (DID) developments and the new KERIpy classes. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999595 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-07-23 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-07-23 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997930 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-07-23 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the KERI Foundation, which aims to fund wallet, witness, watcher, web and wizard work, and the addition of recordings to earlier meeting pages where found. Reports covered splitting the WOT-terms material into Docusaurus, Spec-Up and Kerific repositories, and healthKERI running watchers, witnesses and agents in staging. Discussion covered identifier abandonment, the GitHub discussions opened for the KERI and ACDC specifications, and a CESR 2.0 refresher. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997930 | https://zoom.us/rec/share/Z1UaiabGg5zvVdpko1bj9QBNJpiq3Qm2mQhVenpViV4p2G5CMg4uN3EhqTjJgNHo.JgNljcwKqtVz3d4y | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| kf-github-profile | Documentation and education sites site | KERI Foundation GitHub profile: one-click KERI through the 5 Ws | https://github.com/keri-foundation/.github | KERI Foundation | changed within the last six months, or a live service active | 2026-10-21 | 2024-07-20 | 2024 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The Foundation's GitHub profile page, stating its aim to finish the code base through Wallet, Witness, Watcher, Web and Wizard, and its education role. Read 21 October 2026. | keri-foundation GitHub organization keri-foundation-org | 1 | 0 | ||||||||||||||||||||
| acdc-tf-2024-07-09 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-07-09 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997428 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-07-09 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted that the Tuesday specification meeting would go biweekly, alternating with the implementers call, that healthKERI had engaged penetration testers on its proof-of-concept stack, and an upcoming Trust Spanning Protocol talk on appraising key state and issuance state. Reports covered a new Hio version, KERIpy location records and a witnessing issue, KERIA notifications and identifier endpoint changes, and a proposal to split KERI Suite Search Engine (KERISSE). Discussion covered end role authorizations and the risk of dynamic role names, the watcher network, and the differences between CESR 1.0 and 2.0. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997428 | https://zoom.us/rec/share/Yw1Y-hl9bcozsn7raLj2zFDs8Shvbkq6sTnvD54A5sjTQbb5NYU--VEYD8ilk3yz.rqF0PFbGuLh36F0r | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-07-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-07-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999891 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-07-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion considered how did:webs could be used with web sites that have the Signify browser extension enabled to establish trust in both directions, noted as a promising use case, alongside open pull requests and issues. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999891 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-07-02 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-07-02 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997559 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-07-02 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted no changes to the specifications or KERIpy. Discussion covered new GitHub discussion items for KERI and ACDC questions, the "5 Ws of One Click KERI" approach to complexity management (wallets, web and wizard among them), and a suggestion to describe KERI as complicated rather than complex when speaking with newcomers. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997559 | https://zoom.us/rec/share/09f23XjfhLmOKETP8iQ71YZzUjNgMvTCo__f8sDNGnRNLoiSJ2ydxOQY2nN7lQzH.2PYfYOmkart2R_uL | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-06-25 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-06-25 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997513 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-06-25 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered a KERI specification change moving the receiver field to the top level of exchange messages, a suggestion to reference non-open-source implementations in the foreword for ISO, editorial pull requests, and the new Spec-Up-T repository. Discussion reviewed Digital Identity unConference Europe (DICE), with eight KERI sessions, a master's thesis proposing KERI and a public watcher network for the Swiss eID, and a suggestion to present the material less confrontationally, then how to gain traction for KERI and FIDO2 integration. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997513 | https://zoom.us/rec/share/1SqvcTD5prbZDjz_YTO6sHdpREtX4AwsvrWwEG9K9WxbBoq8Hs6TVSCUbrLzGLbi.0XABBUXDCKHstDC0 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-06-11 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-06-11 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997334 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-06-11 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted that RFC 2119 changes were complete and merged in all the specifications, along with a KERIpy key state notifier fix, KERIA OpenAPI documentation and a pending delegation pull request, and Signify-TS test work. Discussion covered a pull request to the cesr-test-vectors repository, whether an email and ACDC-based threshold recovery service would be custodial, how trust differs between blockchain and KERI ecosystems with watchers and jurors, and Apple's private cloud compute and password announcements. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997334 | https://zoom.us/rec/share/-u8rCjaBbG_O1k5LW5WUsDyiliwwQgqkbGW2t1xJjHONdKzhPcsmaGCOWRWssXfY._t5ElT8l0cHuQ6is | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-06-04 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-06-04 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997251 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-06-04 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered versioned terms in the Trust over IP (ToIP) terminology tooling. Reports covered RFC 2119 changes pushed to the CESR specification with KERI and ACDC to follow, KERIpy bug fixes, Docker and documentation updates and externalized exchange message payloads, and a KERIA delegation approval pull request. Discussion covered FIDO2 integration in light of did:tdw, arguing that pre-rotation alone does not protect against dead attacks and that KERI addresses persistent control despite key compromise, a proposed KERI mini-conference program at Digital Identity unConference Europe (DICE), and whether decentralized identifier (DID) documents have a use with KERI. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997251 | https://zoom.us/rec/share/2Y9EHPhpBi9kZw6hPNsvcXxEH8sJjAFvRWr6GB614h7cBSamp48cBPkkuJRUN_ko.2FWUtIU5NSDJohC3 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-05-28 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-05-28 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997020 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-28 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered Digital Identity unConference Europe (DICE), a possible KERI mini-conference there, and Trust over IP (ToIP) sessions at the European Identity Conference. Reports covered escrow processing of delegated events in KERIpy and KERIA with a manual approval step, and no new specification pull requests. Discussion covered the history of local and remote sources in event processing, user experience, and how FIDO2 relates to KERI, with Smith describing FIDO2 as an authentication factor for federated identity whose key rotation KERI handles better; the page also copies part of the meeting chat with learning resources for newcomers. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997020 | https://zoom.us/rec/share/a-3DYkiWbQe3IBLxPF0XHbw0wOXW2Z7ZTNXkvf2hRgOL4eWUO5xZK8rbuXpSGIRD.zu5-PRXJ8amgTCSl | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-05-21 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-05-21 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996620 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-21 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered Smith adding RFC 2119 requirement language to all the specifications, delegation fixes in KERIpy and KERIA that reverse the order of witnessing and delegation approval, and a Technology Stack Working Group (TSWG) proposal for a did:tdw task force put on hold. Discussion covered making community meetings more transparent and inclusive and whether to hold special-topics calls on higher-level subjects, questions from the Digital Identity unConference Europe (DICE) organizers on KERI's relation to the EU electronic identification and trust services regulation (eIDAS) 2 and the EU Digital Identity (EUDI) wallet framework, and where KERIA should process the escrow of delegated events. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996620 | https://zoom.us/rec/share/n5Q2jGnTTp82ZolZ1wSGPQuBph2gqvQGwMdpKtL3Nqn74G8czFEqyZojU-2cV_WZ.RKWHWQsqsq6QWe3x | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-05-14 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-05-14 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996615 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-14 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Agenda only; no notes recorded: moving the specifics of the Issuance and Presentation Exchange (IPEX) protocol out of the ACDC specification, and an update on key state being written to Cardano blockchains. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996615 | https://zoom.us/rec/share/J3CbXMwAVjGi5-2esNpXavFPtZVjX54vL2CqgPMPn1tb3UZWDgDSMdaukljjcAB6.Y1QiZZ2E8shyVFHt | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-05-10 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-05-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999456 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-10 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports restated IIW (Internet Identity Workshop) Spring 2024 (April 16 to 18), the public review period past 120 days and extended until the 1.0 requirements are met, and the Elixir CESR parser work. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22999456 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-05-07 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-05-07 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997695 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-05-07 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Action-item review recorded the Technology Stack Working Group (TSWG) chairs' view that the specifications still need RFC 2119 language and a conformance section before submission, likely followed by a second public review. Reports noted a KERIpy issue with multisig end-role authorization where seal sequence numbers must be hex strings. Discussion covered a proposed Self-Certifying Identifier (SCID) specification and security guide linked to did:tdw, profiles for different uses of KERI autonomic identifiers (AIDs), and a roadmap to move to CESR 2.0 by the end of 2024. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997695 | https://zoom.us/rec/share/Rq7i9q8k9u0QWfTbkQf5UrJXgCjKEViFuAYAOgI9gtFWazZf5JLai3X8YgLVYKtX.fx_rOmQqHiNT5tK7 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-04-30 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-04-30 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998598 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-30 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered the need for bug report and other issue templates and GitHub Discussions across the repositories, CESR-native serialization and an annotator working in KERIpy with encryption codes and watcher support next, and GitHub API additions to KERISSE (KERI Suite Search Engine). Discussion covered query response error routes in the KERI API (KAPI), including how watchers and judges should report duplicity against a threshold, and Smith's demonstration of CESR-native serializations and annotation. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998598 | https://zoom.us/rec/share/hkeVeNrkev0rvXJ_EB-SAfdU2Cu6QZExtK-OwDKceGcVHVK_u_L4wkUsfPsL-7HY.tFq5kvFjJbGt-fmn | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-04-26 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-26 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998413 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-26 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports restated IIW (Internet Identity Workshop) Spring 2024 (April 16 to 18), the public review period past 120 days and extended until the 1.0 requirements are met, and the Elixir CESR parser work. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998413 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-04-23 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-04-23 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998797 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-23 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The meeting reviewed Internet Identity Workshop (IIW) 38, listing 19 KERI-related sessions, among them Smith's talks on scaling signing infrastructure and CESR 2.0 encoding size, the European Banking Authority (EBA) pilot with the verifiable Legal Entity Identifier (vLEI), secure witnesses and the Trust Spanning Protocol (TSP), and noting the new did:tdw (TrustDIDWeb) method. After reviewing the issues and pull requests for the KERI, ACDC and CESR specifications, the group took up closing their public review. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998797 | https://zoom.us/rec/share/TN5h_j_o5PZKKQoCAQ6JSVpHDPgDzTV5ezkC_j7rqR6rqIaDtMvJRpPeOmtLLUA.G2g034ALzbiwdw0q | Motion to end the public review of the KERI, ACDC and CESR specifications passed | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-04-12 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998582 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon that closed issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998582 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-04-09 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-04-09 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998833 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-09 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered planned Internet Identity Workshop (IIW) presentations and NordLEI becoming the second Qualified verifiable Legal Entity Identifier (vLEI) Issuer. Reports noted that KERIpy, KERIA and SignifyPy had dropped the GitFlow branching model for a single main branch. Discussion covered re-identification risk from context, a Signify-TS passcode length question traced to CESR padding changes, holding the 20-day specification review huddle at IIW, and how KERI can use a blockchain as a backer rather than requiring one. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998833 | https://zoom.us/rec/share/kjek3FeDv8kq9KUIe3vJq2K-UlDruXOwihyK_P3tX6DtmrCG0_TYkwmi6H7tTWbk.gHHmGtx4zzaXgjAs | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-04-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-04-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995116 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon held that week to close the issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995116 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-04-02 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-04-02 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996705 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-04-02 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered the three specifications in public review, KERIpy work on CESR-native serialization (seals remaining), cleanup in Matter and a new database structure with versioning and migration, and pull requests adding search to Spec-Up. Discussion covered an ACDC specification issue seeking a volunteer, and a proposal to use a remaining sniff code in the CESR parser to signal an annotated CESR stream. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996705 | https://zoom.us/rec/share/JwA_CujjbzM3e-LQ2xQ_f_2FmrUryQA0mSslxAkPKFpAEGK40d4bX66tkH06HMcJ.BCnjkMdUqpjNZwT7 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-03-29 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-29 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997846 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-29 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 120 days and still extended until the 1.0 requirements are met. Reports noted the Elixir CESR parser work and a hackathon planned for the following week to close the issues related to the specification's examples. Discussion repeated the diagrams directory and the remaining pre-review items: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997846 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-03-26 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-03-26 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996000 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-26 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered a possible change to RFC 9421 HTTP message signatures in KERIA, Signify-TS and SignifyPy, and the opening of the 30-day public review of the KERI, ACDC and CESR specifications. Reports pointed to the issues and pull requests in the three specification repositories. Discussion covered using CESR (qb64) in HTTP signature headers for cryptographic agility and an upcoming CESR pull request addressing a vulnerability found while getting CESR-native events working. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996000 | https://zoom.us/rec/share/FbB176sKik9x7wMAYezHaXr-n20pF6YhTHmfeLjMY_5qsQw3gN5CIuIQ5GNZ1Vo.a0BXSJPsQxwpsgBE | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-03-19 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-03-19 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22984050 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-19 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered KERIpy support for creating and parsing version 2 messages of all events, and patch releases of KERIpy (1.1.8) and KERIA (0.1.4) driven by qualifying Qualified verifiable Legal Entity Identifier (vLEI) Issuers (QVIs) and working with an existing QVI. Discussion covered CESR stream interoperability examples and a planned cesr-test-vectors repository, the idea of a KERI-based OpenID Connect (OIDC) identity provider and the risk of mixing security postures, the goals of the European Banking Authority (EBA) pilot, and DPoP (Demonstrating Proof of Possession, RFC 9449) as an analogy. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22984050 | https://zoom.us/rec/share/a64UFo9r2xFqzqjaTaHJ0YmcN_uZCOuwxf-oS084mUAb5_swcTT5bbtL4Gzw1vu8.TCfCmi9uSCQSaKpj | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| utah-hb0491-2024 | Government and policy policy | Utah H.B. 491 (2024), Government Data Privacy Act, enrolled | https://le.utah.gov/~2024/bills/hbillenr/HB0491.pdf | Utah Legislature | no change in six to eighteen months; still correct quiet | 2026-10-16 | 2024-03-19 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The statute that created Utah's Office of Data Privacy and its governance, the institutional ground on which the State-Endorsed Digital Identity program was later built. For readers who need to know what the host of the SEDI Summits is in law. | 1 | 0 | |||||||||||||||||||||
| didwebs-tf-2024-03-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998639 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-15 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 90 days and still extended until the 1.0 requirements are met, and the next meeting (2024-03-22) was cancelled for travel. Reports noted the Elixir CESR parser work and the Python reference implementation's upgrade to KERI 1.1.4. Discussion pointed members to the decentralized diagrams and images directory for comment and repeated the implementers draft and remaining pre-review items. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998639 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2024-03-12 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-03-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994363 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered KERIpy work toward CESR and KERI version 2.0 events and patch releases of KERIpy (1.1.7) and KERIA (0.1.3), a pending Signify-TS change to signature header calculation, did:webs examples and public review fixes, and a CESRide version bump. Discussion covered Internet Identity Workshop (IIW) session plans, including CESR performance and interoperability demos, review of the blog post launching the specifications' public review, and the KERI API (KAPI), including the XIP message for starting a verifiable transaction set and routes for exchange and query messages. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994363 | https://zoom.us/rec/share/I11-vzDOnOcFpZ1-VD3Wbjad__So6oXzT6gw44EZZp3l1IgRGSwPs7D5KFgFPSwS.tpkrrTYzDvS6IE9O | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-03-08 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995849 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-08 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted the Python reference implementation upgraded to KERI 1.1.4, failing unit tests and a walk-through of the getting-started guide, and continued work on an Elixir CESR parser. Discussion presented the fully automated approach to a decentralized diagrams and images directory: definitions of a diagram and a reference to one on the WebOfTrust and trustoverip repositories, references as a reputation signal, captured surrounding text as context, and a request for input on which repositories and image paths to include. The implementers draft and remaining pre-review items were repeated. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995849 | https://zoom.us/rec/share/3pRHl8rtVu7Up7PNCsUhz-rnCy8G31gMQibTJ9ZoyNVdXVtghu1o4BNVR9v-yyh9.j1NuiBZrh7_LfIgh | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-03-05 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-03-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998092 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered a draft blog post for the ACDC public review, plans for KERI talks at Digital Identity unConference Europe (DICE), and a World Wide Web Consortium (W3C) pull request on enveloped verifiable credential (VC) presentations. Reports covered KERIpy command-line fixes, a new KERI API (KAPI) repository, and a did:webs presentation. Discussion covered next steps for announcing the public review, the KAPI document and a script parsing KERIpy for routes, and community shared witness pools. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998092 | https://zoom.us/rec/share/087JmLjtXqV9NEoaGs-p4Uc_LPWn-gKUxQDjFd-NEutqN_QtsPFPoCSL_vejj1g.VE86ShW1YDvnBpG2 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-03-01 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-03-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997137 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-03-01 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered an Elixir CESR parser whose author has been filing pull requests and issues on the CESR specification, the wrap-up of the diagram list with simple rules (diagrams live in a /diagrams folder of their own repository and are referenced, not copied), and Switchchord going live with activity across several industries. Discussion repeated the implementers draft and interoperability goals and the remaining items before final public review: the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997137 | https://zoom.us/rec/share/x2nCcuJaOPIv6MH415-n7YTrjOtPceOQUjkCK0ZaHPnGnZW0p8MCIOuMySnGOIc.YoBL-4WaIGH-BSFW | A minimal-effort version of the diagram list was adopted, with simple rules: the repository is on trustoverip, the diagram is in /diagrams, diagrams are referenced in a decentralized way, and copies are avoided | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||
| acdc-tf-2024-02-27 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-02-27 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994386 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-27 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the growing success of cyber attacks and a new Spec-Up cross-reference tool from the Concepts and Terminology Working Group. Reports covered KERIpy 1.1.1 and KERIA 0.1.1 with multisig credential revocation fixes, CESR version 1.1 and 2.0 version strings in KERIpy development, did:webs public review, and external references in Spec-Up. Discussion reviewed the specification issues and the readiness of CESR, KERI and ACDC for public review, and an enhancement to fractionally weighted thresholds. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994386 | https://zoom.us/rec/share/7a9YrczLJOVnnOAQp_2FXTwn-QEpC5WePSuWuIqONtW26UD_BO9XSgULwDo6TtZ4.lZC7X6Fq-ge9eP41 | Motion to ask the Technology Stack Working Group (TSWG) to announce public review of the KERI, ACDC and CESR specifications passed unanimously | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-02-23 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-23 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995987 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-23 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The public review period was reported past 60 days, and a report noted pull requests and issues filed on the CESR specification while implementing a CESR parser. Discussion covered a planned article on the reference implementation aimed at organizations that want the discoverability of did:web with stronger security, citing the LEI (Legal Entity Identifier) and vLEI (verifiable LEI) and the separation of identifier authorization from domain control, alongside the diagram index in KERISSE (the KERI Suite search engine) and the implementers draft. An action item was to add the CESR IANA (Internet Assigned Numbers Authority) provisional registration link to the IANA considerations. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995987 | https://zoom.us/rec/share/cKkCnsY7JGyzl-hHuDmqtwHbWbiNsqQ7oMJblfWHSXjXXsa5iHzXSPV1kztL_dc.b4Dnt2rkZ-US4z0g | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-02-20 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-02-20 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995159 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-20 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered publication of CESR's provisional media type registration by Internet Assigned Numbers Authority (IANA) and the merge into KERIpy of the misfit branch (new escrows, local and remote parsing, superseding delegated rotation) and enhanced fractionally weighted thresholds. Discussion reviewed KERI specification issues to judge readiness for public review of the KERI, ACDC and CESR specifications, which was not yet reached, and starting a specification for a KERI API. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995159 | https://zoom.us/rec/share/NlQ0uHqZDCj0CuFPAns5Peh_MFDD5orN_3Z87Ztgj-_eZCRz3c1LwVUj409ZDoGA.7qOhRleyJYTb1MGf | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-02-16 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995119 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-16 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion covered diagramming across ToIP (Trust over IP): a community index of diagrams as a metadata table, starting with KERISSE (the KERI Suite search engine), with diagrams kept close to their source repositories, an automated broken-link checker, and a decentralized model for judging which are current. The implementers draft and interoperability between implementations before final public review were revisited. Action items included updating the specification version with a call for additional implementations, defining a minimal interoperability profile with optional features such as whois in further profiles, and building a KERISSE-maintained list of diagrams and images. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995119 | https://zoom.us/rec/share/Wqu8x6j93SlM89vCCZzlCM6PVep6KzB5O-kaNYT_JsWCDwRUoeRdEEZtS640cSsi.ry0w28fM4Mhjxz7V | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-02-13 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-02-13 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996332 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-13 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered sorting of specification issues, with references the largest remaining task, release candidates of KERIpy, KERIA, Signify-TS and SignifyPy ready to merge, and the did:webs reference implementation upgraded to KERIpy 1.1.0. Discussion covered a CESR specification issue, a possible Trust over IP (ToIP) requirement for two interoperable implementations and test vectors for CESR, KERI and ACDC, migrating a multisig autonomic identifier (AID) from a command-line wallet to KERIA, and how an issuer could make credential issuances publicly discoverable. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996332 | https://zoom.us/rec/share/GdEmn9AfH6dGtirPUo6nFhRMLsMj53G87CqExnT_HwpY3jmTNhn4FHI0YIceNiST.2GET3-r4Ym5vqsq6 | Merge the release candidates and cut releases of KERIpy, KERIA, SignifyPy and Signify-TS (approved) | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-02-09 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-09 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989306 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-09 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The action-item review reported the provisional IANA (Internet Assigned Numbers Authority) media type registration for CESR as complete, and a co-chair was announced as having stepped down. Discussion proposed an implementers draft so that multiple implementations can verify the steps and show interoperability before final public review, and noted the value of explaining to outside audiences that did:webs separates signing control from web administration control. Remaining items were the whois pull request, the normative and informative split, service endpoint updates and the KERIpy release candidate. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989306 | https://zoom.us/rec/share/u3eWA837Yh0y5u3PIMlSlUVKu6CqJI3_BhMDqqBliRM0Ztz0TIuWptxNwc3FTnFX.pwq-TajnDDbzTyVW | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-02-06 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-02-06 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996907 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-06 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered cleanup of term definitions across the three specifications and the start of issue review, and the Kerific browser extension with a planned consensus feature for definitions. Discussion covered a Rebooting the Web of Trust (RWOT) comparison of did:webs and did:webplus and public review of the KERI, ACDC and CESR specifications. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996907 | https://zoom.us/rec/share/IPnKeEWUlvc8iwa9yOlbxGyipSxHupe4KDn9NzbjU-9TQCIVj3Vl4GV708fzUsHR._ww_IC6hJSd4Y9tW | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-02-02 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-02-02 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22990888 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-02-02 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion of the remaining work before final public review added the whois review and clarified that the implementation guide and reference implementation are separate from the specification, with the graph diagram a candidate for the implementation guide. Other items were the normative versus informative breakdown (issue 120), service endpoint section updates and the KERIpy release candidate. Action items included cleaning up informative links and the old bracketing technique and reviewing a first pass at the normative and informative breakdown. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22990888 | https://zoom.us/rec/share/lCRFrO-640OzJGMw8U7rOvki42UXfji1UTGH0vw7JKRrpo-bt_Mxe0q-3a2OdZIJ.b4F5tu1pCJr5lit- | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-01-30 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-01-30 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996956 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-30 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements and reports covered completion of CESR's provisional media type registration with Internet Assigned Numbers Authority (IANA), release candidates of KERIpy (1.1.0), KERIA, SignifyPy and Signify-TS (0.1.0) awaiting feedback, and did:webs work on normative sections and service endpoints. Discussion covered whether KERIpy should go to 2.0.0 (with 2.0.0 reserved for the CESR and KERI 2.0 protocol update), how to find the transaction event log (TEL) of credentials issued by an autonomic identifier (AID) and the lack of standard query APIs, whether issuers may keep a TEL private, and interdependencies between Trust Spanning Protocol (TSP) and KERI implementations. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996956 | https://zoom.us/rec/share/zGKpX6NOopFt3KoF8PuRplvV_Q5R_XKKBlU7JHIwyJ5LboGE6Mbi-gPIWMdiOmA.iMMkIgrtICF_NY2P | Agreed that TEL events should be at least as visible as the credentials they track | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-01-26 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-26 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995004 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-26 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | With the public review period past 30 days and extended until the 1.0 requirements are met, discussion covered how the specification should guide readers through only the KERI features did:webs needs, including updates to the diagram in pull request 124. Remaining items before final review included the normative versus informative breakdown (issue 120), service endpoint section updates, the KERIpy release candidate, and how contributors could help; a participant offered to work through the reference implementation's getting-started guide on an Apple M3 machine. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995004 | https://zoom.us/rec/share/r0Wsw2wtN-EeCO8lr0Evp8A2fSn4Lw9a4zYnc91vVbWe6sGpPLKTFDg1nzceRP58.ELOofmT8_iIhg5MY | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-01-23 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-01-23 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997014 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-23 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted that the Internet Assigned Numbers Authority (IANA) registration had been submitted and that Linux Foundation EasyCLA (contributor license agreement) checks would be applied to all Trust over IP (ToIP) repositories. Reports covered delegation updates and query by seal in KERIA, passing Signify-TS integration scripts including issuance of all verifiable Legal Entity Identifier (vLEI) credential types, did:webs normative and informative edits, the Signify browser extension and 84 open issues across the KERI, ACDC and CESR specifications ahead of a hoped-for public review on February 2. Discussion covered European Banking Authority (EBA) authentication with the vLEI and the browser extension. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997014 | https://zoom.us/rec/share/F_nnkyervO_HrWsOx9StVs4Cfkv7dbSr9WQ7cnuYUdYUy4xWag21nQjuYM79qQDU.EOVq_3f63oJO9n0x | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-01-19 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-19 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998106 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-19 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements noted the Technology Stack Working Group's new mailing list as part of accepting the new Open Web Foundation licensing, and that the public review period had passed 30 days. The ToIP (Trust over IP) specification template was reported, with its latest changes to be adopted into the did:webs repository. Discussion stressed that the specification must make clear what is optional so readers can see where to stop for their use case, and continued the normative versus informative breakdown of the specification. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998106 | https://zoom.us/rec/share/78XvGsQ2f5RX_VLHgD9Kfgd4Q6a2VWsD_bI2erWnJzYJj-LM4_somcesJAPrSMsw.K3krmc4e7JqVmrlW | Public review period extended until the 1.0 specification requirements are complete | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||
| acdc-tf-2024-01-16 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-01-16 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997047 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-16 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered the specifications' migration to the Trust over IP (ToIP) format, did:webs refactoring after its 30-day public review, the Kerific glossary tool and reuse of terminology across specifications, some test regressions in KERIA, KERIpy and Signify-TS, and UML diagrams of the Issuance and Presentation Exchange (IPEX) protocol. Discussion covered recovery rotation rules and logging in with autonomic identifiers (AIDs) and ACDCs through the Signify browser extension, including signed presentations against replay attacks and the European Banking Authority (EBA) proof of concept for signed report submission with a Document Submitter credential. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997047 | https://zoom.us/rec/share/kjVClDaww8Wplx-RCMYrUi4jJHmqGJ3iogLbrGphYhWJWjRc53Ye6326G9YGPZue.UeiOxqrstslEq-fo | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2024-01-12 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-12 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Discussion focused on separating normative from informative material before release (issue 120): working back from the normative statements, keeping informative text to a minimum and moving the rest to an appendix, implementation guide or separate paper, following the ToIP (Trust over IP) specification template. A section-by-section review covered core characteristics, the method name, the method-specific identifier ABNF (Augmented Backus-Naur Form), whether statements about the KERI AID (autonomic identifier) should be normative and reference the KERI specifications, and the point that W3C does not allow non-normative references, so a SCID (self-certifying identifier) might be specified at bare minimum. The state of the Hyperledger Labs reference implementation was also on the agenda. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998030 | https://zoom.us/rec/share/s_IiwW9wOtlXHFfu3AlPy0O28zlvrDT-naKVPNX3DnRlvBGf8WxWr_SOSPt96zY.ZfYeUSPyHJDudA0R?startTime=1705071805000 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-01-09 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-01-09 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994875 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-09 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports noted that the KERI, ACDC and CESR specification content had been migrated to the Trust over IP (ToIP) format with many open issues remaining, that did:webs 1.0 public review was under way, and that the Kerific extension had been released. Discussion covered the timeline for public review of the specifications and recovery rotation rules. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994875 | https://zoom.us/rec/share/3lUsMHAs_8P0G7DL03Ri4OXlOqssugckQSRO_0wnpn0rjlgaWndR887GNE25uLw5.tuQgsSYkXxMo9x2C | Public review of the specifications targeted to start January 19 for two weeks (no objections) | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||
| didwebs-tf-2024-01-05 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2024-01-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994892 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-05 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the Technology Stack Working Group's new mailing list under its new charter, IIW (Internet Identity Workshop) Spring 2024 on April 16 to 18, and a public review period expected to close at the January 19 meeting, following the ToIP (Trust over IP) blog post of December 15 announcing the review. Discussion repeated the public review preparation items: documented review changes, a review issue template, open to-do sections and the 1.0 milestone. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22994892 | https://drive.google.com/file/d/1APixTsCYPrse7rdP4zX8GKhEYoE1VhGC/view?usp=sharing | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2024-01-02 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2024-01-02 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22975085 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2024-01-02 | 2024 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the did:webs specification public review, ending January 15, and the Digital Identity unConference Europe (DICE) conference in Zurich in June 2024. Reports covered protected event channels between controller and witnesses or delegator and delegate in KERIpy, the Signify browser extension, the Kerific browser extension for glossary terms, and formatting the Trust over IP (ToIP) specifications for both HTML and ISO output. Discussion covered how many multisig signers must sign an admit message, a 2024 roadmap to reduce breaking changes across KERIA, the Signify clients and KERIpy, and the delegation validation rules for superseding delegated rotation. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22975085 | https://zoom.us/rec/share/EjJdjqrUPQ6Jqx5C2ekb0VuA4ofBikhBp2Y5NzFc5_OGFNaciTXTsZY9_xQKBEuZ.1Y4izdzESz7o5IlM | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-12-15 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-15 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997177 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-15 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The blog post announcing the public review period was reported as updated, and the task force would not meet again until January 5. Discussion covered what was needed to enter public review: documenting all review changes, a public review issue template modeled on the one used for the vLEI (verifiable Legal Entity Identifier) EGF (Ecosystem Governance Framework) review with a field for the quoted text, resolving open to-do sections, the 1.0 milestone, and an equivalentId and alsoKnownAs pull request to be revised so as not to change the subset and superset relationship. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22997177 | https://zoom.us/rec/share/5BxR88cPQELxp3QgrKdkLWpQ_XGBEViS6zU7T6S7WxErqy4dGGpMK8hSFRu07Zb6.nYdSj3F9tMfdYRZm | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| kerione-eba-publishes-discussion-paper-on-the-centralisation | Articles, press releases and opinion article | EBA publishes discussion paper on the centralisation of EEA banks Pillar 3 disclosures in the EBA Pillar 3 data hub | https://www.eba.europa.eu/publications-and-media/press-releases/eba-publishes-discussion-paper-centralisation-eea-banks | European Banking Authority (EBA) | no change in six to eighteen months; still correct quiet | 2026-10-14 | 2023-12-14 | 2023 | intro | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The European Banking Authority's press release announcing its discussion paper on the Pillar 3 data hub, which would centralize prudential disclosures by European Economic Area banks. It notes that the paper covers the verifiable Legal Entity Identifier (vLEI), developed by GLEIF, as a possible secure way for large institutions to submit data, and invited comments by 29 March 2024. | European Banking Authority (EBA) | keri.one KERI Resources page keri-one-resources | 1 | 0 | |||||||||||||||||||
| kerione-pillar-3-data-hub-processes-and-possible-practical-i | Government and policy policy | Pillar 3 Data Hub Processes and Possible Practical Implications (Discussion Paper EBA/DP/2023/01) | https://www.eba.europa.eu/sites/default/files/2023-12/d5b13b4d-a9dc-4680-8b7c-0a3a4c694fac/Discussion%20paper%20on%20Pillar3%20data%20hub.pdf | European Banking Authority (EBA) | no change in six to eighteen months; still correct quiet | 2026-10-14 | 2023-12-14 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | A 65-page EBA discussion paper on how a central Pillar 3 data hub would receive, transform and publish banks' prudential disclosures. Section 6 presents the vLEI as an EBA use case for regulatory reporting, describing the vLEI trust chain built on KERI and ACDC, a Gartner study and an EBA-GLEIF proof of concept, and the EBA's initial conclusions. It is for readers looking for a regulator's own assessment of the vLEI. | European Banking Authority (EBA) | EBA/DP/2023/01 | keri.one KERI Resources page keri-one-resources | 1 | 0 | ||||||||||||||||||
| acdc-tf-2023-12-12 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2023-12-12 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995827 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-12 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements covered the Cardano Foundation identity wallet and the cancellation of all KERI meetings for the weeks of December 18 to 31. Reports covered a KERIpy discussion of tables for CESR-native KERI and ACDC messages, the KERI specification pushed in revised format, and did:webs public review starting December 15. Discussion reviewed the KERI specification repository, a convention for aliases (LID, a legitimized identifier), and whether CESR would move to protocol version 2.0. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995827 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | ||||||||||||||||||
| didwebs-tf-2023-12-08 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-08 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996410 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-08 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The December 15 target for a 1.0 specification, a Rubric podcast on December 11 and the blog post announcing the public review period were restated. Discussion caught up on the status of final changes: specification versions and dependencies, terminology and KERI fundamentals, the Designated Aliases public schema, the Hyperledger Labs reference implementation, and open pull requests and issues. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996410 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | ||||||||||||||||||
| acdc-tf-2023-12-05 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2023-12-05 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989175 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-05 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered versionable CESR changes and new CESR codes merged into KERIpy, a KERIA fix for granting chained credentials, Signify-TS test and lint upgrades, did:webs unit testing of designated aliases toward a specification target of December 15, KERI Suite Search Engine (KERISSE) terminology syncing, and a new Signify browser extension. Discussion covered the CESR upgrades. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22989175 | https://zoom.us/rec/share/TitxaCYttUN0uQOFK00wm3cg62PTZteBoV6cNXIxy5lQXsphBKPr5ONeTjWH3J4K.LVWB7DUxkMG1DR2z | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-12-01 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-12-01 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993607 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-12-01 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | The December 15 target for a 1.0 specification and the planned public review period, to be announced by blog post, were restated. Discussion covered terminology and KERI fundamentals, the Designated Aliases public schema, reference implementation work in the Hyperledger Labs did-webs-resolver, and open pull requests and issues. Action items included reviewing the IIW (Internet Identity Workshop) tutorial pull request and migrating that tutorial to Hyperledger Labs as a "did:webs Getting Started" guide. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22993607 | https://zoom.us/rec/share/_fXJAg_svEwHDZpCWwacdcLP_TFNjkLkfGtlKmLYIN-hLZyIsBSAC6agijaIMw4.YHOWnpzxloLKVcca | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2023-11-28 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2023-11-28 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996819 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-28 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered a restructured secure privacy, authenticity and confidentiality (SPAC) paper for the Trust Spanning Protocol, naming the client-server protocol Signify, a pull request for granting chained credentials, draft codes for CESR 1.1, further specification pull requests and a KERISSE (KERI Suite Search Engine) feedback questionnaire. Discussion covered why KERI, having no shared secrets, resists phishing better than password, bearer-token and Diffie-Hellman based approaches, how verifiable Legal Entity Identifier (vLEI) role credentials leave the semantics of authority to an ecosystem governance framework, and how autonomic identifier (AID) delegation differs from ACDC delegation. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22996819 | https://zoom.us/rec/share/QG58UBb7b_WaDSXFb8DNlsdn3cb-EXg_UPVXtz5CXxjIUVneCz2jToyxjKQY5wYB.GpRB3SuJgC6PPSz9 | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-11-17 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-11-17 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995690 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-17 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements kept the December 15 target for a 1.0 specification, noted a Rubric podcast on December 11 and a BC Government did:webs VDR (verifiable data registry) registrar and resolver for Aries agents. The blog post was to be changed to announce a public review period starting with the December 15 completion, ahead of the December 13 all-members call. Discussion covered the Designated Aliases public schema and its example script. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995690 | https://zoom.us/rec/share/L7CZ3st7lzxwZAhK_JlNIxGxYRAfGpL0KEpfBpFKZMxIYFmGayqvgTVtO4gZ_rrx.qgZe4uRQ3X_B7g27 | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 | |||||||||||||||||
| acdc-tf-2023-11-14 | Meetings (one per entry) meeting | ACDC Task Force meeting, 2023-11-14 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998531 | Trust over IP (ACDC Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-14 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Reports covered KERIpy pull requests and scripts for migrating between code versions and moving a group multisig autonomic identifier (AID) to participants in KERIA, matching fixes in SignifyPy, KERIA and Signify-TS, a did:webs ACDC for declaring authorized identifiers, and loading the Slack history into KERISSE (KERI Suite Search Engine). Discussion reviewed the migration scripts, KERI key management for organizational use cases, and how to create an Issuance and Presentation Exchange (IPEX) message for a presentation. | acdc-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22998531 | https://zoom.us/rec/share/YHlXoSBmDnoZ2e5bXVmcEUj48hkZs2OrUchiaLUiEVOuRqJb3MSb9gYm7QiJlEpk.AHpmT-bkKNykm2mk | ToIP ACDC (Authentic Chained Data Container) Task Force acdc-task-force | 1 | 0 | |||||||||||||||||
| didwebs-tf-2023-11-10 | Meetings (one per entry) meeting | did:webs Task Force meeting, 2023-11-10 | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995707 | Trust over IP (did:webs Task Force) | no change in six to eighteen months; still correct quiet | 2026-10-15 | 2023-11-10 | 2023 | practitioner | a statute, a regulator's document, or a standards body's own page official | anyone with the link public | Announcements set a target of a 1.0 specification by December 15 and noted a did:webs VDR (verifiable data registry) registrar and resolver for Aries agents. Switchchord demonstrated a music-industry copyright management system that issues credentials to songwriters and publishers, currently on did:web with a planned move toward something like did:webs. Discussion proposed an authorized identifier list for secure rich discovery, under which equivalentId, redirection and authorized domains are satisfied by authorized did:webs identifiers and alsoKnownAs covers other DIDs (decentralized identifiers), and asked whether resolution must fail when that metadata is absent. | didwebs-task-force | https://lf-toip.atlassian.net/wiki/spaces/HOME/pages/22995707 | https://zoom.us/rec/share/CEasFYFDhwZlTx7j03YGIjsiy1eUfnkjcFMaFvopBJN8Limitn9qccupTZf4pHUA.ll7dSHAa1NtVO6tT | ToIP did:webs Method Task Force didwebs-task-force | 1 | 0 |
Advanced export
JSON shape: default, array, newline-delimited, object
CREATE TABLE resources (id TEXT PRIMARY KEY, type TEXT REFERENCES types(id), name TEXT, url TEXT, maintainer TEXT,
status TEXT REFERENCES statuses(id), last_checked TEXT, date TEXT, year INTEGER, level TEXT REFERENCES levels(id),
evidence TEXT REFERENCES evidence(id), access TEXT REFERENCES access(id), abstract TEXT, authors TEXT, series TEXT,
chair TEXT, minutes TEXT, recording TEXT, media TEXT, decisions TEXT, version TEXT, language TEXT, license TEXT,
release TEXT, pushed TEXT, depends TEXT, since TEXT, via TEXT REFERENCES resources(id),
summary TEXT REFERENCES notes(path), note TEXT, has_abstract INTEGER, has_summary INTEGER,
kind TEXT REFERENCES kinds(id), sector TEXT REFERENCES sectors(id), country TEXT, products TEXT);