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
As discussed in #8534, Lotus is continuing to rely on specs-actors for migrations, despite the refactor to have state types in go-state-types, and the introduction of the FVM.
While this motivates a larger redesign (that might eventually involve having the FVM perform these migrations through the FFI), there is a smaller actionable item: supporting actor code-only migrations in Lotus (no state transformation except the System Actor).
The inputs would simply be the old manifest, new manifest, and state root, and all the migration needs to do is convert all actor CIDs based on the manifests, and update the system actor state. This should be relatively easy to do quickly without any bells and whistles.
It would be good to have this ready sooner rather than later so as to support quick actor upgrades if needed.
The text was updated successfully, but these errors were encountered:
As discussed in #8534, Lotus is continuing to rely on specs-actors for migrations, despite the refactor to have state types in go-state-types, and the introduction of the FVM.
While this motivates a larger redesign (that might eventually involve having the FVM perform these migrations through the FFI), there is a smaller actionable item: supporting actor code-only migrations in Lotus (no state transformation except the System Actor).
The inputs would simply be the old manifest, new manifest, and state root, and all the migration needs to do is convert all actor CIDs based on the manifests, and update the system actor state. This should be relatively easy to do quickly without any bells and whistles.
It would be good to have this ready sooner rather than later so as to support quick actor upgrades if needed.
The text was updated successfully, but these errors were encountered: