v4.0.0-alpha.1

NOT FOR PUBLIC USE

v3.4.3-Dolphin-v3

NOT FOR PUBLIC USE

v3.4.3

Low-Priority Hotfix Release

This release is on-chain runtime only. Upgrade the binary at your discretion.

The main features of this version are:

• Allocation of rewards to collators now works as intended
• improved block production stability

What's Changed

• client trait bound refactor by @zqhxuyuan in #836
• CI: Adding diff result to changelog verification workflow by @Apokalip in #851
• Fix sequence skipping when a collator misses its slot by @Garandor in #846
• Fix XCM tests by @ghzlatarev in #848
• Release v3.4.3 by @Garandor in #854
• Don't include testing helpers in release code by @ghzlatarev in #860
• Aura slot skip fix v2 by @Garandor in #865
• Fix round changes by @Garandor in #867
• Release v3.4.3 (second attempt) by @Garandor in #866

Full Changelog: v3.4.2...v3.4.3

v3.4.2

Low Priority Release

This release consists of cleanups and minor improvements to the staking pallet, versioning, as well as testing and CI that didn't make it in time for v3.4.1 due to that release's urgent nature.

Thank you for your time and votes!

What we need you to do

No action needed from anyone ( besides voting on the runtime upgrade ).
This release affects the on-chain runtime only.

What's Changed

• Run live benchmarks as test in CI by @ghzlatarev in #833
• Followups to Staking by @Garandor in #834
• align block number type in tests by @zqhxuyuan in #835
• Improve mock xcm by @ghzlatarev in #840
• Release v3.4.2 by @Garandor in #841

New Contributors

• @zqhxuyuan made their first contribution in #835

Full Changelog: v3.4.1...v3.4.2

v3.4.1

⚠️ High Priority Hotfix Release ⚠️

This addresses two issues reported with the previous v3.4.0 release, specifically:

1. Round-Robin block producer assignment is now active, block producers no longer need to compete with others in a hardware race to get their block included, evening out staking rewards distribution.
2. Sending KMA from Moonriver via XCM ( using Moonriver apps ) is fixed and will be re-enabled by the Moonriver team shortly following the runtime upgrade. A separate announcement will follow.

What we need you to do

No action needed from anyone ( besides voting on the runtime upgrade ).
This release is a hotfix to the on-chain runtime only.

What's Changed

• Disable v3.40 migration code by @Garandor in #819
• Hardcode weight for instructions with MultiAssetFilter params by @ghzlatarev in #822
• Fix Block Producer Selection by @Garandor in #818
• Release v3.4.1 by @Garandor in #826

Full Changelog: v3.4.0...v3.4.1

v3.4.0

⚠️ HIGH PRIORITY RELEASE ⚠️

We're delighted to present to the community a permissionless Delegated Proof-of-Stake enabled Calamari Network.

The new tokenomics including transaction fee burn and staking rewards described in the docs become active when this runtime upgrade goes live on chain.

Also, this upgrade concludes our collator program as from now on, anyone who wants to run a collator will permissionlessly be able to do so.
We will release staking guides for collators and delegators in the docs before the upgrade goes live.

What to expect

Users: No action needed, but you will be able to delegate your KMA to and share in other’s collator rewards
Full Node Runners: No action needed
Collator Runners: ⚠️ Once this upgrade is live, your node will no longer produce blocks. See below for info

What we need you to do

If you are running an active collator node as part of the collator program before v3.4.0:

• You do not need to upgrade your manta executable though there is no harm in doing so anytime you wish
• Calamari network will use pallet_parachain_staking for collator selection from this upgrade on. Your nodes are currently registered with the old manta_collator_selection pallet which will become inactive once the upgrade vote passes.
• Your current slot with manta_collator_selection entitles you (for a limited time) as a member of our collator program to a collator slot with a reduced bond of 400_000 KMA as a thank-you for your early support of the network
• You need to manually onboard your collator to the new system by calling the joinCandidates extrinsic from polkadot.js on your collator’s account after v3.4.0 is live on-chain. It will take part in staking rewards after you have done so.
  ⚠️ Do NOT leave the old candidate set manually as this will lead to you forfeiting your entitlement and resulting in you having to bond 4M KMA if you wish to rejoin. Just run the below extrinsic and your currently reserved 400_000 KMA for the collator will be migrated over without requiring additional funds ( besides gas fees ).
  The bond is 400_000_000_000_000_000 KMA and 64 is just a hint for transaction weight that must be larger than the current number of registered collators ( or the transaction will fail )
  The bond is 400_000_000_000_000_000 KMA ( 400k plus 12 decimals ) and the 64 is just a hint for transaction weight that must be larger than the current number of registered collators ( or the transaction will fail )
  
• You will find more detailed instructions in the staking guide in the docs soon

What's Changed

