RFC #3: Proposal for Protocol Upgradability and LP migration to custom made Wagmi V4 model

[RFC] Request for comment
1

RFC #3: Proposal for Protocol Upgradability and Liquidity Migration to Custom made Wagmi V4 Model

Introduction:

The WAGMI DAO is proposing for a strategic upgrade of our protocol. We propose an upgradability strategy that includes development of a new Liquidity Pool (LP) system - the custom-developed Wagmi V4 model, transitioning from the existing V3 model that allows us to migrate liquidity and treasury to improved V4 model.

Rationale for Development and Migration to V4:

  1. Greater Customization:
    • The V4 model introduces “Hooks” for creating unique pool designs, allowing for innovative and tailored liquidity management strategies.

  2. Enhanced Efficiency:
    • Improved transaction routing and cost optimizations in V4 promise more efficient trade execution, benefiting both the protocol and its users.

  3. Reduced Gas Fees:
    • The V4 model employs Singleton smart contracts and refined accounting methods to significantly cut transaction costs, enhancing economic efficiency.

  4. Increased LP Revenue:
    • V4’s dynamic fee structure adapts to market conditions, offering the potential for higher returns to liquidity providers.

  5. Flexibility for Launching on New Chains:
    • The V4 model facilitates the WAGMI DAO’s expansion onto additional networks, enabling treasury migration into new V4 style LPs.

Implementation Strategy:

  1. Technical Assessment:
    • Review existing contracts and LPs.
    • Evaluate the impact and advantages of migrating to V4.

  2. Development and Security:
    • Develop required smart contracts for the transition.
    • Focus on security to protect assets during migration.

  3. Phased Implementation:
    • Implement migration in stages for stability.
    • Continuously refine V4 strategies for optimal performance.

Conclusion:

This proposal aims to position WAGMI DAO as a DeFi innovation leader. By developing the Wagmi V4 model, we can utilise its advanced features for enhanced performance and user advantages. We seek community feedback to ensure a successful transition.

Next Steps:

• Collect community feedback and suggestions.
• Finalize migration strategy based on community insights.
• Initiate technical development and execution.

We eagerly await your valuable insights and support in this significant upgrade. Following community feedback, a snapshot vote will be held to decide on the implementation.

WAGMI DAO

Edit number 1:
Adding clarification that treasury is currently team funded and no protocol owned LPs will be used for funding the development.
Major point of doing it is to prepare liquidity infrastructure for hooks that are coming to AMM space.

3 Likes
2

I think there’s not much for the community to comment on here.

The rationale mentions 5 great improvements and its unclear to me how we can suggest anything for the implementation strategy.

The proposal looks great overall and i suggest we move forward with the snapshot asap!

3

I agree, as long as the stability of the chain will be guaranteed.

1 Like
4

All good upgrades but I think a major feature that is missing is GMI not being shared across chains. Ideally, GMI is an index for fees generated across all chains and the user doesn’t have to bet on which chain’s GMI will perform the best. Also, will liquidity that resides in pools with hooks be able to be bonded into GMI? For example, I assume the leverage feature that you plan on shipping is a hook. Can this be bonded into the treasury instead of the liquidity in the standard CL management strategies?

2 Likes
5

In v4, will GMI holders share fee from all chains? Or will that remain chain specific?

6

As with all WAGMI products we aim to provide as much decentralization as possible hence we do not control the fees so they are not routed though DAO controlled contracts where we can divert on how they are distributed. The team is working on a “volunteer” type of contract which will enable crosschain distribution and will support external teams providing “convex” like solutions.

1 Like
7

If someone will build a hook that will provide the leverage as we want it we will be able to whitelist the liquidity to be used for leverage after migration. We will work on such solutions as well.

8

I’m lovin It! :fries: Good proposal, nice to see some reaction!

1 Like
9

I fully support this proposal. This will make us ready for the future.