Overview

The Dexter team proposes a configuration change in the LP Token and Pool codes stored earlier as a part of Dexter's deployment to allow instantiation using the Vault Contract.

Below are the steps that the Dexter Team is following:-

The proposal regarding the whitelisting of the Dexter team's address for code storage and instantiation on the Persistence Core-1 chain was passed successfully by the Persistence governance earlier in January. As a result, Steps 1, 2, and 3, as mentioned below, were performed by the Dexter Team.

Step 1: Store Vault, Keeper, Router, and Multistaking contract code

Store Vault, Keeper, Router, and Multistaking code with instantiate permission

with DEXADMIN () as a permissioned address. This step ensures that the Dexter team can instantiate them without governance proposals.

Step 2: Store Pool (Weighted and Stableswap) and LP token code

This step involves storing the code for two types of pools, Weighted and Stableswap, and the LP token code. However, the code is stored with

as instantiate permission type, implying no address can instantiate these contracts directly. This is done because the code cannot be uploaded with an "instantiate permissioned address" other than the ones allowed for upload, which is not a requirement for these contracts. They rather require the "instantiate permission" to be given to the Vault contract instead. The aforementioned configuration for these contracts can be changed via a governance proposal.

Step 3: Instantiate Vault, Keeper, Router, and Multistaking contracts

These contracts are directly instantiated by the DEXADMIN address for which the permission was granted in Step 1.

Step 4: Change Pool (Weighted and Stableswap) and LP token instantiation permission using Governance Proposal

This step involves changing the instantiation permission for the LP Token and Pool (Weighted and Stableswap) contracts. Currently, these contracts have

as the instantiate permission as done in Step 2, which means no one can instantiate them. This proposal proposes a configuration change to the "instantiate permission" of these codes to allow them to be instantiated using the Vault contract, which facilitates pools' creation.

Conclusion

This step is necessary for the deployment of Dexter and represents the most decentralized approach we have discovered. We anticipate the community's support to successfully deploy Dexter as a Dapp on the Persistence Core-1 chain.

Governance Votes

YES : You approve the proposal statements and agree to allow to give LP token and Pool codes the permission to be instantiated using the Vault Contract with address:

NO : The NO vote is a request for improvements or adjustments. You agree that this proposal's motivation is valuable and that the team should create a follow-up proposal once the amendments are included.

NO (VETO): You veto the entire motivation for the proposal, and the proposers will not create a follow-up proposal.

ABSTAIN: You are impartial to the outcome of the proposal.