diff --git a/Gemfile.lock b/Gemfile.lock
index 5b4ac6e6..a7e96268 100644
--- a/Gemfile.lock
+++ b/Gemfile.lock
@@ -60,8 +60,8 @@ GEM
rb-fsevent (0.11.2)
rb-inotify (0.11.1)
ffi (~> 1.0)
- rexml (3.2.8)
- strscan (>= 3.0.9)
+ rexml (3.3.6)
+ strscan
rouge (4.2.1)
rubyzip (2.3.2)
safe_yaml (1.0.5)
diff --git a/guidelines/maintainer-diversity-best-practices.md b/guidelines/maintainer-diversity-best-practices.md
new file mode 100644
index 00000000..d1c64954
--- /dev/null
+++ b/guidelines/maintainer-diversity-best-practices.md
@@ -0,0 +1,107 @@
+---
+layout: default
+title: Maintainer Diversity Best Practices
+parent: Guidelines
+grand_parent: Hyperledger TOC
+nav_order: 2
+---
+# Maintainer Diversity Best Practices
+
+The following is a set of items that can help in increasing maintainer diversity for projects. If there are any questions on how to implement these practices, please reach out to the community architects or the TOC. Also, if you have additional items that have helped your project increase your maintainer diversity, please feel free to file a PR to add those items.
+
+## Welcoming Environment
+
+- See [video on creating a welcoming community](https://www.youtube.com/watch?v=lHOINFlb9JA)
+- Encourage Collaboration
+- Constructive Feedback
+- Recognize Contributions
+ - SWAG
+ - Public Recognition
+ - Contributor Spotlights
+ - Celebrate Milestones
+ - Badging
+- Distribute Responsibilities
+- Empower Contributors
+- Delegate Tasks
+ - Issue Manager
+ - FAQ Manager
+ - Writing Documentation
+ - Reviewing Pull Requests
+- Community Building
+ - Pair Programming Sessions
+ - Contributor Office Hours
+- Retesting Landing Process for New Users
+- How to Retain Maintainers
+
+## Improving Processes
+
+- Have all meetings in the open (including standups)
+ - Consider rotating meeting times to accommodate different time zones.
+- Document Everything
+ - Decision Making Process
+ - Decisions
+- Have all discussions publicly
+- Code Quality
+- CI/CD Pipelines
+- Local Testing
+- Pull Requests
+ - Doing pull requests quickly
+ - Easy pull request workflows
+ - FIFO is important
+ - Responding within a short time frame even if you are not going to look at it immediately
+ - Invest in finding contributors / maintainers
+ - Work with the Hyperledger staff on ways to reach out to the larger community
+
+## Documentation
+
+- Maintainers Guide
+ - Procedure for becoming a maintainer
+ - Duties of a maintainer
+ - Paths for contributors to become maintainers
+ - Transparent decision making process
+ - Criteria and expectations for becoming a maintainer
+ - Alignment to community values
+ - Technical Proficiency
+ - Understand project goals
+- Contribution Guide
+ - Requirements for contributing
+ - Local development environment setup instructions
+ - Code style guidelines
+ - Testing procedures and requirements
+ - Why contributing makes sense
+ - Convincing your management that contributing makes sense
+ - Continue to contribute after leaving a company
+- Producing Video Content
+- Translation / Localization
+
+## Places to Find New Maintainers
+
+- Existing Contributors
+ - Enthusiastic
+ - Consistent contributions
+- Learning Opportunities
+ - Mentorship program
+ - Workshops
+ - Webinars
+ - Meetups
+ - Documentation sprints
+ - Events
+ - Conferences
+- New Contributors
+ - Good first issues
+ - Provide details and suggested directions for solution
+ - Hactoberfest
+ - Frequent users
+- Researchers
+- Consultancies and Service Providers
+- Vendors of Commercial Offerings
+ - Convey value
+- Non-coders
+ - Not all maintainers are coders
+ - Issue manager
+ - FAQ manager
+ - Translation manager
+ - Documentation manager
+ - Pull Request manager
+ - Release manager
+- See [Raising the Profile of your Project or Lab](https://docs.google.com/presentation/d/13nji_R-op77ERT-AV3-CbOOZwAOjtvq33RRGnjpL3Gc/edit)
diff --git a/meeting-minutes/0000-template.md b/meeting-minutes/0000-template.md
index e7ca7573..68684095 100644
--- a/meeting-minutes/0000-template.md
+++ b/meeting-minutes/0000-template.md
@@ -44,10 +44,10 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
-[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
+[Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Attended by
diff --git a/meeting-minutes/2024/2024-02-22-TOC-meeting-record.md b/meeting-minutes/2024/2024-02-22-TOC-meeting-record.md
index 9794bdc6..70362a6c 100644
--- a/meeting-minutes/2024/2024-02-22-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-02-22-TOC-meeting-record.md
@@ -34,7 +34,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
* [2024 Annual Review Hyperledger Iroha](https://github.com/hyperledger/toc/pull/214) -- Stephen (Primary), David (Secondary)
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-03-14-TOC-meeting-record.md b/meeting-minutes/2024/2024-03-14-TOC-meeting-record.md
index 5c4d1b70..0a14cc88 100644
--- a/meeting-minutes/2024/2024-03-14-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-03-14-TOC-meeting-record.md
@@ -33,7 +33,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
* [TOC Pull Request Review](https://github.com/hyperledger/toc/pulls)
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
* [Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-03-21-TOC-meeting-record.md b/meeting-minutes/2024/2024-03-21-TOC-meeting-record.md
index ed27654c..b678e1b3 100644
--- a/meeting-minutes/2024/2024-03-21-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-03-21-TOC-meeting-record.md
@@ -38,7 +38,7 @@ Details: [Zero Knowledge Proofs and ZK Programming in Blockchain Application Dev
* [2024 Annual Review Hyperledger FireFly](https://github.com/hyperledger/toc/pull/222) -- Tracy (Primary), Dave (Secondary)
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-03-28-TOC-meeting-record.md b/meeting-minutes/2024/2024-03-28-TOC-meeting-record.md
index 0b192b66..53591924 100644
--- a/meeting-minutes/2024/2024-03-28-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-03-28-TOC-meeting-record.md
@@ -39,7 +39,7 @@ Details: [https://docs.google.com/document/d/1Gkd-V17tAYQFI4ymtIGUjfQxBlgOYVj0WB
* [2024 Annual Review Hyperledger Solang](https://github.com/hyperledger/toc/pull/228) -- Yacov (Primary), Peter (Secondary)
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-04-04-TOC-meeting-record.md b/meeting-minutes/2024/2024-04-04-TOC-meeting-record.md
index 6888062a..9a858fed 100644
--- a/meeting-minutes/2024/2024-04-04-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-04-04-TOC-meeting-record.md
@@ -33,7 +33,7 @@ Details: [https://docs.google.com/document/d/1Gkd-V17tAYQFI4ymtIGUjfQxBlgOYVj0WB
* Approved by a role call vote; eight aye, three not present.
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-04-11-TOC-meeting-record.md b/meeting-minutes/2024/2024-04-11-TOC-meeting-record.md
index 3a12bf90..6a97716f 100644
--- a/meeting-minutes/2024/2024-04-11-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-04-11-TOC-meeting-record.md
@@ -33,7 +33,7 @@ Details: [Zero Knowledge Proofs and ZK Programming in Blockchain Application Dev
* [2024 Annual Review Hyperledger Caliper](https://github.com/hyperledger/toc/pull/235) - Arun (Primary), Jim (Secondary)
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-04-18-TOC-meeting-record.md b/meeting-minutes/2024/2024-04-18-TOC-meeting-record.md
index 056d0660..ae177403 100644
--- a/meeting-minutes/2024/2024-04-18-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-04-18-TOC-meeting-record.md
@@ -39,7 +39,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-04-25-TOC-meeting-record.md b/meeting-minutes/2024/2024-04-25-TOC-meeting-record.md
index cdf6eee7..1d99eb68 100644
--- a/meeting-minutes/2024/2024-04-25-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-04-25-TOC-meeting-record.md
@@ -33,7 +33,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-05-02-TOC-meeting-record.md b/meeting-minutes/2024/2024-05-02-TOC-meeting-record.md
index 5d5bb8d8..23da5582 100644
--- a/meeting-minutes/2024/2024-05-02-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-05-02-TOC-meeting-record.md
@@ -33,7 +33,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
# Recordings
-* [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+* [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-05-16-TOC-meeting-record.md b/meeting-minutes/2024/2024-05-16-TOC-meeting-record.md
index 0bc54662..ff02315b 100644
--- a/meeting-minutes/2024/2024-05-16-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-05-16-TOC-meeting-record.md
@@ -35,7 +35,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
- [OpenSSF Scorecard Task Force](https://docs.google.com/presentation/d/18zO30diSW1jUfQwoglWza0Lx2_Q8vwuE__q-JdoC3ho/edit?usp=sharing)
# Recordings
-- [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-05-23-TOC-meeting-record.md b/meeting-minutes/2024/2024-05-23-TOC-meeting-record.md
index 0d932b9c..033794c8 100644
--- a/meeting-minutes/2024/2024-05-23-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-05-23-TOC-meeting-record.md
@@ -38,7 +38,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
- Task Force: Video Series
# Recordings
-- [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-05-30-TOC-meeting-record.md b/meeting-minutes/2024/2024-05-30-TOC-meeting-record.md
index a143d2c1..518a8f53 100644
--- a/meeting-minutes/2024/2024-05-30-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-05-30-TOC-meeting-record.md
@@ -29,7 +29,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
- [Automated Pipeline Best Practices Task Force discussion](https://github.com/hyperledger/toc/pull/252)
# Recordings
-- [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-06-06-TOC-meeting-record.md b/meeting-minutes/2024/2024-06-06-TOC-meeting-record.md
index 65cee4fa..4ab48aee 100644
--- a/meeting-minutes/2024/2024-06-06-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-06-06-TOC-meeting-record.md
@@ -31,7 +31,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
Task force discussion: Badging Lifecycle
# Recordings
-- [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-06-13-TOC-meeting-record.md b/meeting-minutes/2024/2024-06-13-TOC-meeting-record.md
index d15f664b..f907951f 100644
--- a/meeting-minutes/2024/2024-06-13-TOC-meeting-record.md
+++ b/meeting-minutes/2024/2024-06-13-TOC-meeting-record.md
@@ -35,7 +35,7 @@ Hyperledger is committed to creating a safe and welcoming community for all. For
- Task force discussion: Security Artifact Signing
# Recordings
-- [Recordings are available on your Open Profile page](https://openprofile.dev/my-meetings) under Past Meetings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
# Upcoming TOC meetings
[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
diff --git a/meeting-minutes/2024/2024-06-20-TOC-meeting-record.md b/meeting-minutes/2024/2024-06-20-TOC-meeting-record.md
new file mode 100644
index 00000000..8fd6b049
--- /dev/null
+++ b/meeting-minutes/2024/2024-06-20-TOC-meeting-record.md
@@ -0,0 +1,53 @@
+---
+layout: default
+title: 2024-06-20 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+- Cancel July 4 meeting
+
+# Quarterly reports
+- [2024 Q2 Hyperledger Cello](https://github.com/hyperledger/toc/pull/259)
+- [2024 Q2 Hyperledger Firefly](https://github.com/hyperledger/toc/pull/262)
+- [2024 Q2 Hyperledger Solang](https://github.com/hyperledger/toc/pull/263)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q2 Hyperledger Besu (due June 20, 2024)
+- 2024 Q2 Hyperledger Caliper (due June 20, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- New project proposal: [xkey](https://github.com/hyperledger/hyperledger-hip/pull/18)
+ - Approved, eight aye, one nay
+- Preview of upcoming changes - Hart
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+- Task force discussion: Security Artifact Signing (next week)
+[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [ ] ~~Stephen Curran~~
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [x] Yacov Manevich
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [x] Conor Svensson
+- [x] Jim Zhang
diff --git a/meeting-minutes/2024/2024-06-27-TOC-meeting-record.md b/meeting-minutes/2024/2024-06-27-TOC-meeting-record.md
new file mode 100644
index 00000000..71ad5814
--- /dev/null
+++ b/meeting-minutes/2024/2024-06-27-TOC-meeting-record.md
@@ -0,0 +1,55 @@
+---
+layout: default
+title: 2024-06-27 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+- In recognition of the growing market for and adoption of decentralized technologies, the Linux Foundation announced plans to form [LF Decentralized Trust](https://www.linuxfoundation.org/press/linux-foundation-announces-intent-to-form-lf-decentralized-trust).
+- Reminder: The July 4th, 2024 meeting is canceled.
+
+# Quarterly reports
+- [2024 Q2 Hyperledger Firefly](https://github.com/hyperledger/toc/pull/262)
+- [2024 Q2 Hyperledger Solang](https://github.com/hyperledger/toc/pull/263)
+- 2024 Q2 Hyperledger Besu (due June 20, 2024)
+- 2024 Q2 Hyperledger Caliper (due June 20, 2024)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+- Hyperledger Labs Q2 Report
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Cacti (due July 11, 2024)
+- 2024 Q3 Hyperledger Fabric (due July 11, 2024)
+- 2024 Q3 Hyperledger Identus (due July 11, 2024)
+- 2024 Q3 Hyperledger Web3j (due July 11, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- Task force discussion: Security Artifact Signing
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [x] Stephen Curran
+- [ ] ~~David Enyeart~~
+- [ ] ~~Tracy Kuhrt~~
+- [x] Yacov Manevich
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [ ] ~~Peter Somogyvari~~
+- [x] Conor Svensson
+- [x] Jim Zhang
diff --git a/meeting-minutes/2024/2024-07-11-TOC-meeting-record.md b/meeting-minutes/2024/2024-07-11-TOC-meeting-record.md
new file mode 100644
index 00000000..0e723af3
--- /dev/null
+++ b/meeting-minutes/2024/2024-07-11-TOC-meeting-record.md
@@ -0,0 +1,71 @@
+---
+layout: default
+title: 2024-07-11 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+
+# Quarterly reports
+- [2024 Q2 Hyperledger Besu](https://github.com/hyperledger/toc/pull/267)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Past due reports
+- 2024 Q2 Hyperledger Caliper (due June 20, 2024)
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Cacti (due July 11, 2024)
+- 2024 Q3 Hyperledger Fabric (due July 11, 2024)
+- [2024 Q3 Hyperledger Identus](https://github.com/hyperledger/toc/pull/271) (due July 11, 2024)
+- 2024 Q3 Hyperledger Web3j (due July 11, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- Preparation for LF Decentralized Trust
+ - Project charters (reviewed the [Hyperledger Cacti example](https://docs.google.com/document/d/18zvrwNGDXyh9ewKPSoCMZUfbGhSQ0XRfpI80N6SZ9gM/edit))
+ - [Governing Documents](https://toc.hyperledger.org/governing-documents/) - Volunteers to review and see which need to be changed
+ - Hyperledger Foundation Allowed Third Party Licenses - Jim
+ - Project Lifecycle - Jim
+ - Project Annual Review - Stephen
+ - Project Incubation Exit Criteria - Tracy
+ - Project Updates - Marcus
+ - Maintainer and Repository Inactivity - Arun
+ - Release Taxonomy - Peter
+ - Security Policy - Tracy
+
+ - [Guidelines](https://toc.hyperledger.org/guidelines/) - Determine which, if any, should be considered governing documents instead of guidelines
+ - Common Repository Structure - Move to Governance - Rama
+ - MAINTAINERS Guidelines - Move to Governance - Rama
+ - Project Incubation Entry Considerations - Leave as Guideline - Yacov
+ - Project Best Practices - Leave as Guideline - Dave
+ - Raising an Issue - Move to higher level - Tracy
+ - Task Force - Move to Governance - Conor
+ - GitHub Contribution Guide - Leave as Guideline - Dave
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [x] Stephen Curran
+- [ ] ~~David Enyeart~~
+- [x] Tracy Kuhrt
+- [ ] ~~Yacov Manevich~~
+- [ ] ~~Matt Nelson~~
+- [ ] ~~Venkatraman Ramakrishna~~
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [ ] ~~Conor Svensson~~
+- [x] Jim Zhang
diff --git a/meeting-minutes/2024/2024-07-18-TOC-meeting-record.md b/meeting-minutes/2024/2024-07-18-TOC-meeting-record.md
new file mode 100644
index 00000000..5072e779
--- /dev/null
+++ b/meeting-minutes/2024/2024-07-18-TOC-meeting-record.md
@@ -0,0 +1,52 @@
+---
+layout: default
+title: 2024-07-18 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+
+# Quarterly reports
+- [2024 Q2 Hyperledger Caliper](https://github.com/hyperledger/toc/pull/274) (due June 20, 2024)
+- [2024 Q2 Hyperledger Besu](https://github.com/hyperledger/toc/pull/267)
+- [2024 Q3 Hyperledger Identus](https://github.com/hyperledger/toc/pull/271)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Cacti (due July 11, 2024)
+- 2024 Q3 Hyperledger Fabric (due July 11, 2024)
+- 2024 Q3 Hyperledger Web3j (due July 11, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- CommunityOne Bot - Fay - Move to next week
+- Lab Q2 Quarterly Report - Alvaro
+- Task Force: Maintainer Diversity Best Practices (PR: https://github.com/hyperledger/toc/pull/272)
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+[Please check the calendar](https://lists.hyperledger.org/g/toc/calendar)
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [ ] ~~Stephen Curran~~
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [ ] ~~Yacov Manevich~~
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [x] Conor Svensson
+- [ ] ~~Jim Zhang~~
diff --git a/meeting-minutes/2024/2024-07-25-TOC-meeting-record.md b/meeting-minutes/2024/2024-07-25-TOC-meeting-record.md
new file mode 100644
index 00000000..68084929
--- /dev/null
+++ b/meeting-minutes/2024/2024-07-25-TOC-meeting-record.md
@@ -0,0 +1,55 @@
+---
+layout: default
+title: 2024-07-25 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024)
+
+# Quarterly reports
+- [2024 Q2 Hyperledger Caliper](https://github.com/hyperledger/toc/pull/274)
+- [2024 Q3 Hyperledger Identus](https://github.com/hyperledger/toc/pull/271)
+- [2024 Q3 Hyperledger Web3j](https://github.com/hyperledger/toc/pull/275)
+- [2024 Q3 Hyperledger Cacti](https://github.com/hyperledger/toc/pull/277)
+- [2024 Q3 Hyperledger Fabric](https://github.com/hyperledger/toc/pull/278)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Aries (due August 1, 2024)
+- 2024 Q3 Hyperledger AnonCreds (due August 1, 2024)
+- 2024 Q3 Hyperledger Indy (due August 1, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- [CommunityOne Bot](https://communityone.io/) - Fay
+- [Infrastructure changes for LF Decentralized Trust](https://docs.google.com/document/d/1E3cYIGIckXyI2h74Ee7_DCxi48PQmJ38rCnbnSZ9Clg/edit)
+- Task force: OpenSSF Scorecard
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+[Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [x] Stephen Curran
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [x] Yacov Manevich
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [ ] ~~Conor Svensson~~
+- [x] Jim Zhang
diff --git a/meeting-minutes/2024/2024-08-01-TOC-meeting-record.md b/meeting-minutes/2024/2024-08-01-TOC-meeting-record.md
new file mode 100644
index 00000000..e0304713
--- /dev/null
+++ b/meeting-minutes/2024/2024-08-01-TOC-meeting-record.md
@@ -0,0 +1,53 @@
+---
+layout: default
+title: 2024-08-01 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024)
+- Please review [Maintainer Diversity Best Practices PR](https://github.com/hyperledger/toc/pull/272)
+
+# Quarterly reports
+- [2024 Q3 Hyperledger Cacti](https://github.com/hyperledger/toc/pull/277)
+- [2024 Q3 Hyperledger Fabric](https://github.com/hyperledger/toc/pull/278)
+- [2024 Q3 Hyperledger Indy](https://github.com/hyperledger/toc/pull/279)
+- [2024 Q3 Hyperledger Aries](https://github.com/hyperledger/toc/pull/281)
+- [2024 Q3 Hyperledger AnonCreds](https://github.com/hyperledger/toc/pull/282)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Iroha (due August 8, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- [Infrastructure changes for LF Decentralized Trust](https://docs.google.com/document/d/1E3cYIGIckXyI2h74Ee7_DCxi48PQmJ38rCnbnSZ9Clg/edit)
+- Task force: Video Series
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+[Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Attended by
+
+- [ ] ~~Marcus Brandenburger~~
+- [x] Stephen Curran
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [ ] ~~Yacov Manevich~~
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [ ] ~~Conor Svensson~~
+- [ ] ~~Jim Zhang~~
diff --git a/meeting-minutes/2024/2024-08-08-TOC-meeting-record.md b/meeting-minutes/2024/2024-08-08-TOC-meeting-record.md
new file mode 100644
index 00000000..45da5955
--- /dev/null
+++ b/meeting-minutes/2024/2024-08-08-TOC-meeting-record.md
@@ -0,0 +1,63 @@
+---
+layout: default
+title: 2024-08-08 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html)
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024)
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024)
+- Please review [Maintainer Diversity Best Practices PR](https://github.com/hyperledger/toc/pull/272)
+
+# Quarterly reports
+- [2024 Q3 Hyperledger Cacti](https://github.com/hyperledger/toc/pull/277)
+- [2024 Q3 Hyperledger Fabric](https://github.com/hyperledger/toc/pull/278)
+- [2024 Q3 Hyperledger Indy](https://github.com/hyperledger/toc/pull/279)
+- [2024 Q3 Hyperledger Aries](https://github.com/hyperledger/toc/pull/281)
+- [2024 Q3 Hyperledger AnonCreds](https://github.com/hyperledger/toc/pull/282)
+- [2024 Q3 Hyperledger Iroha](https://github.com/hyperledger/toc/pull/285)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Bevel (due August 15, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- LF Decentralized Trust Infrastructure Sequencing
+ - Wiki
+ - Discord
+ - Mailing lists
+ - Community calls
+ - GitHub
+- Task force: Video Series
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+- [Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+- Task forces discussions:
+ - Automated Pipeline Best Practices
+ - Badging Lifecycle
+ - Security Artifact Signing
+
+# Attended by
+
+- [ ] ~~Marcus Brandenburger~~
+- [ ] ~~Stephen Curran~~
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [ ] ~~Yacov Manevich~~
+- [ ] ~~Matt Nelson~~
+- [x] Venkatraman Ramakrishna
+- [ ] ~~Arun S M~~
+- [x] Peter Somogyvari
+- [ ] ~~Conor Svensson~~
+- [ ] ~~Jim Zhang~~
diff --git a/meeting-minutes/2024/2024-08-15-TOC-meeting-record.md b/meeting-minutes/2024/2024-08-15-TOC-meeting-record.md
new file mode 100644
index 00000000..d887747a
--- /dev/null
+++ b/meeting-minutes/2024/2024-08-15-TOC-meeting-record.md
@@ -0,0 +1,57 @@
+---
+layout: default
+title: 2024-08-15 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html).
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024).
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024).
+- Please review [Maintainer Diversity Best Practices PR](https://github.com/hyperledger/toc/pull/272).
+
+# Quarterly reports
+- [2024 Q3 Hyperledger Indy](https://github.com/hyperledger/toc/pull/279)
+- [2024 Q3 Hyperledger Aries](https://github.com/hyperledger/toc/pull/281)
+- [2024 Q3 Hyperledger AnonCreds](https://github.com/hyperledger/toc/pull/282)
+- [2024 Q3 Hyperledger Iroha](https://github.com/hyperledger/toc/pull/285)
+- [2024 Q3 Hyperledger Bevel](https://github.com/hyperledger/toc/pull/286)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Solang (due August 22, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- Proposal to move [Hedera's core network software suite to LFDT](https://github.com/hyperledger/hyperledger-hip/pull/20).
+- Review open questions observed during Hyperledger TOC to LFDT TAC governance document update.
+- Task force: Badging Lifecycle.
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+- [Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+- Task forces discussions:
+ - Automated Pipeline Best Practices
+ - Security Artifact Signing
+
+# Attended by
+
+- [ ] Marcus Brandenburger
+- [ ] Stephen Curran
+- [ ] David Enyeart
+- [ ] Tracy Kuhrt
+- [ ] Yacov Manevich
+- [ ] Matt Nelson
+- [ ] Venkatraman Ramakrishna
+- [ ] Arun S M
+- [ ] Peter Somogyvari
+- [ ] Conor Svensson
+- [ ] Jim Zhang
diff --git a/meeting-minutes/2024/2024-08-22-TOC-meeting-record.md b/meeting-minutes/2024/2024-08-22-TOC-meeting-record.md
new file mode 100644
index 00000000..65132fc9
--- /dev/null
+++ b/meeting-minutes/2024/2024-08-22-TOC-meeting-record.md
@@ -0,0 +1,59 @@
+---
+layout: default
+title: 2024-08-22 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+nav_exclude: true
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html).
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024).
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024).
+- Please review [Maintainer Diversity Best Practices PR](https://github.com/hyperledger/toc/pull/272).
+
+# Quarterly reports
+- [2024 Q3 Hyperledger Indy](https://github.com/hyperledger/toc/pull/279)
+- [2024 Q3 Hyperledger Aries](https://github.com/hyperledger/toc/pull/281)
+- [2024 Q3 Hyperledger AnonCreds](https://github.com/hyperledger/toc/pull/282)
+- [2024 Q3 Hyperledger Iroha](https://github.com/hyperledger/toc/pull/285)
+- [2024 Q3 Hyperledger Bevel](https://github.com/hyperledger/toc/pull/286)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Solang (due August 22, 2024)
+- 2024 Q3 Hyperledger Cello (due August 29, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- Project Proposal: [Move Hedera Core Network Software to LFDT](https://github.com/hyperledger/hyperledger-hip/pull/20)
+ - Proposal was approved via roll call vote; 10 aye, 1 absent
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+- [Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+- LFDT Governance and Guidelines documents
+- Task forces discussions:
+ - Badging Lifecycle
+ - Automated Pipeline Best Practices
+ - Security Artifact Signing
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [x] Stephen Curran
+- [x] David Enyeart
+- [x] Tracy Kuhrt
+- [ ] ~~Yacov Manevich~~
+- [x] Matt Nelson
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [x] Conor Svensson
+- [x] Jim Zhang
diff --git a/meeting-minutes/2024/2024-08-29-TOC-meeting-record.md b/meeting-minutes/2024/2024-08-29-TOC-meeting-record.md
new file mode 100644
index 00000000..a48fff25
--- /dev/null
+++ b/meeting-minutes/2024/2024-08-29-TOC-meeting-record.md
@@ -0,0 +1,55 @@
+---
+layout: default
+title: 2024-08-29 TOC Meeting Record
+parent: 2024
+grand_parent: Meeting Minutes
+---
+
+
+
+
+Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit our Code of Conduct: [Hyperledger Code of Conduct](https://toc.hyperledger.org/governing-documents/code-of-conduct.html).
+
+# Announcements
+- The [Hyperledger /dev/weekly developer newsletter](https://wiki.hyperledger.org/pages/viewpage.action?pageId=39618905) goes out each Friday to hundreds of Hyperledger developers. It is a collaborative effort. If you have a project release, pull request, community event, and/or relevant article you would like highlighted next week, please [leave a comment for consideration on the upcoming newsletter wiki page](https://wiki.hyperledger.org/display/DR/2024).
+- Maintainer Days / Member Summit 2024: Find out more here: [https://www.hyperledger.org/hyperledger-member-summit-2024](https://www.hyperledger.org/hyperledger-member-summit-2024).
+- Please review [Maintainer Diversity Best Practices PR](https://github.com/hyperledger/toc/pull/272).
+
+# Quarterly reports
+- [2024 Q3 Hyperledger Aries](https://github.com/hyperledger/toc/pull/281)
+- [2024 Q3 Hyperledger AnonCreds](https://github.com/hyperledger/toc/pull/282)
+- [2024 Q3 Hyperledger Bevel](https://github.com/hyperledger/toc/pull/286)
+- 2024 Q3 Hyperledger Solang (Overdue August 22, 2024)
+- Please review any [outstanding quarterly reports](https://github.com/hyperledger/toc/pulls?q=is%3Apr+is%3Aopen+label%3Aquarterly-report+user-review-requested%3A%40me).
+
+# Upcoming reports
+- 2024 Q3 Hyperledger Cello (due August 29, 2024)
+- 2024 Q3 Hyperledger Firefly (due September 05, 2024)
+- [2024 TOC Project Update Calendar](../../project-reports/2024/2024-updates.md)
+
+# Discussion
+- LFDT Governance and Guidelines documents
+
+# Recordings
+- [Recordings are available on the Hyperledger calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+
+# Upcoming TOC meetings
+- [Please check the calendar](https://zoom-lfx.platform.linuxfoundation.org/meetings/lf-decentralized-trust)
+- Task forces discussions:
+ - Badging Lifecycle
+ - Automated Pipeline Best Practices
+ - Security Artifact Signing
+
+# Attended by
+
+- [x] Marcus Brandenburger
+- [x] Stephen Curran
+- [x] David Enyeart
+- [ ] ~~Tracy Kuhrt~~
+- [ ] Yacov Manevich
+- [ ] Matt Nelson
+- [x] Venkatraman Ramakrishna
+- [x] Arun S M
+- [x] Peter Somogyvari
+- [x] Conor Svensson
+- [x] Jim Zhang
diff --git a/project-reports/2024/2024-Q2-Hyperledger-Besu.md b/project-reports/2024/2024-Q2-Hyperledger-Besu.md
new file mode 100644
index 00000000..b7b67e0c
--- /dev/null
+++ b/project-reports/2024/2024-Q2-Hyperledger-Besu.md
@@ -0,0 +1,48 @@
+---
+layout: default
+title: 2024 Q2 Hyperledger Besu
+parent: 2024
+grand_parent: Project Updates
+---
+
+# Project Health
+
+The Besu project is doing quite well these days. There is significant interest around public blockchain networks and private chains. This includes a number of L2s that are looking to use Besu in their infrastructure, as well as more and more publicity around the public/private feature parity work (and new contributions). Community interest in Discord is up, contribution numbers are up, engagement by existing contributors and maintainers looks a lot more collaborative than it used to. Overall health is quite good. The #besu-enterprise channel has also helped funnel a lot of new traffic and interest around private networks to the right folks for support. Discord support overall remains strong and engagement with maintainers and the docs is looking strong.
+
+# Questions/Issues for the TOC
+
+None right now.
+
+# Releases
+
+We had several issues with releases this quarter. This was due to the switch over to a new Github Actions-based release process, and the last removal of CircleCI. There have been a lot of headaches with processes on the GH side and it has become burdensome to deal with Github, besu-native, and other parts of the release. The Consensys team primarily handles releases, and may prepare a post-mortem.
+
+We did release several strong releases this quarter, however.
+
+- 24.5.1
+- 24.5.2
+- 24.6.0
+
+These releases brought some high impact features like substantial peering performance improvements, block processing improvements, logging and other fixes, and RPC improvements. We also shipped SnapSync as a Server to allow Besu nodes to serve data to their peers over the Snap protocol. A big win for the health of Ethereum Mainnet and (eventually) for private networks.
+
+# Overall Activity in the Past Quarter
+
+Chat channels stay very active. Maintainers and devs are helping each other support users, node operators, and more. Some security issues have come in and been patched.
+
+This quarter, maintainers were primarily focused on the Prague hardfork, addressing peering/sync issues and technical debt, shoring up performance, and shipping Snap Server. We are attempting to clear technical debt for a jam-packed 2H roadmap and delivery schedule, aligned around EOF and the Prague Fork, as well as finishing up the Public/Private network feature parity work and shipping a Bonsai Archive solution.
+
+# Current Plans
+
+In the coming quarter we plan to continue to chip away at technical debt and modularity work. We also plan on beginning to sunset some legacy features like Tessera privacy. A blog is now in review announcing these plans and stating a timeline. This work will help streamline the code-base and get private networks on the most performant formats like Bonsai and Snap. This work will spill into Q3 and likely Q4. A big focus of the maintainers will be on performance and stability in Q3, targeting a much higher gas throughput number in 2025 for Besu's execution (road to Gigagas).
+
+Feature work is largely paused in this quarter besides Bonsai Archive and work on the plug-in API alongside new documentation to attract plug-in devs and L2s to use the system.
+
+# Maintainer Diversity
+
+No new maintainers were added this quarter, but several contributors remained active or increased activity to move toward maintainership.
+
+# Contributor Diversity
+
+Many new contributors added PRs this quarter. Some were around private net features, like a fixed bass fee. Others were fixes to bugs, and some were cleanup, typo fixing (likely airdrop farming). Regardless, contribution activity is healthy. We are looking to keep some of these folks engaged.
+
+# Additional Information
diff --git a/project-reports/2024/2024-Q2-Hyperledger-Caliper.md b/project-reports/2024/2024-Q2-Hyperledger-Caliper.md
new file mode 100644
index 00000000..289fb43b
--- /dev/null
+++ b/project-reports/2024/2024-Q2-Hyperledger-Caliper.md
@@ -0,0 +1,55 @@
+---
+layout: default
+title: 2024 Q2 Hyperledger Caliper
+parent: 2024
+grand_parent: Project Updates
+---
+
+# Project Health
+
+[2024 Q2 LFX Insights for Hyperledger Caliper](https://insights.lfx.linuxfoundation.org/foundation/hyp/overview?project=caliper&bestPractice=false&repository=https:%2F%2Fgithub.com%2Fhyperledger%2Fcaliper&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true)
+
+* 2 active maintainers
+* Questions on Discord and GitHub are periodically answered
+* Contributor discussions happen mostly on Discord
+* The mentorship projects have started in June, the first contributions are on their way
+
+# Questions/Issues for the TOC
+
+Not at this time.
+
+# Releases
+
+The latest stable release is v0.6.0; we're also continuously publishing unstable releases after every merged PR (no new releases):
+
+* [npm](https://www.npmjs.com/package/@hyperledger/caliper-cli/v/0.6.0)
+* [DockerHub](https://hub.docker.com/layers/hyperledger/caliper/0.6.0/images/sha256-ace68b58b329a5f2c5bd569cc2f59b7f64e9bbee1f3bb9f4f8a97469b55d7b2b?context=explore)
+
+# Overall Activity in the Past Quarter
+
+[List of merged PRs (28)](https://github.com/hyperledger/caliper/pulls?q=is%3Apr+is%3Aclosed+merged%3A2024-04-01..2024-07-17)
+
+Summary of activities:
+* Publish v0.6.0 with a security fix
+* Documentation improvements/fixes
+* Removing legacy components
+* Updating dependency versions
+
+# Current Plans
+
+The two main goals for the next quarter is to migrate the documentation to the suggested Hyperledger template, and to increase the test coverage of the core components. Both plans are carried out by the running mentorship projects.
+
+# Maintainer Diversity
+
+[Hyperledger Caliper maintainers](https://github.com/hyperledger/caliper/blob/08f732a484c93285fdc4df628f10cbc8d454d583/MAINTAINERS.md) in 2024 Q2 (unchanged compared to the previous quarter):
+* Dave Kelsey (IBM UK)
+* Attila Klenik (NTCA|BME, Hungary)
+
+# Contributor Diversity
+
+Contributions from maintainers, the community and the mentorship project mentees.
+
+# Additional Information
+
+N.A.
+
diff --git a/project-reports/2024/2024-Q2-Hyperledger-Cello.md b/project-reports/2024/2024-Q2-Hyperledger-Cello.md
new file mode 100644
index 00000000..1d8964d6
--- /dev/null
+++ b/project-reports/2024/2024-Q2-Hyperledger-Cello.md
@@ -0,0 +1,67 @@
+---
+layout: default
+title: 2024 Q2 Hyperledger Cello
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+# Project Health
+
+The Hyperledger Cello project is running well, fixing chain code related issues and upgrading versions of some dependencies and tools.
+
+* Solve the problem of uploading chain codes and fix the display issue on the chain code page at the same time;
+* Upgrade dependent versions:
+ * idna: 2.10 --> 3.7;
+ * sqlparse: 0.4.4 --> 0.5.0;
+ * gh-pages: 2.2.0 --> 6.1.1.
+* Add hash value verification for chain code packaging files.
+* Add a "Who is using the project" page in the wiki to record the companies using the Cello project.
+
+# Questions/Issues for the TOC
+
+There are currently no outstanding issues.
+
+# Releases
+
+* v1.1 is planned to be released in 2024
+* v1.0.0-GA was released in October 2023.
+* v1.0.0-RC2 was released in September 2023.
+* v1.0.0-RC1 was released in June 2023.
+* v1.0.0-beta1 was completed in November 2022.
+
+# Overall Activity in the Past Quarter
+
+The team mainly focuses on fixing issues in released versions.
+
+* Fix and test the issue of uploading chain codes;
+* Optimizing the chain code page issue;
+* Add hash verification to chain code packets;
+* Discuss and plan the feature points that the new version needs to support.
+
+# Current Plans
+
+Next steps include:
+
+* Complete and test the chain code operation function, conduct research and design on the ledger archiving function.
+* Supports Fabric LTS v2.5
+* Preparing to release version 1.1
+
+# Maintainer Diversity
+
+Currently, there are 4 maintainers, and active developers who consistently contribute to Cello (for at least 3 months) may be nominated as new maintainers:
+
+Baohua Yang (Oracle)
+Feng Yang (H3C)
+Yuanmao Zhu (Coinbase)
+Xichen Pan (University of British Columbia)
+
+# Contributor Diversity
+
+In this quarter, the team merged 12 pull requests. There are a total of 21 commits from 4 contributors, with 0.39 K lines of code change.
+
+# Additional Information
+
+[Contribution Metrics](https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Fcello/dashboard;subTab=technical?time=%7B%22from%22:%22now-90d%22,%22type%22:%22datemath%22,%22to%22:%22now%22%7D)
+
diff --git a/project-reports/2024/2024-Q2-Hyperledger-FireFly.md b/project-reports/2024/2024-Q2-Hyperledger-FireFly.md
new file mode 100644
index 00000000..993a44ce
--- /dev/null
+++ b/project-reports/2024/2024-Q2-Hyperledger-FireFly.md
@@ -0,0 +1,99 @@
+---
+layout: default
+title: 2024 Q2 Hyperledger FireFly
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+# Project Health
+
+Hyperledger FireFly successfully launched [V1.3](https://www.hyperledger.org/blog/hyperledger-firefly-v1.3-is-now-available) this quarter. This is a significant upgrade that makes the industry’s first open-source Web3 Gateway an even more powerful platform for tokenization, multi-chain interoperability, and building blockchain-based applications.
+
+FireFly continues to expand its maintainer base and diversity with 3 new maintainers this quarter. New maintainers include Enrique Lacal from Kaleido, Sam May from Kaleido, and Alexey Semenyuk from Instinct Tools.
+
+In addition, FireFly continues to power many use cases in the digital assets community and remains a leader in enterprise middleware.
+
+### Community adoption updates
+
+- [SWIFT CBDC Phase 2](https://www.swift.com/sites/default/files/files/swift_cbdc_sandbox_project_results_report_phase2_final_220324.pdf)
+ - Hyperledger Firefly was used to facilitate interoperability in the world’s largest CBDC industry collaboration to date.
+ - Interoperability was tested between 38 different banks across chains running Besu, Fabric, and Corda.
+ - Networks included 7 simulated CBDC networks, a foreign exchange network, a digital asset network, and a simulated CLS application, representing a mix of digital and traditional networks.
+
+
+Community members have given talks featuring Hyperledger FireFly at a number of events including:
+
+- Consensus 2024 where Hyperledger FireFly members presented at the Hyperledger booth
+- Hyperledger Member Webinar: [Streamlining Delivery-versus-Payment with Hyperledger Technologies](https://www.youtube.com/watch?v=gnZOXHBsVdk&t=2737s)
+- Duke Web3 Conference: [Real World Asset Tokenization](https://www.dukeweb3conference.com/speakers)
+- Token 2049: [Decentralized Trust & Web3 in the Enterprise](https://lu.ma/lxjqfuw3?hss_channel=lcp-10851358)
+- University of Southampton Business School lecture: [Web3 in Industry](https://www.linkedin.com/feed/update/urn:li:activity:7196499141403856896)
+- [FireFly 1.3 webinar](https://www.meetup.com/hyperledger-raleigh/events/301138155/) scheduled for 6/10
+
+### Contributor activity updates
+
+The star activity for the FireFly repository has continued to grow from 430 end of last quarter to 481 end of this quarter. Discord activity remains consistent with ~45 DAU.
+
+
+
+Contributors are active in the project and since March, there were 19 new contributors who performed at least one commit.
+There are currently over 770k lines of code for Hyperledger FireFly across 20 repositories, with a total of 10.482k commits to date.
+
+# Questions/Issues for the TOC
+
+None
+
+# Releases
+
+## [FireFly v1.3](https://github.com/hyperledger/firefly/releases/tag/v1.3.0)
+FireFly v1.3 new features include:
+- Namespace Isolation: Isolated event streams added per namespace, improving replay functionality and availability without breaking changes.
+- Invoke with Data: FireFly now supports custom smart contracts with data association, enhancing customization and enabling the ability to associate an off-chain data payload and pin it on a custom contract.
+- Transaction Manager Performance: Support for PostgreSQL boosts transaction management performance and provides rich query APIs for better integration and diagnosis.
+- Enhanced Performance with Besu: FireFly v1.3 optimizes integration with Hyperledger Besu, improving transaction coordination and state management for enterprise finance applications.
+- Tezos Connector: New Tezos connector enables remote transaction signing and integration with key management solutions for decentralized applications on Tezos.
+
+# Overall Activity in the Past Quarter
+
+The major highlights have been detailed at the beginning of the report. In summary, there has been a lot of activity in the project. New community members continue to discover the project and make contributions. This quarter has seen the most significant new contribution from outside the set of the original maintainers, in the form of an entirely new blockchain connector. Additionally, FireFly 1.3 was released
+
+# Current Plans
+
+As part of our annual report, we listed the following goals for 2024.
+- Release FireFly v1.3 (Q1) - This has been completed this quarter.
+- Host another in-depth workshop to get even more developers hands on with FireFly - An in-depth workshop is being planned and scheduled for the end of Q3 2024.
+- Continue to increase diversity of maintainers - FireFly has added three 3 new maintainers this quarter across 2 organizations.
+
+# Maintainer Diversity
+
+FireFly now has 14 maintainers representing three different companies:
+
+- [Kaleido](https://kaleido.io/)
+- [Fidelity](https://www.fidelity.com/)
+- [OneOf](https://www.oneof.com/)
+
+It is worth noting that each company has at least one maintainer who is a subject matter expert on one or more specific blockchain connectors, and the most foundational parts of the FireFly technology stack.
+
+A list of all maintainers for Hyperledger FireFly may be found [here](https://wiki.hyperledger.org/display/FIR/Maintainers).
+
+# Contributor Diversity
+
+In the past quarter we’ve seen an increase in contributor strength, commit growth, and new contributors from parties outside of Kaleido.
+
+[Commit Activities](https://insights.lfx.linuxfoundation.org/projects/hyperledger%2Ffirefly/dashboard;subTab=technical;v=source-control%2Fcommits%2Foverview)
+
+
+
+
+
+
+
+
+
+
+
+# Additional Information
+
+No additional information
diff --git a/project-reports/2024/2024-Q2-Hyperledger-Solang.md b/project-reports/2024/2024-Q2-Hyperledger-Solang.md
new file mode 100644
index 00000000..78e6adad
--- /dev/null
+++ b/project-reports/2024/2024-Q2-Hyperledger-Solang.md
@@ -0,0 +1,52 @@
+---
+layout: default
+title: 2024 Q2 Hyperledger Solang
+parent: 2024
+grand_parent: Project Updates
+---
+
+# Project Health
+
+* Hyperledger Solang development is going well. Work on the Soroban target is carried out, with the supervision of the Stellar Foundation.
+
+* Solang Playground now supports compilation in the browser, marking the second milestone of the Web3 Foundation Grant as done.
+
+# Questions/Issues for the TOC
+
+There are no issues at this time.
+
+# Releases
+
+* Hyperledger [Solang v0.3.4: Athens](https://github.com/hyperledger/solang/pull/1639), is currently being worked on by Cyrill Leutwiler. It is not yet published.
+
+# Overall Activity in the Past Quarter
+
+## For Solang
+* For the newly added Soroban target, work on supporting a `counter.sol` contract was underway. The purpose was not only to support simple contracts, but to build a `skeleton` whereby new functionality can be easily added to Soroban contracts.
+
+* Vendor `forge-fmt` into the Solang repository, as the published forge-fmt is out dated, not maintained, and depends on an old version of solang-parser.
+
+## For Solang-playground
+* Work on supporting compilation in the browser was carried out, and submitted to W3F for review.
+
+
+# Current Plans
+
+* Work on Soroban target till maturation.
+* Improve Solang Playground UI/UX, making it more visually attractive.
+* Make content involving Solang/Solang-Playground, including Tutorials, Video content, documentation improvements, etc ...
+
+# Maintainer Diversity
+
+Alongside the four active maintainers Sean Young, Lucas Steuernagel, Cyrill Leutwiler, and Salaheldin Soliman, it is worth mentioning that Solang Playground has added a new maintainer: Tarek Naser, once a hyperledger mentee.
+
+# Contributor Diversity
+
+Most contributions were made by core maintainers, alongside some issues being solved by community members.
+
+
+# Additional Information
+
+None at this time.
+
+
diff --git a/project-reports/2024/2024-Q3-Hyperledger-AnonCreds.md b/project-reports/2024/2024-Q3-Hyperledger-AnonCreds.md
new file mode 100644
index 00000000..6894681e
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-AnonCreds.md
@@ -0,0 +1,121 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger AnonCreds
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+Created by Stephen Curran with input from the Hyperledger AnonCreds Maintainers.
+
+## Implementation Repositories
+
+- [anoncreds-rs] - Rust implementation of AnonCreds
+- [anoncreds-clsignatures-rs] - Rust implementation of CL Signatures used in [anoncreds-rs]. Moved from Ursa and enhanced.
+- [anoncreds-v2-rs] - Rust draft implementation of AnonCreds v2 -- **new contribution this quarter**
+
+[anoncreds-rs]: https://github.com/hyperledger/anoncreds-rs
+[anoncreds-clsignatures-rs]: https://github.com/hyperledger/anoncreds-clsignatures-rs
+[anoncreds-v2-rs]: https://github.com/hyperledger/anoncreds-v2-rs
+
+### Specifications
+
+- [AnonCreds Specification] published from the repository [anoncreds-spec]
+- [AnonCreds Methods Registry] published from the repository [anoncreds-methods-registry]
+- [AnonCreds v2.0 Specification] published from the repository [anoncreds-spec-v2]
+
+[anoncreds-spec]: https://github.com/hyperledger/anoncreds-spec
+[AnonCreds Specification]: https://hyperledger.github.io/anoncreds-spec/
+[anoncreds-methods-registry]: https://github.com/hyperledger/anoncreds-methods-registry
+[AnonCreds Methods Registry]: https://hyperledger.github.io/anoncreds-methods-registry
+[anoncreds-spec-v2]: https://github.com/hyperledger/anoncreds-spec-v2
+[AnonCreds v2.0 Specification]: https://hyperledger.github.io/anoncreds-spec-v2/
+
+### Web and Wiki Pages
+
+- [Hyperledger AnonCreds Website Home Page]
+- [Hyperledger AnonCreds Wiki Home Page]
+
+[Hyperledger AnonCreds Website Home Page]: https://www.hyperledger.org/use/anoncreds
+[Hyperledger AnonCreds Wiki Home Page]: https://wiki.hyperledger.org/display/ANONCREDS/
+
+## Project Health
+
+Contributions remain slow on the AnonCreds project itself this quarter, but
+there has been a significant uptake in conversations around the use of ZKP-based
+verifiable credentials in the AnonCreds and other VC communities. The EU has a
+requirement to use "unlinkable" (non-correlatable) verifiable credentials with
+the [EUDI Wallets]. To now, the plan to meet that requirement has not been to
+use ZKPs, but instead to issue many instances of each credential and have the
+holder use each credential just once, or at least, each credential with just one
+verifier. Each instance is slightly different, and as a result, each verifier
+gets an unlinkable credential -- although the verifiers can correlate the
+credentials through the issuer. The reasons for the "no to ZKP" has been an
+additional requirement that each credential be bound to a hardware key held in
+the holders mobile device -- which is not possible with ZKP schemes such as CL
+Signatures used in AnonCreds v1 or BBS Signatures planned for use in AnonCreds
+v2. Some well-known cryptographers have [weighed in on that approach] and
+[presented a paper] arguing that the "batch issue" approach is ineffective. As
+well, they have proposed a new scheme that implements ZKPs using
+ECDSA hardware-based keys. The folks involved in AnonCreds are part of that
+discussion, and will see how that might impact the direction of the AnonCreds
+project.
+
+[weighed in on that approach]: https://github.com/eu-digital-identity-wallet/eudi-doc-architecture-and-reference-framework/issues/200
+[presented a paper]: https://github.com/user-attachments/files/15904122/cryptographers-feedback.pdf
+[EUDI Wallets]: https://digital-strategy.ec.europa.eu/en/policies/eudi-wallet-implementation
+
+The [AnonCreds Quarterly Activity Dashboard] shows the activity on the project
+repositories from April to June 2024.
+
+[AnonCreds Quarterly Activity Dashboard]: https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview/github?project=anoncreds&routedFrom=Github&bestPractice=false&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true&repository=
+
+## Questions/Issues for the TOC
+
+None.
+
+## Releases
+
+- [anoncreds-rs] -- None
+- [anoncreds-clsignatures-rs] — None
+
+## Overall Activity in the Past Quarter
+
+There have been a couple of PRs to the new AnonCreds v2 Rust repository, including from some new contributors.
+
+Few attendees have been at the recent AnonCreds Working Group meetings.
+
+There have been additional, significant contributions of code in the Hyperledger Labs [Agora]
+project -- [audited cryptographic libraries].
+
+[Agora]: https://labs.hyperledger.org/labs/agora.html
+[audited cryptographic libraries]: https://github.com/hyperledger-labs?q=agora
+
+[AnonCreds Rust]: https://github.com/hyperledger/anoncreds-rs
+
+## Current Plans
+
+Continued evolution of the [AnonCreds Rust] library. Contributing to the
+conversation happening in the broader community about new ways to use ZKPs for
+achieving unlinkable VCs, and determining how to leverage that work into
+expanding efforts on AnonCreds, or using the resources of AnonCreds together
+with those efforts.
+
+## Maintainer Diversity
+
+Project Maintainers are from three different organizations: Animo Solutions, BC
+Gov, and SICPA, plus an individual contributor.
+
+## Contributor Diversity
+
+LFX Insights seems to suggest there have been contributions in the quarter from
+at least 8 different organizations. But it is really hard to be sure.
+
+## Additional Information
+
+- Key channels on Hyperledger Discord: \#anoncreds, \#anoncreds-spec,
+\#anoncreds-rs
+- [AnonCreds Mailing List](https://lists.hyperledger.org/g/anoncreds)
+- Meetings pages
+ - [AnonCreds Working Group](https://wiki.hyperledger.org/display/ANONCREDS/Meetings%3A+AnonCreds+Working+Group)
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Aries.md b/project-reports/2024/2024-Q3-Hyperledger-Aries.md
new file mode 100644
index 00000000..67daf846
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Aries.md
@@ -0,0 +1,144 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Aries
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+nav_exclude: true
+---
+
+## Project Health
+
+Work on [Hyperledger Aries] continues at a healthy pace, with lots of activity
+in all of the Aries and the related-OWF sub-communities. [Aries Cloud Agent
+Python] continues to move to its 1.0.0 release, and the community around
+[Aries-VCX] is again growing, with lots of work happening in moving the
+implementation forward. [Open Wallet Foundation]-hosted [Credo-TS] and [Bifold
+Wallet] continue to evolve rapidly. [Animo Solutions], key maintainers of
+[Credo-TS], were selected by the German Government as a funded participant in
+the [Funke] ("sparkle") initiative to create innovative wallet prototypes in
+preparation for the promised German [EUDI Wallet] to be released by 2026.
+Exciting times!
+
+[Funke]: https://www.sprind.org/en/challenges/eudi-wallet-prototypes/
+[Animo Solutions]: https://animo.id/
+[EUDI Wallet]: https://digital-strategy.ec.europa.eu/en/policies/eudi-wallet-implementation
+
+[Hyperledger Aries]: https://www.hyperledger.org/projects/aries
+[Credo-TS]: https://github.com/openwallet-foundation/credo-ts
+[Aries Cloud Agent Python]: https://github.com/hyperledger/aries-cloudagent-python
+[Aries VCX]: https://github.com/hyperledger/aries-vcx
+[Open Wallet Foundation]: https://openwallet.foundation/
+[Indy VDR]: https://github.com/hyperledger/indy-vdr
+[AnonCreds RS]: https://github.com/hyperledger/anoncreds-rs
+
+## Questions/Issues for the TOC
+
+None at this time.
+
+## Releases
+
+The following Aries releases occurred in the last two quarters (including the
+time covered by the Annual Report and so not yet reported):
+
+- [Aries Cloud Agent Python] -- 0.11.1, 0.12.0, 0.12.1
+- [Aries Askar] -- None
+- [Aries VCX] -- v0.64.0
+
+Interoperability status can be seen
+here: [https://aries-interop.info](https://aries-interop.info).
+
+## Overall Activity in the Past Quarter
+
+Per the [Aries Activity Dashboard] for the months of April-June 2024, Aries
+codebases had 3185 Commits and 275 contributors representing at least 28
+organizations. The numbers do include the repositories
+that have moved from Hyperledger to the Open Wallet Foundation, as well as some
+obsolete (but unchanging) repositories. Per Ry Jones there is not a good way for
+us to control the included list of repos.
+
+[Aries Activity Dashboard]: https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview/github?project=aries&routedFrom=Github&bestPractice=false&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true
+
+- The [Indy SDK] has been removed from ACA-Py, eliminating the older component in favour of newer and more capable
+ replacements ([Aries Askar], [Indy VDR], and [AnonCreds RS]). Good to see that
+ transition!
+ - **NOTE: THIS DOES NOT REMOVE INDY SUPPORT FROM ACA-PY!**
+- Support for AnonCreds in W3C VCDM Format in Aries has been implemented in [Aries Cloud Agent Python].
+- Work has begun on adding [DIDComm v2] support in [ACA-Py].
+
+[Aries Askar]: https://github.com/hyperledger/aries-askar
+[Indy SDK]: https://github.com/hyperledger/indy-sdk
+[DIDComm v2]: https://identity.foundation/didcomm-messaging/spec/
+[ACA-Py]: https://aca-py.org
+
+## Aries Framework Reports
+
+### [Aries VCX]
+
+Lots of work has been happening on Aries VCX with the release of 0.64.0 and
+0.65.0, and it has also gained new maintainers, contributors and support from
+Instnt.
+
+The releases have included updates to the AATH (Aries Agent Test Harness) Aries
+VCX Backchannel to include the latest 0.65.0 updates and implement processes for
+continuous deployment of the backchannel. As part of the efforts updating the
+backchannel, work has occurred to resolve interoperability issues between Aries
+VCX and Aries Cloud Agent Python (ACA-Py) within DID Exchange, adding support
+for DID Exchange 1.1 and did:peer numalgo 4.
+
+Release 0.65.0 marks the planned final release including support for the
+indy-sdk, credx, and indyvdrtools crates and features in Aries VCX. The
+replacement for these crates are already implemented (Aries Askar, anoncreds-rs,
+and indy-vdr) in Aries VCX. Additional info or discussion can be found here.
+Work is underway to remove these dependencies from the project.
+
+Work is in-progress on fixing and enhancing fixing Android support, as well as
+adding support for iOS. Support for usage via React Native will be considered in
+the future as well. Additionally, work is planned and underway to improve the
+overall ease of use of Aries VCX to boost its adoption.
+
+### [Aries Cloud Agent Python]
+
+[Aries Cloud Agent Python] (ACA-Py) work in the quarter has focused on the
+upcoming Release 1.0.0. Almost everything is in place and as this is being
+written, the last PR for the release is being reviewed. Real Soon Now! Details
+about the updates and changes in the release can be found about about the
+release from the [ACA-Py Release Candidate changelog].
+
+The maintainers of ACA-Py are in the process of adding a Long Term Support (LTS)
+policy for the project, modelled on the Hyperledger Fabric LTS approach. We have
+two LTS versions at this time (0.11.x and 0.12.x). Once stabilized, there will
+be a 1.x LTS minor release declared as well.
+
+Transitioned the sourcing of the ACA-Py documentation site [https://aca-py.org]
+to be from the ACA-Py repo itself.
+
+[https://aca-py.org]: https://aca-py.org
+
+[ACA-Py Release Candidate changelog]: https://github.com/hyperledger/aries-cloudagent-python/blob/main/CHANGELOG.md
+
+## Current Plans
+
+- Releasing v1.0.0 of ACA-Py.
+- Deploying support for [AnonCreds in W3C Verifiable Credentials Data Model Standard] format.
+- Continuing working to add support for [DIDComm V2].
+- Adding support for the [`did:tdw` DID Method], including support for rooting AnonCreds Verifiable Credentials using a `did:tdw` DID
+- Moving to Phase 2 of two Community Coordinated Updates ([793], [496]) in effort to deprecate old practices and adopt replacements in a coordinated effort.
+
+[AnonCreds in W3C Verifiable Credentials Data Model Standard]: https://marketplace.digital.gov.bc.ca/opportunities/code-with-us/7afcbd7c-2bbc-41ed-bf27-b6ba6e2903c5
+[`did:tdw` DID Method]: https://bcgov.github.io/trustdidweb/
+[793]: https://hyperledger.github.io/aries-rfcs/latest/features/0793-unqualfied-dids-transition/
+[496]: https://hyperledger.github.io/aries-rfcs/latest/features/0496-transition-to-oob-and-did-exchange/
+
+## Maintainer Diversity
+
+There are currently 62 people on the 48 Hyperledger Aries teams representing at least 19 organizations.
+
+## Contributor Diversity
+
+In the quarter there were commits from 275 individuals representing at least 28 organizations.
+
+## Additional Information
+
+None
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Bevel.md b/project-reports/2024/2024-Q3-Hyperledger-Bevel.md
new file mode 100644
index 00000000..f87fc9dc
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Bevel.md
@@ -0,0 +1,85 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Bevel
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+# 2024 Q3 Hyperledger Bevel
+
+# Project Health
+
+[Hyperledger Bevel LFX Insights page](https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview?project=bevel&repository=&dateFilters=Last%20Year&dateRange=2023-01-01%20to%202023-12-31&compare=PP&granularity=month&hideBots=true)
+
+
+1. Getting code contributions for Hyperledger Bevel still remains a challenge.
+2. The Bevel project has received no external contributions; nearly all contributions for the last couple of releases have come from the Accenture team. Accenture will not be able to maintain the project without other organization or individual contributor help in maintaining.
+3. Community usage and interest are positive, as inferred from discussions and queries on the Discord channel.
+
+[Hyperledger Bevel Operator Fabric LFX Insights page](https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview?project=bevel&repository=https:%2F%2Fgithub.com%2Fhyperledger%2Fbevel-operator-fabric)
+
+
+# Questions/Issues for the TOC
+
+None.
+
+# Releases
+
+[Releases](https://github.com/hyperledger/bevel/releases) past quarter:
+
+- Bevel Release v1.0.1 and v1.1.0
+- Bevel Fabric Operator v1.10.1
+
+
+# Overall Activity in the Past Quarter
+
+The project delivered its roadmap targets for Q2/Q3. See [roadmap](https://hyperledger-bevel.readthedocs.io/en/develop/references/roadmap/) for details.
+
+Deployment using just helm commands with proxy/vault and without proxy/vault options for all DLT platform
+Ansible automations to use the new helm charts.
+
+Bug fixes in `kubectl-hlf` plugin while adding new organisation to the fabric network
+
+# Current Plans
+
+- Continue with Q3 plan and release commitments.
+- Hyperledger meetup: Bevel workshop series remaining two sessions in September.
+- Explore cloud native vaults (AWS secret manager).
+- Collaborate with hyperledger-labs blockchain explorer and fabric-operations-console teams and plan to add deployment support on bevel.
+- Bevel Operator Fabric will have fabric 3.0 support once fabric 3.0 is released.
+
+# Maintainer Diversity
+
+- There is change in the maintainers for Bevel. You can find our current maintainer list here:
+https://github.com/hyperledger/bevel/blob/main/MAINTAINERS.md.
+
+
+
+- Existing maintainers:
+ - Sownak Roy (Accenture)
+ - Suvajit Sarkar (Accenture)
+ - Aditya Joshi (Walmart)
+- Emeritus Maintainers:
+ - Jonathan M Hamilton (Accenture)
+ - Tracy Kuhrt (Accenture)
+ - Jagpreet Singh Sasan (Accenture)
+ - Arun S M (Walmart)
+ - Weihong Ou (Walmart)
+
+- There is no change in the maintainers Bevel-Operator-Fabric. You can find our current maintainer list here:
+https://github.com/hyperledger/bevel-operator-fabric/blob/main/MAINTAINERS.md.
+
+
+
+- Existing maintainers:
+ - David Viejo (Kung Fu Software)
+ - Aditya Joshi (Walmart)
+
+# Contributor Diversity
+[Dashboard](https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/reports/contributors?project=bevel&repository=https:%2F%2Fgithub.com%2Fhyperledger%2Fbevel&routedFrom=Github)
+
+# Additional Information
+
+N/A
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Cacti.md b/project-reports/2024/2024-Q3-Hyperledger-Cacti.md
new file mode 100644
index 00000000..aa02d240
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Cacti.md
@@ -0,0 +1,95 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Cacti
+parent: 2024
+grand_parent: Project Updates
+---
+
+
+# Project Health
+
+- The project is in good health!
+- Multiple mentorship projects are underway, namely [Enabling Enterprise Organizational Blockchain Interoperability](https://wiki.hyperledger.org/display/INTERN/Enabling+Enterprise+Organizational+Blockchain+Interoperability) and [Cacti: Core Operators Modules for DLTs](https://wiki.hyperledger.org/display/INTERN/Cacti%3A+Core+Operators+Modules+for+DLTs).
+- `v2.0.0-rc.2` was released a couple weeks ago and `v2.0.0-rc.3` is not far behind (hopefully next week)!
+- Major efforts are underway to integrate the codebase further
+- We continue to promote interoperability protocol standardization by contributing to, and implementing, the candidate [IETF SATP specification](https://datatracker.ietf.org/doc/draft-ietf-satp-core/) using different combinations of Cacti modules. We conducted a [workshop on May 23, 2024](https://wiki.hyperledger.org/display/events/Standardizing+DLT+Interoperation%3A+Implementing+IETF+Secure+Asset+Transfer+Protocol+in+Hyperledger+Cacti) to discuss the protocol and demonstrate the associated Cacti capabilities.
+- Enabled the [OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com%2Fhyperledger%2Fcacti) for the project.
+
+LFX Insights (Beta) Link:
+https://insights.lfx.linuxfoundation.org/foundation/hyp/overview/github?project=cacti&routedFrom=Github&bestPractice=false
+
+# Questions/Issues for the TOC
+
+No questions for the TOC.
+
+# Releases
+
+- v2.0.0-rc.2 - issued
+- v2.0.0-rc.3 - upcoming
+
+# Overall Activity in the Past Quarter
+
+- Most of our activity comes from the Discord channel. The daily pair programming calls are well attended by mentees, existing contributors and would-be contributors alike.
+- Questions are answered in a mostly timely fashion though it's not perfect we do make a conscious effort to respond quickly.
+- The CI performance optimizations are still ongoing, but we are close to having a solution to dynamic diff analysis which makes it so that our CI jobs only run tests of a package that had changes in itself or its dependency tree of packages.
+- We now have more than 60 packages in the monorepo total.
+- The release automation that published packages to npmjs.com and ghcr.io has been fixed, we no longer have to manually run publishing scripts.
+- New features are being worked on as we speak. Most of the development here focuses on IETF-SATP. More information on the [Cacti discord channel](https://discord.com/channels/905194001349627914/908379338716631050).
+
+# Current Plans
+
+1. Work is being done on a Cacti example that combines the Harmonia Lab smart contracts and the Cacti Corda JVM connector plugin together. Once this is ready, we hope to show it off to the Harmonia Lab maintainers and seek further partnership and collaboration between the two groups.
+2. Cactus & Weaver Integration - we work on this ourselves and also have a mentorship project underway for the same.
+3. Documentation revamp and updating process is ongoing.
+4. There are dozens of branches with build process improvements and test stability fixes (we have flaky tests that are too resource intensive for the free tier GitHub runners but we can't move to the paid tier due to our CI taking 8 to 10 hours of compute time to run).
+5. We are working on improving our OpenSSF Scorecard numbers.
+
+# Maintainer Diversity
+
+We have 8 active maintainers from 4 different organizations total:
+
+- Izuru Sato
+- Michal Bajer
+- Peter Somogyvari
+- Takuma TAKEUCHI
+- Jagpreet Singh Sasan
+- Venkatraman Ramakrishna
+- Sandeep Nishad
+- Rafael Belchior
+
+# Contributor Diversity
+
+Source: https://insights.lfx.linuxfoundation.org/foundation/hyp/reports/organizations?project=cacti&routedFrom=Github&bestPractice=false
+
+|name |Active Days|Activities count|Activities percent|
+|-------------------------------------------|-----------|----------------|------------------|
+|Accenture Global Solutions Limited |277 |3.45K |64.08% |
+|Ework Group |162 |821 |15.21% |
+|International Business Machines Corporation|101 |434 |8.04% |
+|Fujitsu Limited |90 |233 |4.32% |
+|Blockdaemon |63 |269 |4.99% |
+|INESC-ID |34 |62 |1.15% |
+|ZAUBAR |14 |52 |0.96% |
+|Hex Trust |13 |20 |0.37% |
+|Blazpay |13 |18 |0.33% |
+|Hyperledger |11 |49 |0.91% |
+|Cheesecake Labs |9 |19 |0.35% |
+|Reliance Jio Infocomm Limited |8 |15 |0.28% |
+|Infosys Limited |7 |8 |0.15% |
+|TUBITAK UEKAE |4 |7 |0.13% |
+|Foogle Tech Software |3 |5 |0.09% |
+|SAITM22 |3 |4 |0.07% |
+|Samsung Electronics Co. Ltd. |2 |4 |0.07% |
+|SeeWise.AI |2 |2 |0.04% |
+|Rapid Innovation |2 |2 |0.04% |
+|GitHub |1 |2 |0.04% |
+|Signify Holding |1 |1 |0.02% |
+|Individual - No Account |1 |1 |0.02% |
+|Bank of New York Mellon |1 |1 |0.02% |
+|Texas A And M University |1 |1 |0.02% |
+|Zeeve Inc |1 |1 |0.02% |
+
+
+
+# Additional Information
+- Different collaborations with the academia and industry are still taking place. In particular, one of them is [Portugal's BLOCKCHAIN.PT project](https://www.hyperledger.org/blog/portugals-blockchain.pt-uses-hyperledger-cacti-as-its-interoperability-framework).
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Fabric.md b/project-reports/2024/2024-Q3-Hyperledger-Fabric.md
new file mode 100644
index 00000000..10464be0
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Fabric.md
@@ -0,0 +1,71 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Fabric
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+# 2024 Q3 Hyperledger Fabric
+
+# Project Health
+
+Hyperledger Fabric is fairly mature and stable with a v2.5 long-term support (LTS) release.
+There is less churn and fewer commits than in years past, with continued focus on quality, maintenance, and support.
+New features get proposed, approved, and implemented based on a community RFC process.
+Mailing list activity is down a bit compared to prior years.
+PRs and mailing list questions are generally turned around quickly.
+There is significant Discord activity.
+
+# Questions/Issues for the TOC
+
+None.
+
+# Releases
+
+LTS release:
+- v2.5 is the current LTS release with patch releases at least quarterly.
+- Note that v2.2 has reached end of maintenance and all users are encouraged to update to v2.5 to continue receiving fixes and security updates.
+
+[Releases](https://github.com/hyperledger/fabric/releases) past quarter:
+- Fabric v2.5.8 - May 21, 2024
+- Fabric v2.5.9 - June 18, 2024
+- Fabric v3.0.0-beta - March 14, 2024
+
+# Overall Activity in the Past Quarter
+
+The project delivered patch releases for the Fabric v2.5 long-term support release. See [release notes](https://github.com/hyperledger/fabric/releases) for details.
+
+v3.0 development is nearing completion. The following enhancements were made this quarter:
+- Support for cryptographic algorithm Ed25519 for transaction signing and verification (in addition to the existing ECDSA support).
+- SmartBFT automated testing completed.
+- Features that were [marked as deprecated in Fabric v2](https://github.com/hyperledger/fabric/releases/tag/v2.5.9) have been removed in preparation for an official Fabric v3 release.
+
+A v2 API became available for Go chaincodes. Essentially, the same API support was maintained while updating protocol buffer bindings to APIv2. Users are encouraged to utilize the v2 API for new Go chaincodes. See the July contributor meeting [recording](https://youtu.be/fytjclm2Rks) for details and see fabric-samples repository for the simple [edit](https://github.com/hyperledger/fabric-samples/blob/main/asset-transfer-basic/chaincode-go/chaincode/smartcontract.go#L7) to utilize v2.
+
+The project added the [OpenSSF Scorecard](https://scorecard.dev/viewer/?uri=github.com/hyperledger/fabric) and improved score in multiple categories.
+
+# Current Plans
+
+The project continues to maintain and keep Fabric v2.5 current.
+
+The project is working on final items for a v3.0 release, namely the removal of the legacy v1 chaincode lifecycle that has been deprecated since v2.0.
+
+The project is updating its charter to align with LF Decentralized Trust.
+
+# Maintainer Diversity
+
+6 of 9 [maintainers](https://github.com/hyperledger/fabric/blob/main/MAINTAINERS.md) from IBM.
+
+# Contributor Diversity
+
+- 53% of code activities were performed by top 4 contributors. Remaining 47% performed by 185 other contributors.
+- IBM contributors accounted for 82% of activity.
+- Of top 10 contributors, 7 of 10 from IBM.
+
+In summary, the project remains top-heavy from IBM but has good depth of smaller contributors.
+
+# Additional Information
+
+[Insights dashboard link](https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview/github?project=fabric&routedFrom=Github&bestPractice=false&repository=all&dateFilters=2024-04-01%20to%202024-07-01&dateRange=2024-04-01%20to%202024-07-01&compare=PP&granularity=week&hideBots=true)
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Identus.md b/project-reports/2024/2024-Q3-Hyperledger-Identus.md
new file mode 100644
index 00000000..ef297c61
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Identus.md
@@ -0,0 +1,62 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Identus
+parent: 2024
+grand_parent: Project Updates
+nav_exclude: true
+---
+
+Created by Fayyaadh Adams with input from other maintainers
+
+
+# Project Health
+
+The project is fairly new to the Hyperledger Ecosystem however we continue to have steady contributors. We are currently not on the LFX dashboard yet and are waiting to be added to gain further insights. In the last three weeks alone, we have seen 3 new contributors (not code related) show up and additional usage of our code within production environments (https://socious.io/ - production use case).
+
+
+# Questions/Issues for the TOC
+
+Is there a way to access funds for open source contributions and development?
+
+
+# Releases
+
+ * Identus V2.12
+ * Identus Cloud Agent - V.1.33.0
+ * Identus Mediator - V.0.14.2
+ * Identus Apollo - V.1.2.14
+ * Identus Edge Agent SDK TS - V.5.1.0
+ * Identus Edge Agent SDK KMP - V.3.0.0
+ * Identus Edge Agent SDK SWIFT - V.6.0.0
+ * Identus Docs - V.1.92.0
+
+
+
+# Overall Activity in the Past Quarter
+
+The main focus this quarter, and continuing into the next, is to achieve a rich set of features within Identus. The contribution of the code base from IOG to Hyperledger was completed in early July 2024. Initially it was only the cloud agent repository that was part of Hyperledger that started out as the Open Enterprise Agent Lab. The rest of the repositories were public repositories in IOG and has since been migrated to Hyperledger.
+
+The mailing list is not the primary tool for discussions, instead we encourage discussions and questions within the relevant Discord channels. To enhance support for community members, we have enlisted the CommunityOne bot, which is trained on the Identus documentation. This has been extremely helpful for developers seeking immediate answers when a contributor or maintainer is unavailable. The majority of development now is to get to feature complete and fix existing bugs that get reported by the community.
+
+We currently utilize two Discord servers: the Hyperledger Discord and the Atala Discord. The Atala Discord has seen significantly more engagement. Since January 2024, our membership has grown from 258 to 476 members. On average, there are 348 activities across various channels monthly, with about 39 users online daily. We are currently encouraging people to utilize the Hyperledger Discord instead of the Atala Discord.
+
+
+# Current Plans
+
+As previously mentioned, the team will focus on enhancing the features of Identus. This entails enabling the mediator to become production ready, OIDC for Verifiable Credential Issuance (OID4VC), revocation mechanisms for JWT, Universal Resolver for Prism DIDs, Implementation of user level events in SDKs and much more. This is constantly shared with the contributors and maintainers in order to come to a general consensus.
+
+Community is also encouraged to log feature requests, issues etc and this is then incorporated into a roadmap that is transparent for everyone to see https://github.com/orgs/hyperledger/projects/48
+
+
+# Maintainer Diversity
+
+We currently have 24 maintainers with 2 maintainers from outside of IOG. We aim to expand the external maintainers list in the future
+
+# Contributor Diversity
+
+At the moment, the main contributors of source code is IOG. Other organizations have given additional on feature request ideas such as Ahau and Socious. While we have other organizations such as C-Sign developing books specifically aimed at developers wanting to develop with Identus. The book is expected to be completed next year https://identusbook.com/book/
+
+
+# Additional Information
+
+NA
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Indy.md b/project-reports/2024/2024-Q3-Hyperledger-Indy.md
new file mode 100644
index 00000000..4e19dec5
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Indy.md
@@ -0,0 +1,145 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Indy
+parent: 2024
+grand_parent: Project Updates
+has_children: false
+has_toc: false
+---
+
+Created by Stephen Curran with input from the Hyperledger Indy Maintainers.
+
+## Sub-Projects
+
+### **Distributed Ledger**
+
+- [indy-node]
+- [indy-plenum]
+- [indy-test-automation]
+- [indy-node-monitor]
+- [indy-node-container]
+- [indy-blssignatures-rs]
+- [indy-besu]
+
+[indy-node]: https://github.com/hyperledger/indy-node
+[indy-plenum]: https://github.com/hyperledger/indy-plenum
+[indy-test-automation]: https://github.com/hyperledger/indy-test-automation
+[indy-node-monitor]: https://github.com/hyperledger/indy-node-monitor
+[indy-node-container]: https://github.com/hyperledger/indy-node-container
+[indy-blssignatures-rs]: https://github.com/hyperledger/indy-blssignatures-rs
+[indy-besu]: https://github.com/hyperledger/indy-besu
+
+### **Client Tools**
+
+- [indy-vdr]
+- [indy-shared-rs] -- for AnonCreds, [Hyperledger AnonCreds] should be used
+- [indy-cli-rs] -- new, Indy CLI based on Indy VDR, not Indy SDK
+
+[indy-vdr]: https://github.com/hyperledger/indy-vdr
+[indy-shared-rs]: https://github.com/hyperledger/indy-shared-rs
+[indy-cli-rs]: https://github.com/hyperledger/indy-cli-rs
+[Hyperledger AnonCreds]: https://github.com/hyperledger/anoncreds-rs
+
+### **Specifications**
+
+- [did:indy Specification], [did:indy Specification source repository]
+- [did:indy Networks]
+- [Indy HIPE] (Hyperledger Indy Project Enhancements)
+- [indy-did-method]
+
+[did:indy Specification]: https://hyperledger.github.io/indy-did-method/
+[did:indy Specification source repository]: https://github.com/hyperledger/indy-did-method
+[did:indy Networks]: https://github.com/hyperledger/indy-did-networks
+[Indy HIPE]: https://github.com/hyperledger/indy-hipe
+[indy-did-method]: https://github.com/hyperledger/indy-did-method
+
+## Project Health
+
+The project had less contributor activity over the quarter. Per the [Indy Quarterly
+Activity Dashboard], in the months April through June, 2024 there were 426
+commits (down about 50%) and 77 contributors (down about 30%). Work was focused
+on dependabot updates, the [Indy Besu] efforts (which is not included in the LFX
+data), and client performance improvements in digital credential wallets.
+
+[Indy Quarterly Activity Dashboard]: https://insights.lfx.linuxfoundation.org/foundation/lf-decentralized-trust/overview/github?project=indy&routedFrom=Github&bestPractice=false&dateFilters=Last%20Quarter&dateRange=2024-04-01%20to%202024-06-30&compare=PP&granularity=week&hideBots=true
+
+## Questions/Issues for the TOC
+
+None
+
+### Issues from previous reports
+
+#### **Diversity of Contributor Community**
+
+See the updated type of information in the appropriate section of this report.
+
+## Releases
+
+Release since the last quarterly report:
+
+- indy-node - None
+- indy-plenum - v1.14.0rc0 -- first release candidate for the Ubuntu 22.04 release of Indy Plenum
+- indy-vdr - - v0.4.2, v0.4.3
+- indy-node-container - v1.2.6
+- indy-shared-rs - None
+
+## Overall Activity in the Past Quarter
+
+Work continued this quarter on the Ubuntu 22.04 version of Indy.
+
+The [indy-vdr] work focused on improving performance in Wallets, and especially
+caching immutable transactions.
+
+Progress was made on the [Indy Besu] implementation of Indy capabilities on
+a Besu base, and in defining the Indy Besu updates to the [Indy DID Method].
+
+[Indy Besu]: https://github.com/hyperledger/indy-besu
+[Indy DID Method]: https://github.com/hyperledger/indy-did-method
+
+An Indy [Hyperledger Mentorship] project was kicked off this quarter to
+implement an [Indy Read Replica] capability. We look forward to the
+implementation efforts of [Bryan Elee] over the next few months on this project.
+
+[Hyperledger Mentorship]: https://wiki.hyperledger.org/display/INTERN/Hyperledger+Mentorship+Program
+[Indy Read Replica]: https://wiki.hyperledger.org/display/INTERN/Project+Plan+-+Indy+Read+Replica+Implementation
+[Bryan Elee]: https://github.com/rxbryan
+
+Two followups meetings to the most recent Indy Ecosystem Summit (#4, held April
+9, 2024) were held in May, 2024 covering the technical aspects and funding
+approaches to implementing Ledger Redactibility on Indy. A design was developed,
+but little progress was made towards a cross-community collaboration for funding
+and implementing the work. A couple of organizations have (as was suggested)
+submitted a proposal for a grant to fund the effort.
+
+## Current Plans
+
+The maintainers would like to see the publication of an official Indy release
+supporting Ubuntu 22.04. the work is well underway, with [indy-plenum] work
+complete, and a "rinse and repeat" of the dependency changes in [indy-node].
+
+[Indy Besu] work continues and is gaining interest. Work has begun towards
+adding a verifiable credential revocation capability to the implementation.
+
+We're now waiting on word of whether there will be a funding award for the
+Ledger Redaction implementation work as described above.
+
+## Maintainer Diversity
+
+There are 35 individuals on 22 Indy GitHub Teams representing at least 16 organizations.
+
+Still needed -- a cleanup of the teams are needed as some of the individuals are
+no longer active in the community. No progress was made on that cleanup this
+quarter. We have the team lists, but have not queried those on the list to see
+if they are still interested in being maintainers.
+
+## Contributor Diversity
+
+See the [Indy Quarterly Activity Dashboard] for information about contributors
+this quarter. The contributions came from at least 13 different
+organizations.
+
+## Additional Information
+
+- Key channels on Hyperledger Discord: \#indy, \#indy-sdk,
+\#indy-node, \#indy-maintainers, \#indy-vdr
+- [Indy Mailing List](https://lists.hyperledger.org/g/indy)
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Iroha.md b/project-reports/2024/2024-Q3-Hyperledger-Iroha.md
new file mode 100644
index 00000000..127879d2
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Iroha.md
@@ -0,0 +1,51 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Iroha
+parent: 2024
+grand_parent: Project Updates
+---
+
+# Project Health
+
+Iroha 2 continues to make steady progress in Q3. One more pre-MVP version was released, [pre-RC 22.0](https://github.com/hyperledger/iroha/releases/tag/v2.0.0-pre-rc.22.0). Current focus is on fixing performance issues, ironing out the API, updating the SDKs and documentation.
+
+Community activity is healthy: potential users and contributors express interest in the project, questions are being answered regularly, issues are being assigned to contributors, and we merged 5 community PRs since the last update. Project updates are sent out every two weeks.
+
+# Overall Activity in the Past Quarter
+
+In the past quarter, we rolled out Iroha `2.0.0-pre-rc.22.0`. Although pre-RC 21 was initially intended to be the final pre-MVP version, we have delayed the MVP release to address performance issues. Python SDK has been updated to the latest version, and significant progress has been made on the [Java](https://github.com/hyperledger/iroha-java/pull/431) and [JavaScript](https://github.com/hyperledger/iroha-javascript/pull/199) SDKs.
+
+### Highlights
+
+- **Key-centric Accounts**: Accounts are now [identified by a primary key](https://wiki.hyperledger.org/display/iroha/Key-centric+accounts+structure), with future support for aliases.
+- **Filtered Queries**: Queries in smart contracts [can now be filtered](https://github.com/hyperledger/iroha/pull/4544). An [open PR](https://github.com/hyperledger/iroha/pull/4833) introduces type-safe queries.
+- **Custom Instructions**: Added support for custom instructions via [executor upgrades](https://github.com/hyperledger/iroha/pull/4645), allowing users to expand the instruction set beyond the built-in ISI.
+- **On-chain `Parameter` API**: Refined for better type-safety and differentiation between built-in and custom parameters.
+- **New `ConfigReader` API**: Introduced for improved configuration debugging, error-reporting, and logging.
+- **Removed genesis signing.**: The signed genesis block is now provided to peers on startup, simplifying network initialization and improving consensus speed and security.
+- **Shallow data model**: [reduced nesting in the data model](https://github.com/hyperledger/iroha/issues/3921), enhancing performance and memory usage.
+- Added initial support for **multi-signature transactions** via triggers, with an example [here](https://github.com/hyperledger/iroha/pull/4788).
+- Improved UX with **new crate names**: `irohad` for the peer crate/binary, and `iroha` for the client crate/CLI.
+
+# Releases
+
+The following releases occurred in the past quarter:
+
+- [Iroha 2.0.0-pre-rc.22.1](https://github.com/hyperledger/iroha/releases/tag/v2.0.0-pre-rc.22.1) – July 30th, 2024
+- [Iroha 2.0.0-pre-rc.22.0](https://github.com/hyperledger/iroha/releases/tag/v2.0.0-pre-rc.22.0) – July 26th, 2024
+
+# Maintainer Diversity
+
+Since the last update, [Alexandra Zorina](https://github.com/a-zorina) has joined Iroha as a Technical Writer.
+
+# Contributor Diversity
+
+Most contributions in the past quarter were made by the core maintainers, with sporadic contributions by community members.
+
+# Current Plans
+
+Our main goal for the next quarter remains to deliver [RC 1](https://github.com/hyperledger/iroha/milestone/4), a feature-complete MVP. Additionally, there is an ongoing effort to overhaul the documentation and complete updating the SDKs.
+
+# Questions/Issues for the TOC
+
+None.
\ No newline at end of file
diff --git a/project-reports/2024/2024-Q3-Hyperledger-Web3j.md b/project-reports/2024/2024-Q3-Hyperledger-Web3j.md
new file mode 100644
index 00000000..7a999045
--- /dev/null
+++ b/project-reports/2024/2024-Q3-Hyperledger-Web3j.md
@@ -0,0 +1,86 @@
+---
+layout: default
+title: 2024 Q3 Hyperledger Web3j
+parent: 2024
+grand_parent: Project Updates
+---
+
+# Project Health
+
+- The project is in good health.
+- We did 15 releases for all the Web3j Repos fixing several bugs, issues, vulnerabilities and adding new features.
+- Upgraded Gradle to 8.7 and updated all the dependencies.
+- Fixed and simplified Web3j release process.
+- We got 2 Mentees involved in Web3j-android project through Hyperledger Mentorship Program.
+- Set up a fortnightly contributors call.
+
+# Questions/Issues for the TOC
+
+None at the moment.
+
+# Releases
+
+We did release several strong releases for all Web3j repos.
+
+- Web3j Core
+ - v4.9.8-hotfix for android (April 18, 2024)
+ - v4.11.3 (May 1, 2024)
+ - v4.12.0 (May 23, 2024)
+
+- Web3j Gradle Plugin
+ - v4.11.3
+ - v4.11.3-hotfix
+ - v4.12.0
+
+- Web3j Maven Plugin
+ - v4.11.3
+
+- Web3j Unit
+ - v4.11.3
+ - v4.12.0
+
+- Web3j EVM
+ - v4.11.3
+ - v4.12.0
+
+- Web3j Sokt
+ - v0.4.0
+
+- Web3j Solidity Gradle Plugin
+ - v0.4.1
+ - v0.5.0
+
+- Web3j CLI
+ - v1.6.0
+
+# Overall Activity in the Past Quarter
+
+- 100+ commits and 30 PRs merged in Web3j core.
+- 50+ commits and 34 PRs merged across all other Web3j repositories.
+- Fixed bugs, issues, and vulnerabilities, and updated Java and Kotlin versions.
+- Simplified and fixed the release process of Web3j after migrating to the Hyperledger GitHub organization.
+- Upgraded to Gradle 8.7 and updated all dependencies. [Check Announcement](https://medium.com/web3labs/boost-dev-efficiency-security-with-web3js-gradle-8-7-upgrade-d8435a9fb990).
+- Hyperledger Mentorship Program - Mentees started working on web3j-android. [Check project roadmap](https://wiki.hyperledger.org/display/INTERN/Project+Plan+-+Hyperledger+Web3j%3A+Enhancing+Android+Support+with+Updated+web3j-android+Integration).
+- Set up a fortnightly contributors call. A few people joined the call, but it is not very successful yet.
+- The Discord channel was active with questions and announcements of new releases.
+
+# Current Plans
+
+- Fixing Bugs and issues in Web3j.
+- Getting web3j-android fixed for newer Android versions.
+- Adding support for account abstraction in Web3j.
+
+# Maintainer Diversity
+
+- No new maintainers were added this quarter, but several contributors remained active and showed interest towards maintainership.
+- Added guidelines for becoming a [maintainer](https://github.com/hyperledger/web3j/blob/main/MAINTAINERS.md).
+
+# Contributor Diversity
+
+- 6 new contributors in Web3j releases.
+- Contribution from Quant Labs to support decoding of dynamic structs.
+
+# Additional Information
+
+N/A
+
diff --git a/project-reports/2024/images/HLFF_2024_Q2_1.png b/project-reports/2024/images/HLFF_2024_Q2_1.png
new file mode 100644
index 00000000..2c5fca36
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_1.png differ
diff --git a/project-reports/2024/images/HLFF_2024_Q2_2.png b/project-reports/2024/images/HLFF_2024_Q2_2.png
new file mode 100644
index 00000000..0f986e4c
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_2.png differ
diff --git a/project-reports/2024/images/HLFF_2024_Q2_3.png b/project-reports/2024/images/HLFF_2024_Q2_3.png
new file mode 100644
index 00000000..d0a6da7a
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_3.png differ
diff --git a/project-reports/2024/images/HLFF_2024_Q2_4.png b/project-reports/2024/images/HLFF_2024_Q2_4.png
new file mode 100644
index 00000000..eb8867a4
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_4.png differ
diff --git a/project-reports/2024/images/HLFF_2024_Q2_5.png b/project-reports/2024/images/HLFF_2024_Q2_5.png
new file mode 100644
index 00000000..a3bb22c4
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_5.png differ
diff --git a/project-reports/2024/images/HLFF_2024_Q2_stars.png b/project-reports/2024/images/HLFF_2024_Q2_stars.png
new file mode 100644
index 00000000..b5784475
Binary files /dev/null and b/project-reports/2024/images/HLFF_2024_Q2_stars.png differ