feat(tracking): cairo native

[jbcaron]

Cairo Native

Integration of Cairo Native.

Description

Context and Motivation

Cairo Native offers AOT compilation that could significantly improve execution performance. This PR aims to discuss and design the best approach for this integration.

Key Points to Address

1. Compilation Strategy

a) Compilation Pipeline
We need a robust and isolated compilation process. Discussion points:

• How should we handle compilation failures?
• Should compilation be synchronous or asynchronous?
• What's the best approach for resource management during compilation?
• How do we handle compilation priority for different contracts?

2. Execution Strategy

a) Contract Selection Criteria
We need to define clear criteria for when to use native execution vs interpreted execution:

• What metrics should influence this decision?
• Should we implement a learning mechanism to improve selection over time?
• How do we handle edge cases and special contracts?
• What's the optimal threshold for switching between execution modes?

b) Fallback Mechanism
Need to design a robust fallback system:

• What should trigger a fallback?
• How do we ensure seamless transition between execution modes?
• How do we monitor and log fallback events?
• What's the performance impact of fallback mechanisms?

3. Isolation and Security

a) Compilation Security
Discussion needed on isolation approach:

• Container-based vs OS-level isolation?
• Resource limits and their configuration
• Security boundaries and potential vulnerabilities
• Monitoring and logging requirements

b) Execution Security
Need to define security parameters for native execution:

• What isolation level is required?
• How to handle malicious or buggy contracts?
• What security metrics should we track?
• How to implement secure state management?

Let's discuss these points and align on the best approach forward. Your input on any of these aspects would be valuable for shaping the final implementation.