This proposal rectifies an error in the previously approved Dexter smart contract upgrade proposal (link to previous proposal can be included here). The upgrade itself went through successfully, but the configuration for the new weighted pool and stableswap pool contracts was not set correctly.

Issue

The last proposal implemented a comprehensive upgrade of Dexter smart contracts. However, during the process, the configuration for the new versions of the weighted pool (v1.1.1) and stableswap pool (v1.1.1) contracts was not set correctly. This means the upgraded contracts cannot be used to create new pools, hindering their functionality.

Due to this configuration error, the proposal for the creation of the WBTC-XPRT pool failed. You can view the details of the failed proposal on Mintscan.

Solution

This proposal seeks to address the configuration issue by granting the Dexter Vault contract permission to instantiate (create) new instances of the weighted pool and stableswap pool contracts. Currently, the 'instantiate permission' for these contracts is set to 'Nobody', preventing anyone from creating new pools.

By granting the Vault contract this permission, we ensure that only authorized pool creations can occur through the established Dexter workflow. This maintains security while enabling the core functionality of the upgraded contracts.

Here's a breakdown of the specific configuration change:

• Target Contracts:
  • Weighted Pool Contract (Code ID: 17)
  • Stableswap Pool Contract (Code ID: 18)
• New Permission: 'AnyOfAddresses'
• Authorized Address: Dexter Vault Contract Address (
  persistence1k8re7jwz6rnnwrktnejdwkwnncte7ek7gt29gvnl3sdrg9mtnqkstujtpg
  )

This configuration change allows the Dexter Vault contract to instantiate (create) new instances of the weighted and stableswap pool contracts, enabling the creation of new pools with the improved functionalities of the upgraded versions.

Impact

This proposal ensures the newly deployed smart contracts function as designed. Users will be able to create new pools using the upgraded weighted and stableswap pool contracts, benefiting from the improved features and functionalities.

Voting Options

• YES: Vote to implement the corrected configuration for the new weighted pool and stableswap pool contracts.
• NO: Vote against fixing the configuration issue. (This would leave the upgraded contracts unable to create new pools.)
• NO WITH VETO: If you believe this is a spam proposal and the proposer should lose their deposit, vote NO WITH VETO.
• ABSTAIN: Choose to abstain from voting but still contribute to quorum requirements.