Upgrade Checklist – Polkadot / Paseo (with Xcavate)

Pre-Requisites

• Linux/macOS (or WSL/VM for Windows)

• Installed: psvm, zepter, cargo, try-runtime

• Local chain running & baseline runtime noted (spec_version, impl_version)

---

Upgrade Steps

1. Baseline

   • Record current runtime version (spec_version, pallets, dependencies).

2. Select Target Version

   • Pick next stable Polkadot SDK release (don’t skip versions).

   • Check Paseo governance announcements for testnet alignment.

3. Bump Dependencies

   • Run: psvm -v stableYYMM-ZZ

   • Run: zepter fix

4. Review Changes

   • Read node-level changelogs.

   • Read runtime-level changelogs.

   • Compare against Polkadot SDK templates.

5. Update Metadata

   • Bump spec_version in runtime/src/lib.rs.

   • Bump package version in Cargo.toml.

6. Migrations

   • Write storage migration code if needed.

   • Run try-runtime to validate migrations.

7. Build & Test

   • cargo build --release → confirm WASM generated.

   • Run all unit & integration tests.

8. Deploy Runtime Upgrade

   • Dev/Testnet → Sudo extrinsic via Polkadot.js Apps.

   • Mainnet → Governance proposal.

9. Verify

   • Confirm runtime version updated on-chain.

   • Run E2E functional tests.

---

Xcavate Nuances

• Review custom pallets (NFT-backed loans, funding, compliance).

• Write migration logic if Xcavate storage schema is affected.

• Test Xcavate flows (mint, loans, asset transfers) on Paseo before production.

• Validate XCM interactions with AssetHub/BridgeHub.

---

Post-Upgrade

• Update internal documentation.

• Record upgrade in CHANGELOG.md.

• Tag release in Git.