feat(sync): Utilize Signature Verification Methods to Secure L2-only Blocks

[jbcaron]

Feature Request

Summary

We need to enhance the security of blocks that exist solely on Layer 2 by implementing signature verification methods.

Action Required

• Implement Signature Verification: Utilize the get_signature and get_public_key endpoints to verify block data on L2.
• Use ECDSA on the STARK Curve for all cryptographic signatures to ensure data integrity and authenticity.

Goals

• Ensure Data Integrity: Verify that all L2 block data (block_hash & state_diff_commitment) is accurate and unchanged.
• Increase Security: Protect against unauthorized data changes and potential security threats.

Impact

• Nodes will require updates to handle new verification methods.
• Operators must learn how to use these new features effectively.

Feedback Requested

• Please provide feedback on this plan, especially any concerns about implementation or potential impacts on system performance.

Note

• This mechanism is temporary and will be replaced by the Starknet Consensus protocol once it is released
• The key pair will be updated every year (unless the key is compromised, in which case we will replace it immediately)

[github-actions]

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a 👍
Because this issue is marked as stale, it will be closed and locked in 7 days if no further activity occurs.
Thank you for your contributions!