If this change is applied, the collators that are active will be determined about every 2 hours (`600 blocks * 12 sec/block = 2 hours`). In addition, reward calculation and payouts will also be done every 2 hours. Those two processes are very intense operations that the chain has to execute currently every 4 minutes, so making this change will unlock many resources for transactions. Other side effects are that decreasing the bonds or leaving the candidate set will increase to 4 hours. 
Changing the blocks per round to higher value is also mandatory to increase the active collator set size.
We decided to go with 2 hours based on the example of Moonriver, a parachain on Kusama whose organization created the *parachain-staking* pallet that is handling the `blocksPerRound` value.

The proposal aims to develop the KILT Decentralized Identity Provider (DIP), offering an OpenID-like authentication flow for Web3. It enables cross-chain identity establishment by using on-chain and off-chain mechanisms. Led by BOTLabs GmbH, seeks to reduce centralization in identity management while providing users control over their data. Key components include pallets for identity providers and relying parties, along with support crates for chain runtimes. The proposal outlines milestones for development, testing, and deployment, highlighting the need for ongoing maintenance and future enhancements

Implemented new Polkascan Explorer and Subsquid extensions to the py-substrate-interface extension framework.

New runtime interface: more intuitive approach to interface with the runtime functionality.

Added support for ink! v4.

Added SCALE type definitions for upcoming MetadataV15 in Substrate.

Added multiple params as key support for query_map().

Add support for runtime calls at other blocks than the most recent #346.

Upgrade contract interface to support WeightV2 #337.

Updated metadata docs for Polkadot & Kusama parachain and stand-alone runtimes.

Technical support on Github and in #polkascan:matrix.org and substrate.stackexchange.com channels.

- **Problem Statement:** 
  - Active collators and reward calculations currently occur every 4 minutes, creating resource-intensive operations for the chain.

- **Significance:** 
  - Changing collator determination and reward calculations to every 2 hours will free up resources for transactions and reduce the intensity of operations.

- **Proposed Solution:** 
  - Adjusting the collator determination and reward calculation frequency to every 2 hours, similar to Moonriver's approach on Kusama.

- **Expected Outcomes:** 
  - Increased efficiency in resource allocation, reduced intensity of operations, and potential for a larger active collator set size.

#5 Increase round duration to approximately 2 hours - external proposal 0x503be4