Skip to content

TSCCall20260203

Jump to bottom
itsbrandond edited this page Feb 9, 2026 · 10 revisions

Hiero Technical Steering Committee Meeting

TL;DR: The TSC approved the creation of the new Hiero Identity Platform project (name TBD). The group reviewed HIP-1137 and HIP-1357 (vote planned next week), discussed consolidating SDK committer/maintainer teams with CODEOWNERS safeguards, and kicked off a plan for “junior committer” onboarding calls to reduce maintainer burden.

Details

Organization: Hiero
Date: Feb 3rd 2026
Time: 10:00am ET (meeting ran ~1 hour)
Recording: https://zoom.us/rec/share/Mh8aTC_HurfCin7sjpt25WBc8bHevC8ZEUJ6XYiI58mhC3I0OXHW9dHc-gFzxPCL.Ip_DCmVIRtbsyxgc

TSC Attendees

  • Brandon Davenport
  • Georgi Lazarov
  • Hendrik Ebbers
  • Michael Kantor
  • Milan Wiercx van Rhijn
  • Stoyan Panayotov
  • Alexander Popowycz

Guests

  • Angelina Ceppaluni
  • Alexander Shenshin
  • Bhargava Tejas
  • Diane Mueller
  • Jake
  • Jessica Gonzalez
  • Jessie Ssebuliba
  • Joseph Sinclair
  • Keith Kowal
  • louis's Notetaker
  • Mark Blackman
  • Nana Essilfie-Conduah
  • Noah
  • Pavel Borisov
  • Priyanshu Yadav
  • Renata Toktar
  • Robert Walworth
  • Sophie Bulloch

Agenda Items

Guests

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:
https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero

Code of Conduct

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:

Meeting Summary

  • Opening / format reminder

    • Hendrik reiterated the meeting is public and covered Linux Foundation antitrust and Code of Conduct expectations.
    • Hendrik provided a verbal recap of the prior TSC meeting (rather than approving prior minutes in-meeting).

  • Community updates & events

    • Jake shared an upcoming blockchain/open-source event in Cape Town, South Africa, noted as moved to Feb 14 (date mentioned as tentative). He also described multiple February hackathons, including one focused on the Hiero CLI, and stated another hackathon has $250,000 in prizes with $13,000 allocated toward a Hiero-related bounty (details still being defined).
    • Michael Kantor promoted a weekly “HOLxAI” space (reported ~300+ listeners) and noted an upcoming $100 pitch competition, themed around an “OpenClaw / multiplook” topic (term unclear from transcript).

  • LFDT Maintainer Days

    • Hendrik, Jessica, and others shared positive feedback on LFDT Maintainer Days (and Member Summit).
    • Hendrik and Jessica reported they recorded most sessions and expect video publication in the near future; topics highlighted included Linux Foundation mentorship approaches, “good first issues,” and multiple Hiero-related sessions/presentations.
    • Jessica requested feedback from attendees to pass along to LFDT and gave a shout-out to Andrew’s cross-project brainstorming session.

  • HIPs (presentations; vote planned next week)

    • HIP-1137 (presented by Joseph Sinclair): “Block Node discoverability via on-chain registry”
      • Goal: enable on-chain discovery for non-consensus node/service types (examples discussed: block nodes, mirror nodes, RPC relays), instead of relying on off-chain knowledge.
      • Proposed: a registry with create/update/delete transactions; endpoints include IP/domain + port + TLS requirement; nodes have an admin key, type, description, and one or more endpoints.
      • Discussion: possibility of a mirror-node query endpoint; using HCS for this was considered but rejected for use cases requiring data to be in state.
    • HIP-1357 (presented by Nana Essilfie-Conduah): “Tier 1 Block Node Operation Rewards”
      • Goal: reward Tier 1 block node operators via an on-chain mechanism, leveraging the existing node rewards process.
      • Proposal: if a consensus node operator is eligible for consensus node rewards and has associated Tier 1 block nodes, then add block node rewards on top during the rewards process.
      • Key discussion points:
        • Reward precedence and funding constraints: Alex raised questions about reward distribution if the rewards account balance is insufficient and whether consensus rewards should be prioritized or whether block-node rewards should be discounted/deferred.
        • Nana agreed to review and circle back on configurability/policy implications (Hiero vs. Hedera operational considerations were noted).
        • Association mechanism: Keith asked how the network verifies a consensus node operator is also running a block node; Nana explained the linkage is via an association from the consensus node to registered nodes (per HIP-1137).
    • Next steps: TSC to review and return next week for voting (or vote asynchronously if needed).

  • Project proposal vote: “Hiero Identity Platform” (issue #281)

    • The TSC discussed separating the project approval from the project naming.
    • Decision: the TSC approved creating the project (with the name to be finalized by maintainers; the TSC retains the right to object to an unsuitable name).
    • Vote outcome: 7 “yes” votes recorded (including a “yes” from Michael Kantor in chat).

  • Deferred / moved topics

    • HCS integration in HIP repository: deferred due to key stakeholders not being present.
    • Release/package namespace workflow (governance issue #507): not reached in the available time.
    • Additional AOB items listed in the agenda (GFI label consistency, governance for Python SDK) were not discussed due to time.

  • Maintainer/committer group restructuring (SDKs; and potentially DID)

    • Hendrik proposed consolidating multiple language-specific SDK maintainer/committer GitHub teams into:
      • one SDK maintainers group, and
      • one SDK committers group,
      • while using CODEOWNERS to ensure language-appropriate review requirements where needed.
    • Sophie and Robert supported the collaboration benefits (coverage across time zones, sharing best practices) and requested clarity on how CODEOWNERS would be configured to avoid unintended merge authority across languages.
    • Hendrik requested Robert add this as an agenda item for the next SDK community call to walk through a concrete example.

  • Onboarding & training new committers/maintainers (AOB)

    • Sophie highlighted strong contributor growth (notably in Python SDK) and the burden/lead time (~6 months) to develop new committers/maintainers, especially with many new contributors.
    • Discussion focused on reducing maintainers’ one-on-one overhead and creating structured pathways.
    • Proposed direction: establish “junior committer calls” (and potentially additional time zones) to support onboarding, surface contributor interest, and scale mentorship/community engagement.

Key Decisions

  • Approved: Create the new project proposed as “Hiero Identity Platform” (final name TBD), based on a TSC vote with 7 recorded “yes” votes.
  • Agreed: HIP-1137 and HIP-1357 will be brought back next week for final voting after additional review time.

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.

📘 Agendas and Minutes

TSC Call

Community Call

Maintainers Monthly Meeting

📘 ARCHIVED

Marketing / Community Engagement Meeting

SDK Community Call

Hiero Mentorship

Solo Community Call

Solo Action Community Call

Website Community Call

Hiero Community Management

Identity Community Call

Clone this wiki locally