Due to an issue in the recent [decommissioning of Governance 1.0 on Kusama](https://github.com/paritytech/polkadot/pull/7314), which was enacted via [Referendum 301](https://kusama.subsquare.io/referenda/301), deposits associated with Treasury spend proposals remain locked. This referendum seeks to slash Kusama Gov 1.0 treasury deposits and refund the corresponding amounts to their respective proposers in a batch call similar to [Referendum 73](https://polkadot.subsquare.io/referenda/73), which was previously submitted on Polkadot.
Please note that spam proposals numbered 291, 292, 293, 294, and 296 have been identified as invalid submissions. Consequently, any bond associated with these proposals, as well as older proposals rejected by the council, are not included in this `forceBatch` call.

This proposal aims to optimize Polkadot and Kusama on-chain data accessibility, surpassing traditional block explorers and costly dashboards, catering to the needs of industry leaders, data analysts, marketers, and builders within the Web3 community.

- **Problem Statement:** Issue with locked deposits from Treasury spend proposals due to the decommissioning of Governance 1.0 on Kusama.
- **Significance:** Refunding deposits to proposers impacted by the Governance 1.0 decommissioning.
- **Proposed Solution:** Slash Kusama Gov 1.0 treasury deposits and refund them to proposers in a batch call.
- **Expected Outcomes:** Resolving locked deposit issue and ensuring fair treatment for proposers.

#366 Rejecting Kusama Gov1.0 Treasury Proposals and Facilitating Bond Reimbursement whenever appropriate