Starknet All Core Devs Meeting #47
Meeting Details
Agenda Items
1. Starkware Updates (Eitan Moed)
A. Network Stability & Testnet Issue Resolution
- Testnet block hash calculation issue - status of fix and investigation
- Is the new code ready to re-enable on testnet?
- Any incidents on mainnet since Call #46?
Context: In Call #46, Eitan reported testnet downtime and reorg on Feb 25 due to new code allowing sequencers to calculate block hash themselves. One sequencer had discrepancy causing overwrites in proving system. Root cause: Empty state diff caused same hash for consecutive rounds. Fixed by disabling the new block hash calculation code. Mainnet was stable and unaffected.
B. v0.14.2 Integration Timeline
- March 8th target - did it happen or was it delayed?
- If delayed, what's the new timeline?
- RPC RC3 release status (was delayed, expected "by end of day" on Feb 26)
- Client-side proving deployment status
Context: In Call #46, v0.14.2 still targeting March 8th but possible delay due to testnet issue. Eitan said they'd know "by sometime next week" (week of March 3). RPC RC3 was delayed, expected by end of Feb 26. Call #47 is March 12, so we should have clarity now.
C. Decentralized Validation & Propeller
- Propeller version decision - can you share technical details?
- Two-tier networking requirements (normal/above average stake vs high stake) - what are the actual specs?
- Key management API specification - is documentation ready to share?
- Hardware stack optimization progress
- Timeline for validator testing
Context: In Call #46, Eitan announced they've decided on a Propeller version to implement with two networking requirement tiers based on stake. Key management API interface defined. Said they'd bring engineers to discuss details "in the next call" and share key management spec documentation across ecosystem once written up.
2. Client Team Updates
- JSON RPC v0.10.1 RC3 beta - released after spec came out?
- Proof representation changes testing
- WebSocket Ethereum node requirement - implementation status
- Any updates since v0.21.5?
Context: In Call #46, Pathfinder waiting for RPC RC3 release to cut new beta. Already implemented proof representation changes. Upcoming breaking change: Will require WebSocket connection to Ethereum node (removing HTTP/HTTPS auto-conversion). v0.21.5 remains stable.
- RPC v0.10.1 pre-release - updated with RC3?
- New trie implementation - merged and ready for v0.16?
- v0.16 release timeline and breaking changes communication
Context: In Call #46, Juno had pre-release for RPC v0.10.1, will update when RC3 releases. New trie being reviewed for v0.16 (opt-in with migration first). v0.16 will make v0.15 migration mandatory and set RPC v0.10 as default.
- Madara mainnet sync - did the fix work? Is it fully synced?
- SNOS v0.14.1 - any user feedback or production deployment experience?
- Memory optimization PR to Lambda Class VM - merged yet?
- Merkleization parallelization - have teams had a chance to review the details?
Context: In Call #46, Karnot implemented fix for mainnet sync and was testing it. Heemank said "hopefully we'll have an update by the next call...whether we have synced or not." SNOS v0.14.1 merged and released after Dojo approval. Submitted 30% memory reduction PR to Lambda Class VM (still open). Merkleization parallelization showing 2-3x TPS improvement - teammate was going to share details in full node group.
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, March 26, 2026, at 12:00 PM UTC.
All interested parties are encouraged to join and contribute to the ongoing discussions and development efforts.
Starknet All Core Devs Meeting #47
Meeting Details
Agenda Items
1. Starkware Updates (Eitan Moed)
A. Network Stability & Testnet Issue Resolution
Context: In Call #46, Eitan reported testnet downtime and reorg on Feb 25 due to new code allowing sequencers to calculate block hash themselves. One sequencer had discrepancy causing overwrites in proving system. Root cause: Empty state diff caused same hash for consecutive rounds. Fixed by disabling the new block hash calculation code. Mainnet was stable and unaffected.
B. v0.14.2 Integration Timeline
Context: In Call #46, v0.14.2 still targeting March 8th but possible delay due to testnet issue. Eitan said they'd know "by sometime next week" (week of March 3). RPC RC3 was delayed, expected by end of Feb 26. Call #47 is March 12, so we should have clarity now.
C. Decentralized Validation & Propeller
Context: In Call #46, Eitan announced they've decided on a Propeller version to implement with two networking requirement tiers based on stake. Key management API interface defined. Said they'd bring engineers to discuss details "in the next call" and share key management spec documentation across ecosystem once written up.
2. Client Team Updates
Pathfinder (Krisztian Kovacs)
Context: In Call #46, Pathfinder waiting for RPC RC3 release to cut new beta. Already implemented proof representation changes. Upcoming breaking change: Will require WebSocket connection to Ethereum node (removing HTTP/HTTPS auto-conversion). v0.21.5 remains stable.
Juno (Rodrigo Pino)
Context: In Call #46, Juno had pre-release for RPC v0.10.1, will update when RC3 releases. New trie being reviewed for v0.16 (opt-in with migration first). v0.16 will make v0.15 migration mandatory and set RPC v0.10 as default.
Karnot (Heemank Verma)
Context: In Call #46, Karnot implemented fix for mainnet sync and was testing it. Heemank said "hopefully we'll have an update by the next call...whether we have synced or not." SNOS v0.14.1 merged and released after Dojo approval. Submitted 30% memory reduction PR to Lambda Class VM (still open). Merkleization parallelization showing 2-3x TPS improvement - teammate was going to share details in full node group.
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, March 26, 2026, at 12:00 PM UTC.
All interested parties are encouraged to join and contribute to the ongoing discussions and development efforts.