With the release of the new [Spiritnet 1.9.0 runtime](https://github.com/KILTprotocol/kilt-node/releases/tag/1.9.0), a new feature was added: registering the creation block number for new CTypes, to allow clients to retrieve the entire CType content using the block number as a reference.

The 1.9.0 runtime migration did not intentionally set the block number for previously-created CTypes. This is what this proposal aims to do: it dispatches a `utility.batchAll` transaction which sets the correct block number for all the 14 previously-issued CTypes on Spiritnet.

One way of verifying the information in the call, is to use Subscan, and [filtering for the `ctype::ctypecreated` event type](https://spiritnet.subscan.io/event?address=&module=ctype&event=ctypecreated&startDate=&endDate=&startBlock=&endBlock=&timeType=date&version=10890).



- A new feature was added in the Spiritnet's 1.9.0 runtime to register the creation block number for new CTypes to allow for easier retrieval of content associated with them.
- The 1.9.0 runtime migration did not intentionally set the block number for previously-created CTypes.
- This Polkassembly Referendum post proposes dispatching a `utility.batchAll` transaction to set the correct block number for all 14 previously-issued CTypes on Spiritnet.
- Verifying the information in the call can be done by filtering the Subscan for `ctype::ctypecreated` event type.

Set the correct block creation for existing CTypes

No Active Proposals