TSCCall20260324

Hiero Technical Steering Committee Meeting

TL;DR: The TSC reviewed community updates, discussed LF Decentralized Trust sub-project naming guidance and internal artifact namespace consistency, and heard a preview of HIP-1193 related to mirror node changes for the move from record streams to block streams. The TSS ceremony HIP was reclassified as informational, so no TSC vote is needed on that item.

---

Details

Organization: Hiero
Date: March 24, 2026
Time: 10:00 AM ET
Recording: https://zoom.us/rec/share/-Oba-KqNGOUzK4xjGjFm3EnsDsmUi9-Hnj4N3Fxq9Ee8Fsso6moUYhCwE03kzpl5.ZfNLgZ-g6m2QApfh

---

TSC Attendees

• Brandon Davenport
• Hendrik Ebbers
• Michael Kantor
• Milan Wiercx van Rhijn
• Richard Bair
• Stoyan Panayotov

Guests

• Diane Mueller
• Joseph Sinclair
• Alexander Shenshin
• Angelina Ceppaluni
• Bhargava Tejas
• David Boswell
• Jessica Gonzalez
• Jessie Ssebuliba
• Kiran Pachhai
• Lindsay Walker
• Mark Blackman
• Mike Cave
• Pavel Borisov
• Roger Barker

---

Agenda Items

1. Short overview of last TSC call
2. Community updates and events
   • Rare Evo 2026 workshop opportunity
3. Reminder to attend public community calls and increase activity in Hiero Discord channels
4. David Boswell: Hiero sub-project naming guidelines and related governance update
   • https://github.com/hiero-ledger/governance/pull/598/changes
5. HIPs
   • TSS ceremony
   • HIP-1193 discussion
6. Any other business

Public Participation

As with every Hiero TSC meeting, this is a public meeting and everybody can attend it. You can find information about TSC meetings and other Hiero meetings in the public calendar.

Code of Conduct

As in every meeting, the call opened with a reminder of the Linux Foundation antitrust policy and the LF Decentralized Trust Code of Conduct.

---

Meeting Summary

• Hendrik opened the meeting with a reminder that Hiero meetings are public, pointed attendees to the public calendar, and noted that recordings and AI-generated minutes are available for missed meetings.
• A brief recap of the prior TSC call covered three main topics: the TSS ceremony HIP, the mentorship program final submissions, and the Hiero Hackers initiative plus analytics reporting.
• Jessica Gonzalez reminded the community that Rare Evo 2026 is an opportunity for Hiero maintainers and contributors to run a technical workshop, and invited interested participants to contact her.
• Hendrik highlighted the new “Hiero Links of the Week” blog posts as a way to share community updates more broadly.
• Angelina Ceppaluni announced that a new TSC tab has been added to the Hiero website to centralize TSC information and make site maintenance easier as the TSC evolves.
• David Boswell presented LFDT guidance on sub-project naming, explaining that using “Hiero” as a prefix in sub-project names helps with trademark protection and reduces the risk of future renaming conflicts.
• The group discussed how that guidance should apply in practice, especially for existing repos and product-style names such as HECA and Solo. The consensus was that the first visible usage should ideally include the Hiero prefix, while existing repo names should not be changed if doing so would be disruptive.
• Jessica offered to help update README files for affected repos, and the group noted this guidance should also be incorporated into project proposal templates going forward.
• Hendrik then raised a related internal naming question around published artifact namespaces across package ecosystems such as NPM, Rust, Python, and Maven.
• Michael Kantor emphasized the value of short package names for usability and discoverability, but Hendrik and others noted that fragmented namespace ownership can introduce confusion and supply-chain risk.
• Richard Bair agreed that the supply-chain risk argument was compelling, and Hendrik said he would follow up on consolidating the NPM approach where possible and continue work on Maven namespace setup under org.hiero.
• Mark Blackman presented HIP-1193, a mirror node-focused proposal describing the transition from record streams to block streams, including cryptographic credentials, block node connectivity, fallback bucket access, and mirror node operational considerations during cutover.
• Mark clarified that the TSS ceremony HIP has been changed to an informational HIP, so it no longer requires a TSC vote.
• During discussion of HIP-1193, Diane asked about timing; Mark said the target window is late Q2 to Q3.
• Diane also asked whether the HIP covered cutover criteria, and Mark said the document is intentionally high-level and focused on mirror node operators rather than Hedera-specific rollout details.
• Mike Cave asked whether block streams will become the default recommendation for future Hiero network deployments, and Mark and Richard confirmed that the ecosystem direction is toward blocks, block streams, and block nodes.
• Diane asked whether this would eventually archive the Mirror Node sub-project; Richard clarified that mirror nodes will continue to play an indexing and API-serving role, distinct from consensus nodes and block nodes.
• No additional business was raised, and the meeting adjourned early.

---

Presentations

David Boswell: Sub-project Naming Guidance

David walked through new LFDT naming guidance intended to help projects choose sub-project names that are legally safer and more consistent from a branding perspective. The discussion focused on when the “Hiero” prefix should be used, how to handle existing repositories, and how to avoid unnecessary disruption while still improving compliance.

Mark Blackman: HIP-1193

Mark introduced HIP-1193 as a mirror node-oriented HIP covering the operational implications of migrating from record streams to block streams. The presentation focused on what mirror node operators need to understand and prepare for ahead of the cutover.

---

Key Decisions

• The TSS ceremony HIP will be treated as an informational HIP and does not require a TSC vote.
• Sub-project naming should use the Hiero prefix in the first visible/reference usage where appropriate to strengthen trademark protection.
• Existing repositories should generally avoid disruptive renames; README and documentation updates are the preferred near-term fix.
• The project proposal/template process should be updated to remind submitters about naming guidance up front.
• The TSC viewed namespace consistency across published artifacts as important, with supply-chain risk cited as a strong reason to prefer consolidated namespaces where possible.
• HIP-1193 will return for TSC vote consideration at a subsequent meeting after members have additional time to review it.

---

Prepared by: Brandon Davenport, Dir of Product, Hgraph