#Include Shillables contracts in the list of pre v1.10 contracts in the v1.10 upgrade ## Summary This is a signaling proposal by Shillables to append their contracts to the list of pre v1.10 contracts in the v1.10 upgrade. We missed the opportunity to be included in prop #262 and are asking kindly to be appended to the list. This will allow these contracts to be upgraded to the new version without having to create a new contract and have users manually migrate their state. If approved, the v1.10 upgrade, tentatively scheduled for the 12th of September, 2023, will include the proposed hardcoded admins in its code. ## Details Due to Cosmos SKD proposal length limit, the full list of contracts is available on [GitHub](https://github.com/wolfbytes4/shill-stake/blob/main/docs/hardcode-admins-on-v1.10.md ). ## Key Takeaways This proposal will allow the listed contracts to be upgraded to the new version without having to create a new contract or manually migrating user data. This will save time and effort for developers and make it easier for users to continue using the contracts after the v1.10 upgrade. The Shillables team is seeking to upgrade all of their Shill Stake contracts to allow for multiple rewards to be given without impacting the users. The Wolf Pack PackBuilder is included to be able to fix a problem with the contract where new payment methods can not be added. SHILL is included in this list in case there are any key privacy updates. ## Risks The following is copied from proposal #262. The main risk of this proposal is that hardcoded admins could be used to upgrade contracts to malicious code that could leak private data or steal funds. To mitigate this risk, hardcoded admins should be carefully chosen and the chain should be monitored for suspicious `MsgMigrateContract` transactions. Note: Hardcoded admins can only be changed or removed by a governance proposal and a subsequent chain upgrade. For more info: [https://forum.scrt.network/t/an-update-on-the-contract-upgrade-feature/7012](https://forum.scrt.network/t/an-update-on-the-contract-upgrade-feature/7012)