Backwards-compatibility check automation

[j1010001]

Why (Objective)

To deliver on the promises on Crescendo release (and according to our branching strategy), future Flow releases must be backwards-compatible - this automation will check execution results of Flow pre-release (including Cadence pre-release) agains prod and alert the engineering team if the difference in execution is detected.

How will we measure success (Key Results)

• The goal is 0 future releases deployed to prod without going through the compatibility check, re-executing min of 500K blocks.

Effort estimate

TBD - @sjonpaulbrown, @zhangchiqing

DACI

Role	Assigned
Driver	@sjonpaulbrown
Approver	@Kay-Zee
Consulted	@zhangchiqing
Informed	Flow Protocol engineering