## Why (Objective) Cadence compiler: 1) enables us to keep evolving the language while maintaining backwards compatibility 2) unlocks future optimizations to increase execution throughput ## How will we measure success (Key Results) ? - [ ] All flow-go tests (FVM, EN, VN, etc.) work with compiler/VM - Cadence compiler executes transactions correctly (compared with current runtime with interpreter) - [ ] Execution results match for X period of time - [ ] Validate “Unused features” in https://github.com/onflow/cadence/issues/3804 are not needed for deployment - Performance of the compiler is at least on par with interpreter, or better - Ready to launch early 2026 ## Effort Estimate TBD ## DACI | Role | Assigned | | ------ | ---------| | Driver | Technical: @SupunS , EM: @j1010001 | | Approver | @Dete, @turbolent | | Consulted| @roham, @Kay-Zee | | Informed| Flow engineering team |
Why (Objective)
Cadence compiler:
How will we measure success (Key Results) ?
All flow-go tests (FVM, EN, VN, etc.) work with compiler/VM
Cadence compiler executes transactions correctly (compared with current runtime with interpreter)
Execution results match for X period of time
Validate “Unused features” in Compiler Milestone X #3804 are not needed for deployment
Performance of the compiler is at least on par with interpreter, or better
Ready to launch early 2026
Effort Estimate
TBD
DACI