Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passively Test F3 on Mainnet #213

Open
9 tasks
masih opened this issue May 13, 2024 · 1 comment
Open
9 tasks

Passively Test F3 on Mainnet #213

masih opened this issue May 13, 2024 · 1 comment
Labels
Component testing Related to testing and validation

Comments

@masih
Copy link
Member

masih commented May 13, 2024

The following task list outlines the milestones required to complete the passive F3 testing on mainnet.

See F3 Mainnet Passive Test Plan for more details.

  • Testing utilities for passive testing in network deployment #229
  • Comprehensive Simulation Testing #226
  • Monitoring Infrastructure Setup #227
  • Local Testnet Deployment #228
  • Calibnet Deployment: Deploy the F3 protocol on Calibnet to mimic the conditions and processes of a mainnet rollout.
  • Post-Calibnet Deployment Metrics Analysis: Analyze the collected metrics for performance and correctness indicators. Confirm that all systems function as expected based on the metrics.
  • Potential Pre-mainnet F3 Implementation Adjustments: Based on insights from the Calibnet deployment, make any necessary adjustments. Freeze the F3 Alpha implementation in preparation for mainnet deployment.
  • Mainnet Deployment: Roll out the optimized F3 implementation across the mainnet. Follow a phased approach to monitor performance and impact during the rollout.
  • Post-Mainnet Deployment Metrics Analysis: Continuously monitor the F3 metrics post-mainnet deployment. Assess performance, correctness, and uptake to determine if further adjustments are needed.
@jennijuju jennijuju added testing Related to testing and validation Component labels May 15, 2024
@masih
Copy link
Member Author

masih commented May 17, 2024

This was intented to be the top level umbrella issue. But now it's in Milestone 1.

If that's where we want it to be then we should remove milestone 0 tasks from it.
CC @Kubuxu @jennijuju

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Component testing Related to testing and validation
Projects
Status: No status
Development

No branches or pull requests

3 participants