Repository navigation
Sdk20251103
Rob Walworth edited this page Dec 1, 2025
·
1 revision
- API design PRs
- HIP-1313 High Volume Entities
- Rob introduced the SDK v3 sandbox
- Folder in the SDK collaboration hub to come up with ideas and suggestions for what a v3 SDK will look like
- Invited discussion and contributions to the documents and code that currently lives there
- Keith brought up questions about the need for a v3 SDK
- Rob mentioned a strong desire to redesign some of the SDK APIs to allow for less user error and better intuitive use, as well as clean the slate of deprecated APIs
- Rob went through current open PRs for design doc API guidelines
- Described what is already there and approved, as well as the improvements being made
- Adding extra type annotations
- "extends" keyword for inherited types
- Described what is already there and approved, as well as the improvements being made
- Ivan went over his design doc for HIP-1313
- He brought up a concern about defining the high volume throttle boolean flag in the base
Transaction, or only doing it in the transactions where high-volume throttles are enabled- Rob and Ivan both agreed it should be defined at the
Transactionlevel, so that enabling transactions later for high-volume throttles wouldn't require an SDK upgrade
- Rob and Ivan both agreed it should be defined at the
- Testing this HIP brought about questions as to how to test without introducing flakiness to SDK CI workflows
- Testing based on speed can be tough because some CI runners may experience heavier traffic at different times, therefore introducing flakiness
- The idea of a custom build was brought up, but that would require a separate CI job
- The HIP is still a couple of months away from being introduced, so there's time to figure this out
- Team will wait until consensus node has made more progress on this
- He brought up a concern about defining the high volume throttle boolean flag in the base
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