You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From time to time, the version of cadence or FVM need to be upgraded to address security issues, or add new functionality. When this happens, all nodes interacting with execution state (Execution, verification and access nodes) perform what's call a "Height Coordinated Upgrade" to synchronize updating to the new version at the same block height. This ensures that transactions and scripts produce the same result on all nodes.
Currently, Access nodes can run a single version of cadence/FVM for use by script execution. This is fine for executing against the latest block, but poses problems for archival nodes that want to serve queries for previous blocks that cross HCU boundaries. The only way to address this today is to run a separate node for each range of blocks between HCUs, that's running the correct software versions, but this creates operational challenges.
Proposed Solution
Add support for executing script against different cadence/FVM versions on a single node.
The content you are editing has changed. Please copy your edits and refresh the page.
Problem Definition
From time to time, the version of cadence or FVM need to be upgraded to address security issues, or add new functionality. When this happens, all nodes interacting with execution state (Execution, verification and access nodes) perform what's call a "Height Coordinated Upgrade" to synchronize updating to the new version at the same block height. This ensures that transactions and scripts produce the same result on all nodes.
Currently, Access nodes can run a single version of cadence/FVM for use by script execution. This is fine for executing against the latest block, but poses problems for archival nodes that want to serve queries for previous blocks that cross HCU boundaries. The only way to address this today is to run a separate node for each range of blocks between HCUs, that's running the correct software versions, but this creates operational challenges.
Proposed Solution
Add support for executing script against different cadence/FVM versions on a single node.
Tasks
The text was updated successfully, but these errors were encountered: