Follow up from the Ironwood DB upgrade review.
The current migration reads legacy history tree entries in place and backfills the empty genesis Ironwood tree/anchor for upgraded databases. Before treating this as fully de-risked, validate the operational behavior on real node databases.
What to test
- Measure first-startup / format-upgrade time on a fully synced non-pruned database.
- Test startup and restart behavior on a pruned database.
- Confirm the upgrade completes without panics and the database remains readable after restart.
Acceptance criteria
- Record the database mode, chain height, approximate database size, host details if available, and elapsed startup / upgrade time.
- Exercise at least one pruned database upgrade path.
- Document any migration risk or follow-up code changes needed.
Follow up from the Ironwood DB upgrade review.
The current migration reads legacy history tree entries in place and backfills the empty genesis Ironwood tree/anchor for upgraded databases. Before treating this as fully de-risked, validate the operational behavior on real node databases.
What to test
Acceptance criteria