-
Notifications
You must be signed in to change notification settings - Fork 99
TSCCall20260210
TL;DR: The TSC unanimously approved HIP-1137 (Block Node discoverability via on-chain registry) and HIP-1357 (Tier 1 Block Node Operation Rewards). The group also reviewed the proposed Hiero 2026 Project Goals and agreed to continue HIP implementation tracking work (starting with SDKs) in the SDK forums, with a future TSC discussion planned on moving HIP Q&A out of the weekly TSC agenda.
Organization: Hiero
Date: Feb 10, 2026
Time: 10:00–11:00 ET
Recording: https://zoom.us/rec/share/P7c18f-fp5HUcDklF71tKL19bFtb0U86w2Hqv16MaDEi4gi04L08_srDoQjow6OF.pdGe3NSZGXlDZzej
- Hendrik Ebbers
- Richard Bair
- Stoyan Panayotov
- Alexander Popowycz
- Michael Kantor
- Milan Wiercx van Rhijn
- Georgi Lazarov
- Jessica Gonzalez (The Linux Foundation)
- Sophie Bulloch
- Mark Blackman
- Keith Kowal
- Nana Essilfie-Conduah
- Angelina Ceppaluni
- Robert Walworth
- Lindsay Walker
- Michael Garber
- 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
- Voting: HIP-1137: Block Node discoverability via on-chain registry
- Voting: HIP-1357: Tier 1 Block Node Operation Rewards
- Hiero 2026 Project Goals summary (15 min)
- Discussion: HCS integration in HIP repository
- Discussion: Workflow to define namespaces of releases/packages fort publishing
- Update: Hiero Community Management
- Any other business (AOB)
As with all Hiero meetings, the TSC meeting is a public meeting and anybody can attend. You can find information about TSC meetings and other Hiero meetings on the public calendar: https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero
As in every meeting, the meeting opened with a reminder of the Linux Foundation antitrust policy and the LF Decentralized Trust Code of Conduct:
- Antitrust policy: https://www.linuxfoundation.org/legal/antitrust-policy
- Code of Conduct: https://www.lfdecentralizedtrust.org/code-of-conduct
-
Opening / recap of prior week
- Hendrik Ebbers opened the meeting, reminded attendees about the public meeting calendar and how to access past recordings/minutes.
- Recapped that the prior TSC meeting included presentations for HIP-1137 and HIP-1357, with votes scheduled for this week.
- Noted that the TSC previously approved onboarding a new identity project, now referred to as the Heka Identity Platform, and that the transfer work was in progress.
-
Community updates / events
- Hendrik shared an upcoming event: Hedera Dev Day (the following week), including a Hiero booth to support community questions and first contributions (e.g., first PRs).
-
HIP voting
- The TSC held votes on two HIPs presented the prior week:
- HIP-1137 (Block Node discoverability via on-chain registry): Unanimously approved by voting members present.
- HIP-1357 (Tier 1 Block Node Operation Rewards): After Q&A and clarifications on reward mechanics, unanimously approved by voting members present.
- Additional context discussed for HIP-1357:
- Tier 1 block nodes are treated as integral to consensus-node operation rather than a separate “lower priority” class for rewards.
- The group discussed reward pooling behavior and why incentives should align consensus node operators with running (and maintaining) Tier 1 block nodes.
- Richard Bair provided a deeper explanation of the trust and incentive model around Tier 1 block nodes, including why Tier 1 nodes are assumed to maintain full history and why rewarding arbitrary block nodes is non-trivial without deterministically proving “honest storage.”
- The TSC held votes on two HIPs presented the prior week:
-
HIP implementation tracking / visibility
- Sophie Bulloch asked about a tracker to monitor HIP implementation progress across codebases (initially motivated by SDK implementation visibility).
- Angelina Ceppaluni shared a draft tracking board that maps HIPs to implementation status across multiple SDKs (with Java used as an early baseline, and additional SDK coverage planned).
- The group agreed the tracker should be used as a starting point in the SDK meetings, and revisited later for broader coverage (e.g., consensus node, mirror node).
-
Process improvement request: HIP Q&A outside weekly TSC
- Sophie Bulloch requested discussion of moving deeper HIP Q&A and discussion to a separate meeting to preserve more TSC time for broader community topics.
- Hendrik Ebbers agreed to add this as a future TSC agenda item (planned for two weeks out, given availability constraints).
-
Hiero 2026 Project Goals
- Jessica Gonzalez presented the proposed Hiero 2026 Project Goals, requesting TSC and maintainer feedback in the GitHub discussion.
- The goals were organized into eight themes:
- Project Participation & Engagement
- Security & Supply Chain Transparency
- Core Components & Sub-Project Roadmaps
- Specifications Stewardship & Reference Implementations
- Training
- Ecosystem Adoption & Integrations
- Innovation & Future-Readiness
- Cross-Project Collaboration Targets
- Lindsay Walker highlighted work relevant to the innovation goals and requested the link to contribute context and potential standards alignment.
-
AOB / scheduling
- The group briefly discussed whether to cancel the next week’s meeting due to Hedera Dev Day attendance. The outcome was to keep the meeting, expecting a lighter agenda and optional attendance for those traveling.
-
Topics not reached due to time
- HCS integration in the HIP repository
- Release/package namespace workflow for publishing
- Hiero community management update
- Approved: HIP-1137 (Block Node discoverability via on-chain registry) — unanimous approval among voting members present.
- Approved: HIP-1357 (Tier 1 Block Node Operation Rewards) — unanimous approval among voting members present.
- Process direction: Start HIP implementation tracking in SDK meetings using Angelina’s draft board as a baseline; revisit expansion later.
- Agenda planning: Add a future TSC agenda item (two weeks out) to discuss creating a separate venue for HIP Q&A / deeper discussion.
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.