Hello, Flow Community!
Today, I’m excited to share with you the detailed strategy for the transaction inspection logic for the Crescendo network upgrade on Flow’s mainnet, aimed at ensuring a smooth and successful migration for all developers and stakeholders involved.
This logic checks transactions that are submitted to Flow mainnet for imports of contracts that have not been staged for upgrade yet. It is capable of failing transactions that have unstaged dependencies in order to make the maintainers aware that they need to stage or their contracts will break permanently.
If all dependencies have been staged, transactions will have no chance of failing because of this logic.
Here’s how it works:
Starting Point: We initiate the transaction failure mechanism at 0% of transactions with unstaged dependencies. This gentle start allows the network to adapt without immediate disruption.
Continuous Escalation: We will continuously escalate the percentage of transactions set to fail with each block. This steady increase will continue throughout the month, culminating at 100%.
Block-by-Block Adaptation: This block-by-block escalation allows for a very granular and controlled increase, providing developers with the opportunity to monitor and adjust their systems in real-time. This method is designed to catch and address issues incrementally, which helps in maintaining network stability and performance.
Ongoing Evaluation and Mitigation: We will be continuously monitoring the results of the transaction inspection logic. This step ensures that we maintain a balanced approach to ramping up without overwhelming the system or the developers.
Objective: Our ultimate goal is to ensure all transactions on the network have been thoroughly tested and vetted under progressively stringent conditions. This ensures that the Crescendo network environment on Flow’s mainnet is as stable and reliable as possible.
We believe this approach not only meets our technical goals but also demonstrates our commitment to a transparent and collaborative community process. It allows us to methodically tackle potential issues before they affect the broader ecosystem, offering a safer and more effective migration path.
Your feedback is crucial as we refine our approach and move towards a successful mainnet launch. Please share your insights, suggestions, and any concerns you might have about this strategy. FLIP for this change can be found here: Crescendo Path To Mainnet Governance FLIP - 285.
Thank you for your ongoing support and collaboration. Together, we’re building a robust and scalable blockchain platform that will serve as a home for innovation for years to come.
Looking forward to our collective journey to the Crescendo network upgrade on Flow’s Mainnet!