Skip to content

Full Nodes Call #24 #14

Closed
Closed
@Giri-Aayush

Description

@Giri-Aayush

Starknet All Core Devs Meeting #24

Meeting Details

Agenda Items

1. Mainnet v0.13.5 Operation Status (Leonardo Lerer)

  • Post-upgrade stability assessment after two weeks in production
  • Resolution of Gateway investigation issues mentioned in call #23
  • Lessons learned from the deployment process

Reasoning: Leo mentioned in our last call that there were still issues being investigated in the Gateway. I'd like to follow up to ensure those have been resolved and get an overall assessment of stability now that v0.13.5 has been running in production for two weeks.

2. Cairo Native Implementation Progress (Ariel Elperin)

  • Results from completed replay testing
  • Testnet deployment status (expected 1-2 weeks from last call)
  • Shadow fork planning and timeline

Reasoning: Ariel told us last time that replay testing was still in progress, with a potential testnet deployment within 1-2 weeks if testing went well. I want to check if this timeline was met and understand the next steps toward production, particularly the shadow fork approach mentioned.

3. Client Team Updates

  • Pathfinder (update by Krisztian Kovacs):
    • Resolution of starknet_getEvents RPC provider issues
    • Large block timeout handling improvements
    • Malachite integration kickoff status
  • Juno (update by Rodrigo Pino):
    • Implementation status of dynamic timeout window for large blocks
    • Production performance with v0.13.5
  • Kasar Labs (update by Trantorian/Nathan):
    • Progress on v0.13.4/v0.13.5 support
    • Testnet status update

Reasoning: Each client team reported specific technical challenges in our last call. I want to confirm whether these issues have been resolved and understand current development priorities, particularly around large block handling that affected multiple teams.

4. P2P Protocol Chain ID Implementation (Shahak Shama)

  • Status of adding chain IDs to protocol names and topics
  • Implementation approach for multi-chain environments
  • Testing framework for network isolation validation

Reasoning: We reached consensus in our last call to add chain IDs to both protocol names and topics as a safeguard against misconfiguration. I want to confirm if this implementation is complete and discuss how it will handle multi-chain environments, particularly given comments from Trantorian about app chain requirements.

5. Malachite Consensus Integration (Adi Seredinschi)

  • Extended network testing results (latency, larger networks, non-empty blocks)
  • Integration progress with client teams (particularly Pathfinder)
  • Liveness sub-protocol review outcomes
  • Technical guidance for implementers

Reasoning: Adi outlined plans for extended testing with non-empty blocks and larger networks last time. I'd like to hear the results of these tests and understand how integration is progressing, especially with Pathfinder who mentioned they would begin work after v0.13.5 deployment.

6. L1 Data Extraction Tool Progress (Vaclav/Leonardo Lerer)

  • Status of stateless compression integration with parsing layer
  • Support for multiple state diff formats
  • Timeline for proof-of-concept completion

Reasoning: Vaclav mentioned in our last call that stateless compression was working but not yet integrated with parsing, with that integration expected within a week. I want to check if this integration was completed and understand what's next for this project that will help explorers better interpret Starknet data.

7. 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, April 24, 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