testnet-v0.5.0 & pop-node v0.3.0

[al3mart]

Release Readiness Tracking

Node Release

• All changes have passed peer-review.
• • feat(testnet): mainnet & devnet into testnet runtime #482
• • chore(node): pop-node v0.3.0 #484
• pop-node crate version has been updated.
• • chore(node): pop-node v0.3.0 #484
• The new binary is able to sync the live network and peers with other active nodes, logs are healthy.

2025-03-03 16:39:24 [Relaychain] ⚙  Syncing 576.4 bps, target=#5389664 (7 peers), best: #3649 (0xfbe0…d391), finalized #3584 (0x2976…4e30), ⬇ 939.2kiB/s ⬆ 9.5kiB/s    
2025-03-03 16:39:24 [Parachain] ⚙  Syncing 428.2 bps, target=#3590258 (3 peers), best: #3316 (0x2d06…0c33), finalized #0 (0xe8b2…8aa1), ⬇ 1.7MiB/s ⬆ 0.8kiB/s    
2025-03-03 16:39:25 [Parachain] assembling new collators for new session 3 at #3600    

• One collator runs with the new binary, syncs the network and peers with other nodes, produces blocks and logs are healthy.

Runtime Release

• All changes have passed peer-review. feat(testnet): mainnet & devnet into testnet runtime #482
• Update runtime crate version. Note that pop-runtime-devnet is usually not updated.
• • feat(testnet): mainnet & devnet into testnet runtime #482
• Runtime spec version is updated.
• • feat(testnet): mainnet & devnet into testnet runtime #482
• If needed, new benchmarks have been run. A diff between the new weights and the current ones has been reviewed.
  • substrate-weight-compare can be used for this purpose.
• Execution of try-runtime doesn't point out any missing migrations or other items requiring action.

Testing Tracking

• Local upgrade test runs as expected.

1. Build the latest release.
2. Launch a network using pop up parachiain -f networks/testnet.toml -v.
   • pop-node version can be verified via: rpc calls -> system -> version()
   • Runtime version can be verified via: rpc calls -> state -> getRuntimeVersion()

Node release

3. Switch to the new release branch and rebuild.
4. Kill the running pop-node process

For instance, on Mac one can look in Activity Monitor, find the pop-node process and force quit. The network will still be running, but without the collator so Pop Network might not be producing blocks.

6. Run the new pop-node binary using the command prompted in step 2, with the same specs that are prompted at step 2.
7. Verify that the new node is producing blocks.
8. Verify running versions as needed.

Runtime release

The new runtime might need a certian pop-node version to be deployed first, if that is the case make sure you follow the above steps for a Node Release

3. Do a runtime upgrade using the new runtime release -- can be found in ./target/release/wbuild/pop-runtime-testnet/pop_runtime_testnet.compact.compressed.wasm.
4. Verify the runtime upgrade was successful:
   • The runtime version should have changed.
   • The corresponding migrations should have run.
   • Pop Network is still producing blocks.

• Successful execution of try-runtime .

cargo build --release --features=try-runtime -p <runtime-crate>
try-runtime --runtime ./target/release/wbuild/pop-runtime-testnet/pop_runtime_testnet.compact.compressed.wasm on-runtime-upgrade live --uri wss://rpc3.paseo.popnetwork.xyz:443

[2025-03-03T15:23:57Z INFO  runtime::contracts] === POST UPGRADE CHECKS ===
[2025-03-03T15:23:57Z INFO  runtime::frame-support] ⚠ IsmpParachain declares internal migrations (which *might* execute). On-chain `StorageVersion(1)` vs in-code storage version `StorageVersion(1)`
[2025-03-03T15:23:57Z INFO  runtime::executive] ✅ Entire runtime state decodes without error. 8096312 bytes total.
[2025-03-03T15:23:57Z INFO  try-runtime::cli] PoV size (zstd-compressed compact proof): 3.7 KB. For parachains, it's your responsibility to verify that a PoV of this size fits within any relaychain constraints.
[2025-03-03T15:23:57Z INFO  try-runtime::cli] Consumed ref_time: 0.001704826s (0.09% of max 2s)
[2025-03-03T15:23:57Z INFO  try-runtime::cli] ✅ No weight safety issues detected. Please note this does not guarantee a successful runtime upgrade. Always test your runtime upgrade with recent state, and ensure that the weight usage of your migrations will not drastically differ between testing and actual on-chain execution.

• (Advised) Runtime upgrade on a local fork of Pop Network.

More instructions around using chopsticks for this can be found in .chopsticks directory

1. Launch the local fork:

    npx @acala-network/chopsticks@latest xcm -r ./.chopsticks/paseo.yml -p ./.chopsticks/testnet.yml

2. Do a runtime upgrade using the new runtime release -- can be found in ./target/release/wbuild/pop-runtime-testnet/pop_runtime_testnet.compact.compressed.wasm.
3. Might be needed to trigger block production on Pop Network:

    websocat ws://localhost:8000
    {"jsonrpc":"2.0","id":2,"method":"dev_newBlock","params":[{"count":20}]}

Release

Node release

• New node release has been created: https://github.com/r0gue-io/pop-node/releases/tag/node-v0.3.0
  • Create a tag like node-v<x.y.z>. node-v0.3.0
  • Point to the previous node release to create a proper diff.
  • Provide a description and then release notes.

Runtime release

• New runtime release has been created: https://github.com/r0gue-io/pop-node/releases/tag/testnet-v0.5.0

  • Create a tag like runtime-v<x.y.z>: testnet-v0.5.0
  • Point to the previous runtime release to create a proper diff.
  • Provide a description and then release notes.

• Create the authorization call data

  • Encoded call data: 0x00097fc702f000281e7a6321aaefac70ddd27fafce8d107f397ea183689a050419ae