Manta-Network/Manta v3.3.0

on GitHub

⚠️High priority release with a breaking client change that will upgrade the network's consensus mechanism⚠️

The upgrade sequence for this release is:

• Users: No action needed
• Full Node Runners: Upgrade manta binary at your earliest convenience
  ⚠️If your node is not on the v3.3.0 binary by the time the runtime upgrade is enacted, it will fall out of sync with the network
• Collator Runners: Upgrade manta binary after the on-chain runtime upgrade to v3.3.0 is enacted
  ⚠️If you upgrade the binary before the runtime is live, it will not be able to produce blocks. This will cost you missed rewards, slow down the chain and delay the runtime upgrade)
  ⚠️ You have one week to upgrade after the v330 runtime is live on-chain. After one week, we will submit a governance motion to remove every collator that has not upgraded by then. If your node gets removed because of this, you will have to go through the collator onboarding process again ⚠️

Troubleshooting

I upgraded the binary and my node is stuck :(

1. Verify that Calamari Network has had its runtime upgraded to v3.3.0 (top left corner)
2. Verify that you're running the correct binary. manta --version should output manta 3.3.0-6718bf10797

The v3.3.0 runtime is live, I have just upgraded my node's binary but it is still stuck on the runtime upgrade block

It is possible your node got banned from networking by the upgraded peers, please

1. stop your node
2. delete your base-path/chains/chain/network folder (only the network folder, not db or keystore)
   NOTE: If you installed from our Debian package, base-path is /var/lib/substrate
3. restart your node

The v3.3.0 runtime is live, my node stays stuck after upgrading the binary and the log says

Idle (X peers), best: #<RUNTIME_UPGRADE_BLOCK+1> (0xca66…99bb), finalized #<RUNTIME_UPGRADE_BLOCK> (0xa572…70d8)

1. Stop your node
2. Run manta revert --chain=calamari -- 1
3. Restart your node

If it still does not resume syncing, please let us know in the #collator-maintainer channel on Discord!

What's Changed

• Use u128::MAX in fungible ledger transfer test by @ghzlatarev in #694
• Fix double spend reclaim test by @ghzlatarev in #703
• Minor: Ignore target folder on taplo fmt + clippy by @Garandor in #700
• Revert taplo cli workaround by @ghzlatarev in #709
• CI Ledger RPC Tests by @ghzlatarev in #681
• Use LengthToFee in the congested_chain_simulation's fee calculation by @ghzlatarev in #682
• Refactor fungible ledger mint/burn by @ghzlatarev in #695
• Update xcm-onboarding and release templates by @ghzlatarev in #715
• fix: upgrade to manta-rs v0.5.4 by @bhgomes in #723
• Dolphin-2085 on Baikal genesis by @ghzlatarev in #717
• switch runtime to wasm only by @flame4 in #701
• Update deps from v0.9.22 to v0.9.26 by @ghzlatarev in #720
• Trivial: Remove changelog, add label requirement to PR template by @Garandor in #714
• support STORAGE_VERSION for our pallets by @flame4 in #726
• Add changelog verification. Remove old changelog workflow by @Apokalip in #738
• Remove v3.2.1 SessionKey migration code by @Garandor in #737
• Add RPC for latest checkpoint by @bhgomes in #712
• Consensus migration stage 1: Enable Nimbus-Aura by @Garandor in #582
• Update github self hosted runner token by @ghzlatarev in #757
• v3.3.0 bump versions and weights by @ghzlatarev in #752
• Support verification of historic Aura blocks by @Garandor in #763
• Release v3.3.0 by @ghzlatarev in #764
• Remove changelog input in publish-draft-release job by @ghzlatarev in #765

New Contributors

• @Apokalip made their first contribution in #738

Full Changelog: v3.2.1...v3.3.0