Repository navigation
TSCCall20260127
TL;DR: The TSC heard a proposal to onboard a new “Hiero Identity Platform” project (end-to-end identity apps like a mobile wallet + backend agency) and agreed to defer the approval vote to next week while the team refines naming and begins onboarding checks. The group also discussed upcoming HIP timelines (Pectra HIPs likely within ~2 weeks) and a plan to coordinate ideas for the Linux Foundation mentorship program.
Organization: Hiero
Date: Jan 27, 2026
Time: 10:00 AM ET
Recording: https://zoom.us/rec/share/s7YQ3qUhIvaeplynd94z4vmOX-5R7RuhoHmi2PYDraU_KmGhG9J7VMzDwQbQf-YP.XGf2LqqzY9MJt4Ta
- Brandon Davenport
- Hendrik Ebbers
- Alex Popowycz
- Georgi Lazarov
- Milan Wiercx van Rhijn
- Richard Bair
- Alexander Shenshin
- Angelina Ceppaluni
- Bhargava Tejas
- Daniel Swid
- Jessie Ssebuliba
- Keith Kowal
- louis's Notetaker
- Luke Forrest
- Michael Garber
- Pavel Borisov
- Raphael Messian
- Renata Toktar
- Short overview of last TSC call
- Any Updates/Events from Communities or members?
- Reminder to attend public community calls + bring more activity into Hiero Discord channels. (Encourage others! 💪)
- HIPs
- Project Proposal: Hiero Identity Platform
- Any other business (AOB)
As every Hiero meeting the TSC meeting is a public meeting and everybody can attend it.
You can find all the information about the TSC meetings and all other Hiero meetings in our public calender.
As in every meeting we start with a short notice of the antitrust policy of Linux Foundation and an introduction of our Code of Conduct.
-
Opening + context
- Hendrik opened the meeting from New York during LF Decentralized Trust-related events (maintainer days / member summit activities), noting some travel disruption due to a winter storm.
- Reminder that Hiero meetings are public, with meeting info/recordings accessible via the community calendar, and that participants are encouraged to speak up during calls.
-
Overview of prior TSC meeting
- Recapped a guest presentation (Linux Foundation) on a mentorship program that can provide structure and funding for mentored project work.
- Noted that HIP-1313 was approved via asynchronous vote.
- Ongoing discussion about HIP repository structure (including how HashCraft-related topics fit) was paused and will be revisited when Michael Kantor is present.
-
Community updates / reminders
- Encouraged participation in public community calls and increased activity in the Hiero Discord channels.
-
HIPs status / timeline
- Michael Garber shared that HIP-1340 and HIP-1341 (“Pectra” HIPs) are expected to come to the TSC soon, likely within ~2 weeks for review, and this timing was acknowledged as reasonable.
-
Project Proposal: “Hiero Identity Platform” (DSR)
-
Alexander Shenshin (DSR) and Renata Toktar (DSR) presented a proposal to contribute a net-new project consisting of end-to-end identity applications (not primarily libraries), including:
- A mobile wallet and an agency/backend service for issuing/verifying verifiable credentials.
- A modular/white-label approach intended to reduce adoption friction by providing a working reference implementation.
- Alignment with multiple VC-related standards/protocols and broader identity ecosystem interoperability (as described in the proposal/presentation).
- The presenters emphasized the need to intentionally build community around an initially contributed codebase and expressed intent to adopt contribution practices like Good First Issues.
- Current status / licensing: DSR stated the codebase has been private to date (therefore limited “open community metrics” so far) and is intended to be open sourced; Apache 2.0 licensing was discussed as the expectation, with standard Hiero onboarding checks to follow (license/DCO/etc.).
-
Alexander Shenshin (DSR) and Renata Toktar (DSR) presented a proposal to contribute a net-new project consisting of end-to-end identity applications (not primarily libraries), including:
-
Discussion: structure, dependencies, and community contribution
- Repo structure discussion covered whether to start with one repository vs multiple repositories over time:
- DSR preference: begin with one repo to reduce initial complexity, then split if/when growth requires it; the stack is largely JavaScript-based, with React Native including some native modules.
- TSC members noted the need to consider clarity and navigability, especially given existing identity SDK repositories and potential future growth.
- Clarified that this proposal is additive (a new repo/project) and does not replace existing identity repos; the new project would likely consume existing SDKs as dependencies rather than merging them.
- Community contribution pathways discussed included Good First Issues, UI-focused tasks for newcomers, and potential mentorship-program alignment.
- Repo structure discussion covered whether to start with one repository vs multiple repositories over time:
-
Naming
- Multiple members raised concern about using a generic name like “Hiero Identity Platform,” given the likelihood of additional identity-related projects in the future.
- The group leaned toward using a more distinctive project name to avoid namespace confusion and overlapping acronyms.
-
Mentorship program coordination
- Hendrik proposed organizing a community touchpoint to gather a small set of strong mentorship project ideas to submit in February, leveraging lessons learned from other projects’ mentorship success.
- No vote held during this meeting on the “Hiero Identity Platform” proposal.
- The TSC intends to vote next week if quorum is present; otherwise, an asynchronous vote will be initiated next week.
- Agreement in principle to continue refining project naming to reduce future confusion and enable clearer differentiation.
Prepared by: Brandon Davenport, Dir of Product, Hgraph
All Hiero community meetings must follow Linux Foundation's antitrust policy and adhere to our Code of Conduct.
- 2024-2025
- 2026-01-06
- 2026-01-13
- 2026-01-20
- 2026-01-27
- 2026-02-03
- 2026-02-10
- 2026-02-17
- 2026-02-24
- 2026-03-03
- 2026-03-10
- 2026-03-17
- 2026-03-24
- 2026-03-31
- 2026-04-07
- 2026-04-14
- 2026-04-21
- 2026-04-28
- 2026-05-12
- 2026-05-19
- 2026-05-26
- 2026-06-02
- 2026-06-09
- 2026-06-16
- 2026-06-23
- 2026-06-30
- 2026-07-07
- 2026-07-14
- 2026-07-21
- 2026-07-28
- 2026-08-04
- 2026-08-11
- 2026-08-18
- 2026-08-25
- 2026-09-01
- 2026-09-08
- 2026-09-15
- 2026-09-22
- 2026-09-29
- 2026-10-06
- 2026-10-13
- 2026-10-20
- 2025-11-11
- 2025-11-25
- 2025-12-02
- 2025-12-09
- 2026-01-20
- 2026-02-03
- 2026-02-17
- 2026-03-03
- 2026-03-17
- 2026-03-31