Summary
Proposal: Suspend Funding for MCP Advisor DAO Phase 1 Pending Clarification
Summary
This proposal requests that funding for the approved “Phase 1: Discovery & MCP Aggregator” initiative be suspended until the proposing team provides sufficient information for the WAVES DAO community to evaluate the initiative properly.
The purpose is not to reject the underlying idea permanently. An MCP-based advisory and data-aggregation service may be worth exploring. However, the current proposal was approved without enough public information about the responsible team, the concrete deliverables, implementation plan, budget, and governance structure.
DAO funds should only be released once the community can make an informed decision.
Requested Decision
Suspend any outstanding or future funding transfers connected to the MCP Advisor DAO Phase 1 proposal until a revised and sufficiently detailed proposal has been publicly presented and approved by the WAVES DAO.
Any funds already irreversibly transferred are not affected by this vote. However, no additional funds, treasury allocations, or related payments should be released while the initiative remains insufficiently specified.
Rationale
1. The responsible team is unknown
The proposal does not clearly identify the people or entities responsible for delivering the project.
The community should know:
- Who is leading and implementing the project;
- What relevant technical, operational, and business experience they have;
- Who controls project funds and treasury wallets;
- Who is accountable for delivery, reporting, and potential failure to deliver.
Without this information, token holders cannot reasonably assess execution capability, accountability, or conflicts of interest.
2. The funded scope is too vague
The original proposal refers broadly to an “MCP aggregator,” data-source discovery, intelligent routing, subscription infrastructure, partnerships, and initial operations. However, it does not define sufficiently concrete deliverables.
Before funding proceeds, the community should receive a revised specification including at least:
- A technical architecture and intended MCP/data-source integrations;
- Clearly defined Phase 1 deliverables;
- A development roadmap with milestones and dates;
- A detailed budget and expected use of funds;
3. The central idea has not been publicly discussed
The main concept appears not to have been discussed sufficiently in public before the funding vote.
Community members therefore lack clarity on important questions, including:
- What exact problem the MCP Advisor DAO is intended to solve;
- Why MCP aggregation is the appropriate technical and commercial approach;
- What data sources, users, and markets are being targeted;
- How the service will generate sustainable subscription revenue;
- What risks exist regarding data quality, trading advice, legal compliance, security, and custody;
- Why this initiative should receive DAO funding instead of competing priorities.
A substantial initiative that may receive DAO funds and establish a revenue stream should first be openly debated by the community.
Conditions for Resuming Funding
Funding may resume only after a revised proposal has been published and approved through a new DAO vote. The revised proposal should include:
- Public identification of the responsible team and its roles;
- A concrete technical and business specification;
- A transparent budget and treasury/payment structure;
- Milestone-based funding releases;
- Defined reporting obligations;
- Public community discussion before the new vote;
- Clear rules for the proposed 10% revenue flow to the WAVES DAO treasury.
Conclusion
This proposal does not prejudge the value of the MCP Advisor DAO concept. It asks only that DAO funds be protected until the community receives the information necessary to evaluate the project responsibly.
A pause now allows the initiative to return with a transparent team, a concrete plan, measurable milestones, and meaningful community support.
Vote YES to suspend further funding until a revised and fully specified proposal is publicly discussed and approved.
- Transaction ID
- 5j6MzuzcXewYLL9w9nvSakeAUAYtdA5Wqr9DLAoDqPsd
- Sender address
- 3PEwRcYNAUtoFvKpBhKoiwajnZfdoDR6h4hPublic key: GDPfYHA6NUZCmin3J7LWZhCvSjBcna8HebyvQyrw17v
- Smart contract address
- 3PEwRcYNAUtoFvKpBhKoiwajnZfdoDR6h4h
- Function call
cancelSchedule(3P3xxFTi8x3273J1YFaA17SVk4PPwHiG6dh)- Blockchain fee
- 0.005 WAVES
- Execution time
- 12 Jul 2026 15:39Broadcast 14:39 - 16:39
Raw transaction data
{
"type": 16,
"version": 2,
"senderPublicKey": "GDPfYHA6NUZCmin3J7LWZhCvSjBcna8HebyvQyrw17v",
"dApp": "3PEwRcYNAUtoFvKpBhKoiwajnZfdoDR6h4h",
"call": {
"args": [
{
"type": "string",
"value": "3P3xxFTi8x3273J1YFaA17SVk4PPwHiG6dh"
}
],
"function": "cancelSchedule"
},
"payment": [],
"fee": 500000,
"feeAssetId": null,
"timestamp": 1783870782280,
"chainId": 87,
"proofs": [],
"id": "5j6MzuzcXewYLL9w9nvSakeAUAYtdA5Wqr9DLAoDqPsd"
}