---
# System prepended metadata

title: Notification Message on Runtime Changes

---

### Important Release Notification about 2 Upcoming Changes

**1. Auto-incremented asset IDs in Asset Hub**

**Change**
The [v1.3.0 release](https://github.com/polkadot-fellows/runtimes/issues/186) upcoming release introduces an auto-incremented ID strategy for Trust-Backed Assets. This change sets a new constraint for all teams providing asset creation and management functionality on _Polkadot Asset Hub_ and _Kusama Asset Hub_. More information can be found in the related [PR](https://github.com/polkadot-fellows/runtimes/pull/414).

**Who should take Action**
Wallets and UIs that handle the creation and management of trust-backed assets in Asset Hubs.

**Required Action**
If applicable, teams should review the associated PR and update their code accordingly.

**Timeline**
Although no proposal has been submitted yet, it is expected to be up for a vote in the coming days. No estimated timeline can be given for the time being.


**2. Transaction Payment Extension Added in Collectives**

**Change relevant ONLY for Collectives parachain**
The [v1.3.1 release](https://github.com/polkadot-fellows/runtimes/releases/tag/v1.3.1) release includes a breaking [change](https://github.com/polkadot-fellows/runtimes/pull/442) on how transactions are encoded in the Collectives parachain. More specifically, it adds the Transaction Payment extension in the Collectives runtime which results in fees being applied when submitting transactions.

**Who should take Action**
Wallets and UIs that enable the creation and submission of transactions in the Collectives parachain.

**Required Action**
Teams that are using their own encoding (such as hardcoding the list of signed extensions) should update their code to include the new Signed Extension when encoding transactions for the Collectives parachain. This extension is already implemented in other chains, so teams should be familiar with the process. Failing to update the code will result in transaction failures once v1.3.1 is enacted.

**Timeline**
No proposal has been submitted yet, so the exact timeline is not available.