Skip to content

Full Nodes Call #32 #22

@Giri-Aayush

Description

@Giri-Aayush

Starknet All Core Devs Meeting #32

Meeting Details


Agenda Items

1. Mainnet v0.14.0 Deployment Status & Timeline Update (Leonardo Lerer)

  • Mainnet deployment timeline following 1-2 week delay confirmation from Call #31
  • Stress testing progress and internal readiness assessment
  • External ecosystem readiness status and remaining blockers
  • Final deployment date announcement and coordination requirements
  • Post-deployment monitoring and support preparation

Reasoning: Leo confirmed in Call #31 that mainnet would be delayed 1-2 weeks from July 28th for both internal and external readiness. Final timeline and deployment coordination needs confirmation.

2. Client Team Production Readiness & Bug Resolution Updates

Pathfinder (Krisztian Kovacs):

  • v0.18 bug fix release status and database migration compatibility
  • WebSocket API enablement ecosystem coordination and documentation updates
  • JSON RPC 0.9 subscription methods implementation progress for pre-confirmed blocks
  • Production stability assessment following testnet experience

Juno (Rodrigo Pino):

  • v0.15 stable release completion status (targeting end of week from Call #31)
  • Tendermint implementation final validation and production readiness
  • P2P specification coordination for consensus network requirements
  • Cross-client testing preparation and coordination with other implementations

Kasar Labs (Trantorian):

  • v0.14.0 sync support implementation completion for testnet compatibility
  • Pre-confirmed block database updates resolution and testing status
  • L2 gas updates integration and stability validation
  • Mainnet deployment readiness assessment

Reasoning: Each team had specific completion targets and technical issues in Call #31 that need follow-up for mainnet readiness.

3. Consensus Implementation & Cross-Client Testing Coordination

Malachite Progress (Adi Seredinschi / Yasmina):

  • v0.4.0 release status and block sync improvements
  • Consensus vs execution testing approach finalization with client teams
  • Pathfinder coordination outcomes following planned discussion
  • Documentation and API refinements based on client team feedback

Cross-Client Consensus Testing:

  • Testing strategy distinction between consensus-level and execution-level interoperability
  • Responsibilities allocation between Malachite team and full node teams
  • Timeline coordination for meaningful cross-client consensus validation
  • P2P specification alignment for consistent implementation across clients

Reasoning: Call #31 established clear testing strategy and responsibilities. Need updates on implementation and coordination progress.

4. P2P Network Evolution & v0.15 Features (Shahak Shama / Guy)

  • DNS infrastructure migration completion status and ecosystem impact
  • v0.15 authentication mechanism protocol specification release
  • Staker-only consensus network implementation requirements and timeline
  • Protocol buffer specifications availability for client team integration
  • Network access control implementation coordination across client teams

Reasoning: Call #31 introduced significant changes to P2P networking with staker authentication. Client teams need detailed specifications and implementation guidance.

5. 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, August 14, 2025, at 11:00 AM UTC. All interested parties are encouraged to join and contribute to the ongoing discussions and development efforts.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions