Dear community,

With an upcoming runtime upgrade we should see the decommissioning of Governance 1.0 on the Polkadot network.  Associated with this are several unlocks of deposits including those associated with Treasury Spend Proposals.  There are already several teams who have requested immediate return of their deposits via tips or spend proposals on OpenGov or tips on Gov 1.0.  

This referendum seeks to reduce the number of refund requests and prevent double spends by:

- Slashing treasury deposits already returned to proposers 
- Slashing treasury deposits for proposers who have pending OpenGov proposals requesting or incorporating same
- Slashing Gov 1.0 tips and treasury deposits for applicable proposers. The proposers would have their treasury funding and tip deposit returns to their respective accounts
- Treasury deposits would be slashed and refunded to all those not matching the criteria to any of the above

The list of recipients was determined with collaboration with Otar who been keeping track of such refunds.  

Regards,
 


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:** Addressing the influx of refund requests related to Treasury Spend Proposals on Polkadot due to the upcoming Governance 1.0 decommissioning.
- **Significance:** Preventing double spends and reducing the number of refund requests to streamline the transition process.
- **Proposed Solution:** Implementing measures to slash and refund treasury deposits based on specific criteria for proposers.
- **Expected Outcomes:** Efficient handling of refund requests, preventing double spends, and ensuring a smooth transition during the Governance 1.0 decommissioning on Polkadot.

#366 Rejecting Gov1.0 Treasury Proposals and Facilitating Bond Reimbursement where applicable

No Active Proposals