Skip to content

Full Nodes Call #37 #27

@Giri-Aayush

Description

@Giri-Aayush

Starknet All Core Devs Meeting #37

Meeting Details


Agenda Items

1. Network Stability Milestone - 38 Days Post-Deployment (Ohad)

  • 10-day uptime achievement since September 15th and ongoing stability assessment
  • Post-September incidents resolution validation and prevention measures effectiveness
  • v0.14.2 development status and committer implementation replacement timeline
  • Monitoring and alerting improvements following incident learnings
  • Network performance observations and stress testing continuation

Reasoning: Ohad reported 10-day uptime streak since September 15th in Call #36, with three incidents resolved. Need assessment of continued stability and v0.14.2 preparation.

2. Client Team Production Performance Updates

Pathfinder (Krisztian Kovacs):

  • Latest release deployment status and feeder gateway inconsistency fix validation
  • Pre-confirmed data polling performance and JSON RPC reply consistency
  • Production stability assessment over the past two weeks
  • Community feedback on recent improvements

Juno (Rodrigo Pino):

  • v0.15.7 release performance and bug resolution status
  • Reorg detection mechanism validation in production environment
  • Sync mechanism refactoring results and testing improvements
  • Bug reports investigation outcomes and resolution status

Karnot (Hemank):

  • v0.14.0 support completion status and RPC 0.9 implementation progress
  • Block replay testing results from 150k Starknet blocks validation
  • v0.14.0 block replay initiation and performance assessment
  • Sequencer reorg implementation progress and production readiness
  • E2E testing framework deployment and validation results

Reasoning: Each team had specific deliverables and testing activities in Call #36. Need to validate completion and assess production performance.

3. AOB (Any Other Business)

Note: Informal Systems team (Yasmina) is unavailable due to company retreat. Consensus implementation updates will resume in the next call following their meeting with the foundation.

  • Reorg documentation availability for sequencer implementation guidance
  • Incident reports sharing and team coordination improvements
  • Cross-team knowledge transfer requirements and support mechanisms

Reasoning: Karnot requested reorg documentation for sequencer implementation. Need to address documentation and knowledge sharing across teams.

4. 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, October 23, 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