Proposal to deploy MetDipper.
Background Our AI developers have invested considerable time in training our proprietary large language model (LLM) to optimize the timing of digital asset purchases and determine the optimal allocation percentage of a user's portfolio at any given moment, thereby helping users grow their portfolios.
The MetDipper buy signals have been thoroughly back-tested, and MetDipper significantly outperforms more traditional date-based dollar-cost-averaging (DCA).
No additional development costs are needed to deploy MetDipper.
Motivation Millions of people globally could benefit from an automated digital asset buying tool, potentially leading to increased adoption of the MetFi protocol.
How It Works MetDipper would allow users to commit funds regularly, e.g., 50 USDT per week or more, building a smart pool of funds that waits for the opportune moment to buy. Instead of regular date-based buys, MetDipper buys based on real-time market signals, e.g., buying more when prices dip lower and less when prices are higher.
MetDipper would deploy in four (4) stages, with stages 1 and 2 deploying first, with stages three (3) and four (4) to follow.
Stage 1 – Bitcoin signals the user to buy manually. Stage 2 – Automated, hands-free Bitcoin buying. Stage 3 - Assets such as ETH, SOL, and tokenized stocks are added to the signals portfolio. Stage 4 - Enhance the user experience (UX) with more automations and seamless platform integrations.
Eligibility Own an active affiliate-qualified MetFi Vault NFT.
Proposal Deploy MetDipper per the terms of this proposal.
Vote Discussion Join the discussion on this proposal in the MetFi DAO Discord #Vote-Discussion channel.
Vote If the community approves this proposal with a 'FOR' vote, MetDipper will be deployed as soon as possible.
Please vote 'FOR' to approve this proposal or 'AGAINST' to block it.
Off-Chain Vote
Loading…
- Author
MetFi
- IPFS#bafkreig
- Voting Systemquadratic
- Start DateJul 24, 2025
- End DateJul 27, 2025
- Total Votes Cast12.56M METFI
- Total Voters259
Timeline
- Jul 24, 2025Proposal created
- Jul 24, 2025Proposal vote started
- Jul 27, 2025Proposal vote ended