TSCCall20260310

Hiero Technical Steering Committee Meeting

TL;DR: The TSC discussed community growth and engagement, a near-term governance fix for the Swift SDK’s single-maintainer bottleneck, updates to the LFDT mentorship program, an x402 ecosystem presentation from Lindsay Walker, and decided to defer a vote on HIP-1398 pending revisions and clarification.

---

Details

Organization: Hiero
Date: March 10, 2026
Time: 10:00 AM ET
Recording: Zoom recording

---

TSC Attendees

• Hendrik Ebbers
• Richard Bair
• Stoyan Panayotov
• Alexander Popowycz
• Milan Wiercx van Rhijn
• Brandon Davenport

Guests

• Sophie
• Andrew Brandt
• Angelina Ceppaluni
• Bhargava Tejas
• Daniel Ntege
• Diane Mueller
• Jessica Gonzalez
• Jessie Ssebuliba
• Joseph Sinclair
• Keith Kowal
• Lindsay Walker
• Mark Blackman
• Michael Garber
• Noah
• Pavel Borisov
• Raphael
• Robert Walworth
• Roger Barker

---

Agenda Items

1. Short overview of last TSC call
2. Community/member updates and events
3. Reminder to attend public community calls and increase activity in Hiero Discord channels
4. Discussion of governance issue #544
5. Update on the mentorship program (wiki page)
6. Update on x402 by Lindsay Walker
7. HIPs
8. Any other business

Guests

As with every Hiero meeting, the TSC meeting 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 TSC opened with a reminder of the Linux Foundation antitrust policy and the LF Decentralized Trust Code of Conduct.

---

Meeting Summary

• Hendrik opened by reminding attendees that Hiero meetings are public, recorded, and listed on the community calendar.
• A brief recap of the prior TSC meeting was given, including Hart Montgomery’s discussion on the future direction of LF Decentralized Trust and distributed ledger projects, as well as earlier mentorship-program discussion.
• Sophie announced a new blog post on the Issue Progression Initiative (IPI), describing a lightweight process for labeling issues by difficulty to create clearer contributor on-ramps and improve contributor progression.
• Hendrik also highlighted Hiero Enterprise Java as a newly added project for developers working in Java enterprise environments such as Spring, MicroProfile, and Jakarta.

Governance issue #544: single-maintainer repository risk

• The TSC discussed the risk created when a repository has only one maintainer able to approve maintainer-level pull requests.
• The immediate example was the Swift SDK, where Robert Walworth may be left as the sole maintainer after role changes.
• Hendrik proposed a short-term mitigation: temporarily add an experienced maintainer or committer from another SDK so Swift pull requests can receive meaningful review and approval.
• Robert agreed the added reviewer should have real SDK experience and not be a rubber stamp.
• Longer term, Hendrik noted that consolidating SDK maintainer/committer groups across SDKs could address this class of problem more broadly.
• Alex raised a broader governance question about repository oversight and whether the TSC should periodically review a dashboard showing repository health, activity, and maintainer coverage.
• Hendrik and Diane pointed to LFX Insights and OpenSSF Scorecards as existing tools, while Sophie noted that more tailored contributor and governance analytics would still be useful.

Mentorship program update

• Hendrik reported that two Hiero mentorship topics had been submitted into the LFDT mentorship process for review:
  • SDK Version 3
  • Hiero Enterprise Java
• A third proposal is planned in collaboration with Web3j, focused on compatibility, tutorials, and improving the developer experience for using Web3j with a Hiero-based network.
• The overall tone was positive, with participants viewing this as a strong start for Hiero’s first cycle in the mentorship program.

x402 update from Lindsay Walker

• Lindsay Walker presented an overview of x402, explaining it as a payment flow based on the HTTP 402 Payment Required pattern.
• The core concept discussed was the use of a facilitator to reduce payment friction by verifying payment payloads, sponsoring fees where appropriate, settling transactions on-chain, and reimbursing merchants in an acceptable asset.
• Lindsay explained that Hedera’s approach can reduce a double-spend risk by explicitly designating the intended facilitator in the transaction.
• She also noted that Hedera’s payment scheme had been accepted into the Coinbase x402 specification process and that a reference implementation was in progress.
• Questions covered:
  • who determines settlement behavior and fee handling across supported assets
  • the double-spend scenario for partially signed transactions
  • whether auto-account creation is handled for payers
  • whether facilitator code or reference implementations might become more visible to the ecosystem
• Hendrik asked attendees to provide feedback in chat on whether short guest presentations like this should remain part of regular TSC meetings.

HIPs

• Mark Blackman requested a vote on HIP-1398, which had been presented during the prior meeting.
• Discussion focused on whether the proposal mixed technical ceremony design with Hedera-specific governance and operational details.
• Diane asked for clearer treatment of participant awareness, governance sign-off, and whether participants would be publicly listed.
• Alex raised concerns that the HIP should remain generic enough for broader Hiero use and avoid overly Hedera-specific implementation details.
• Keith noted that many of the governance and operational concerns appeared more appropriate for Hedera TechCom than for the Hiero TSC.
• The group agreed not to vote during this meeting and instead send the proposal back for revision and clarification.

---

Presentations

Lindsay Walker: x402 update

Lindsay provided an overview of x402 and the facilitator model for reducing payment friction in crypto-based micropayments. The presentation focused on how facilitators verify and settle payments, how Hedera can reduce double-spend risk in this model, and what it would take for broader ecosystem participation through facilitator services and reference implementations.

---

Key Decisions

• The TSC aligned on the need for a short-term mitigation to avoid single-maintainer bottlenecks in repositories such as the Swift SDK.
• No formal vote was taken on HIP-1398; the proposal will be revised and brought back after clarification.
• The TSC reinforced the importance of better repository oversight and contributor analytics, though no formal new reporting process was adopted during this meeting.

---

Prepared by: Brandon Davenport