• Workflow to check for labels by @Apokalip in #745
• Update fees splits, 50% burned, 50% to treasury by @ghzlatarev in #770
• All-benchmarks script and CI workflow improvements by @ghzlatarev in #758
• Change QA workflow link to internal Notion by @Garandor in #766
• Split all testing from publish_draft_release workflow and filter execution by labels on the PRs by @Garandor in #743
• Fix calamari bootnode names in chain-spec and docker by @ghzlatarev in #783
• Proper XCM weights benchmark by @ghzlatarev in #781
• Run manta-pay randomized tests in a loop 10 times by @ghzlatarev in #782
• Fix CI by ignoring failure of stop- jobs by @Garandor in #791
• Minor: Update PULL_REQUEST_TEMPLATE.md by @Garandor in #678
• Adapt 45/45/10 TX fee split for KMA, 100% to author for DOL by @Garandor in #792
• Nimbus Stage 2 - Enable permissionless staking on Calamari by @Garandor in #724
• Manta v3.4.0 Release by @Garandor in #797

Full Changelog: v3.3.0...v3.4.0

v3.3.0

⚠️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

v3.2.1

This is a runtime-only release that will be used to upgrade the on-chain runtimes for calamari and dolphin.
⚠️ Collator runners: Please continue using the manta binary from the previous v3.2.0 release

What's Changed

• Mention SDK in release template by @Garandor in #591
• Auto-enforce code formatting by @Garandor in #590
• feat: update parameter path from sdk to manta-parameters by @BoyuanFeng in #622
• [manta]Add strip profile to production by @Dengjianping in #449
• Autoassign new issues to the Development Github project by @Garandor in #601
• Dolphin CI runtime upgrade test by @ghzlatarev in #619
• fix: add CLI library back into node by @bhgomes in #607
• New MantaPay Storage Layout and RPC by @stechu in #628
• Fixup to #601 by @Garandor in #634
• Unfilter xtokens.transfer_multicurrencies and bump MaxAssetsForTransfer to 2 by @ghzlatarev in #576
• Reimplement TransactAsset with FungibleLedger and AssetConfig traits by @ghzlatarev in #563
• minor: Fix name change of #634 by @Garandor in #639
• Remove OnRuntimeUpgrade hooks by @Dengjianping in #614
• fix: add concurrency groups to the relevant workflows by @bhgomes in #653
• Yi/retire mpl by @flame4 in #657
• Minor: Remove deprecated license_template_path from rustfmt by @Garandor in #656
• Reduce CI failure rate by switching AWS CI runners from AMD to Intel by @Garandor in #652
• existence_requirement argument for FungibleLedger trait functions by @ghzlatarev in #638
• include calamari bootnodes in genesis by @grenade in #666
• Minor: Update PULL_REQUEST_TEMPLATE.md by @Garandor in #676
• Compile the runtime with stable Rust by adding RUSTC_BOOTSTRAP=1 flag by @Garandor in #677
• Bump deps to v0.9.22 by @Dengjianping in #571
• polkadot-v0.9.22 syn breakage workaround by @Garandor in #671
• Equalize Barrier impl between Calamari/Dolphin and mock parachain for XCM tests by @ghzlatarev in #636
• Add session key types for new consensus implementation to Dolphin and Calamari (Nimbus Stage 0) by @Garandor in #646
• Release v3.2.1 by @Garandor in #627

New Contributors

• @BoyuanFeng made their first contribution in #622
• @flame4 made their first contribution in #657

Full Changelog: v3.2.0...v3.2.1

v3.2.0

What's Changed

• Proper bare-metal instances for benchmarking workflows by @ghzlatarev in #505
• Concrete fungible ledger integration tests by @ghzlatarev in #519
• Dedupe mock-xcm tests (part 1) by @ghzlatarev in #493
• Move xcm and assets related runtime configurations to own files by @ghzlatarev in #523
• Clean up AssetManager migration code by @ghzlatarev in #531
• Add issue template for Calamari xcm onboarding of other parachains by @ghzlatarev in #507
• Skip build on too tiny change by @Dengjianping in #541
• Revamp collator-selection by @Dengjianping in #491
• Let CI support cargo audit and dependabot by @Dengjianping in #539
• Update xcm integrations template issue by @ghzlatarev in #542
• Multiply tx len and base fee component by max number of remarks per block, in the fees calculation of congested_chain_simulation test by @ghzlatarev in #536
• Bump serde from 1.0.136 to 1.0.137 by @dependabot in #549
• Bump srtool to v0.4.0 by @Dengjianping in #560
• Fix file structure of relay chian specs by @ghzlatarev in #567
• Remove sudo pallet from calamari runtime by @Dengjianping in #550
• Fix try runtime and metadata diff ci workflows by @ghzlatarev in #558
• Revert hard-coded branch of yamllint github action by @ghzlatarev in #570
• Bump deps to v0.9.18 by @Dengjianping in #481
• Benchmark cumulus-pallet-xcmp-queue and white list Treasury Account in benchmark test by @Dengjianping in #554
• feat: add ledger sync protocol by @bhgomes in #529
• feat: remove checkpoint from PullResponse RPC API by @bhgomes in #583
• Release v3.2.0 by @Dengjianping in #572

New Contributors

• @dependabot made their first contribution in #549

Full Changelog: v3.1.5-1...v3.2.0

v3.1.5-1

What's Changed

Runtime Only Release

• #475 New workflow for comparing runtime metadata before and after runtime upgrade.
• #485 XCM Fees now accrue to the Treasury instead of AssetManager.
• #509 OnRuntimeUpgrade hook for AssetManager to properly set initial configurations.
• #510 Automate publishing of Dolphin release artifacts.
• #513 Update the release issues template.