Asset Hub Monthly Update
Asset Hub Migration Support Article
We’ve published an article explaining what the Asset Hub Migration is and what it entails on Polkadot Support. This article aims to cover end-users’ doubts and warns them about the migration.
Sidecar update - Tracking Asset Hub state by Relay Chain block number
We’ve introduced a new query parameter in Sidecar (version 20.5.0 and above): useRcBlock. When enabled, it returns all Asset Hub events and transactions that occurred in a given Relay Chain block.
This is particularly useful for anyone who wants a consistent way to track Asset Hub activity in alignment with Relay Chain blocks. Continuing to use Relay Chain blocks as the reference allows you to maintain a single block height reference for the entire Polkadot network.
Looking ahead, once Elastic Scaling is enabled (using multiple cores for a single chain), this parameter will return aggregated transactions and events from all Asset Hub blocks included within the given Relay Chain block (i.e. there could be multiple Asset Hub blocks per Relay Chain block).
Please, find here the updated guide for the usage of useRcBlock.
New Forum Category: Resources & FAQ
To streamline your experience, we’ve added a FAQ category to the forum. You’ll find threads dedicated to specific migration subsystems there. Parity contributors, specialized in each topic, monitor the threads and provide answers directly within them.
Warning if you’re using transfer_assets 
The transfer_assets extrinsic will change behavior with the upcoming Asset Hub Migration. If you don’t update, some cross-chain transfers may start failing. Read more about this here.
Paseo was updated 
We successfully migrated to Asset Hub on August 27th. We are now conducting AMAs and gathering feedback from those affected by the migration. This will help us prepare and fine-tune the upcoming Kusama migration. Let us know if you have anything to report, or if something doesn’t look quite right in a tool that you use.