I am pushing a motion to council now for an issue we found with collators on Westend: blocks are not being included every 6 sec to the relay chain. This issue is caused due to Westend not having secondary vrf slots enabled, therefore non-primary blocks didn't have randomness available. A sudo tx was pushed to Westend to enable it and the same this should be pushed on Kusama if it works on Westend.

The proposal to Council adds a tx to change BABE's config on Kusama to use secondary vrf slots that will need to go after runtime upgrade execution, so this proposal should only be executed only after the runtime is executed. The Technical Committee should take this into account when calculating `delay`.

Preimage [HERE](https://drive.google.com/file/d/1P0nEgO0hJtfzp3JYkERQT5zze3KIWMy6/view?usp=sharing). 

 Plan an epoch config change. The epoch config change is recorded and will be enacted on
 the next call to `enact_epoch_change`. The config will be activated one epoch after.
 Multiple calls to this method will replace any existing planned config change that had
 not been enacted yet.

- There is a problem with collators on Westend not including blocks every 6 seconds.
- This is because Westend doesn't have secondary vrf slots enabled, which means non-primary blocks don't have randomness available.
- A change was made to enable secondary vrf slots on Westend, and the same change should be made on Kusama if it works on Westend.
- A proposal has been made to the Council to change BABE's config on Kusama to use secondary vrf slots, but it should only be executed after the runtime is executed.
- More information can be found in the provided link.

#109 Fix for issue found with collators on Westend, also in Kusama.

No Active Proposals