Starknet All Core Devs Meeting #51
Meeting Details
Agenda Items
1. Starkware Updates (Ohad Barta)
A. Network Health
- Any incidents or issues since Call #50
Context: In Call #50, Ohad reported testnet reorg on April 19 caused by a Cairo Native bug, which was fixed before the call. Mainnet remained stable through the v0.14.2 upgrade on April 20.
B. v0.14.3 Planning
- Final feature package and integration timeline
- Pre-confirmed transactions protocol - any updates with full node teams?
Context: In Call #50, Ohad said v0.14.3 timeline was being re-evaluated. Confirmed features include SNIP-35 (dynamic prices), cost optimizations, and pre-confirmed transaction protocol changes being worked on with full node teams. Ohad promised a more final answer "in two weeks" (this call).
2. Client Team Updates
Pathfinder (Chris)
- v0.22.3 (max L2 gas limit fix) - adoption and stability?
- Pre-confirmed API extensions for v0.14.3 - progress update?
- Any new releases since Call #50?
Context: In Call #50, Pathfinder released v0.22.3 with max L2 gas limit bug fix (tip accounting corrected, discovered by Starkware). No issues reported on previous releases (v0.22.1 and April 7 Blockifier bump). Started working on pre-confirmed API extensions for v0.14.3 and additional server pre-confirmed work beyond that.
- v0.16 adoption and stability
- State pruning for validators - on track for end of May release?
Context: In Call #50, Juno released v0.16 with breaking changes - performs mandatory migration (40 minutes to 1 hour depending on SSD). Includes max L2 gas limit fix caught by Starkware. Working on state pruning for validators to reduce disk space, targeting release before end of May.
- Madara and SNOS v0.14.2 releases - shipped after reviews completed?
- Technical debt cleanup progress
Context: In Call #50, Karnot's v0.14.2 releases were pending reviews - waiting for Dojo team review on SNOS v0.14.2 PR and internal reviews for Madara/orchestrator updates. Heemank committed to releasing them before Call #51. Working on technical debt cleanup.
3. AOB (Any Other Business)
Note: These Starknet All Core Devs Calls occur bi-weekly at the same time. The next call is scheduled for Thursday, May 21, 2026, at 11:00 AM UTC.
All interested parties are encouraged to join and contribute to the ongoing discussions and development efforts.
Starknet All Core Devs Meeting #51
Meeting Details
Agenda Items
1. Starkware Updates (Ohad Barta)
A. Network Health
Context: In Call #50, Ohad reported testnet reorg on April 19 caused by a Cairo Native bug, which was fixed before the call. Mainnet remained stable through the v0.14.2 upgrade on April 20.
B. v0.14.3 Planning
Context: In Call #50, Ohad said v0.14.3 timeline was being re-evaluated. Confirmed features include SNIP-35 (dynamic prices), cost optimizations, and pre-confirmed transaction protocol changes being worked on with full node teams. Ohad promised a more final answer "in two weeks" (this call).
2. Client Team Updates
Pathfinder (Chris)
Context: In Call #50, Pathfinder released v0.22.3 with max L2 gas limit bug fix (tip accounting corrected, discovered by Starkware). No issues reported on previous releases (v0.22.1 and April 7 Blockifier bump). Started working on pre-confirmed API extensions for v0.14.3 and additional server pre-confirmed work beyond that.
Juno (Rodrigo Pino)
Context: In Call #50, Juno released v0.16 with breaking changes - performs mandatory migration (40 minutes to 1 hour depending on SSD). Includes max L2 gas limit fix caught by Starkware. Working on state pruning for validators to reduce disk space, targeting release before end of May.
Karnot (Heemank Verma)
Context: In Call #50, Karnot's v0.14.2 releases were pending reviews - waiting for Dojo team review on SNOS v0.14.2 PR and internal reviews for Madara/orchestrator updates. Heemank committed to releasing them before Call #51. Working on technical debt cleanup.
3. AOB (Any Other Business)
Note: These Starknet All Core Devs Calls occur bi-weekly at the same time. The next call is scheduled for Thursday, May 21, 2026, at 11:00 AM UTC.
All interested parties are encouraged to join and contribute to the ongoing discussions and development efforts.