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
There's a small issue with the live migration that can be done with the command:
namadan ledger run --height $BLOCK_HEIGHT --path $PATH_TO_MIGRATION_JSON_FILE --hash $JSON_FILE_HASH
The command applies the migration at the end of the specified block and this could be a problem if the migration also requires a protocol update. In this case, the transactions included in the block would be processed by the updated protocol but on the old state, which could make them fail or even crash the node in some cases.
As suggested by @tzemanovic, there's another way to see that issue: the run-until command cannot apply a migration: if this were the case then we could use this command and apply the following logic:
Run until the height before the specified one
Execute the block at $HEIGHT-1 and, at the end of it, apply the migration file
Skip to the next block height and halt (before executing the block)
Relaunch the node with the update binaries
The text was updated successfully, but these errors were encountered:
There's a small issue with the live migration that can be done with the command:
namadan ledger run --height $BLOCK_HEIGHT --path $PATH_TO_MIGRATION_JSON_FILE --hash $JSON_FILE_HASH
The command applies the migration at the end of the specified block and this could be a problem if the migration also requires a protocol update. In this case, the transactions included in the block would be processed by the updated protocol but on the old state, which could make them fail or even crash the node in some cases.
As suggested by @tzemanovic, there's another way to see that issue: the
run-until
command cannot apply a migration: if this were the case then we could use this command and apply the following logic:$HEIGHT-1
and, at the end of it, apply the migration fileThe text was updated successfully, but these errors were encountered: