DAO Council Meeting Report
Date: August 3, 2026
Attendance: Canessa, MetaRyuk, Monotributista and Fehz (Agus was away)
1. Multisig Dashboard and Payments
Canessa and MetaRyuk completed onboarding to the Safe Workspaces dashboard. The council clarified that Avantgarde transactions require signatures from Canessa and MetaRyuk on the council side.
The council signed the following pending transactions:
-
Curator payment of 1.49K MANA
-
Council stipend transaction
-
Avantgarde authorization transaction
The Avantgarde transaction still requires an additional signature from the Avantgarde team’s second signer.
Council payments, curator stipends and gas-tank refills are now operational, completing the first fully automated payment cycle. The Multisig channel bot will issue payment reminders automatically on the first day of each month.
2. Points of Interest Status
The council addressed a critical issue with the Points of Interest (POI) feature management. The POI system has been effectively halted since the DAO Committee was deprecated, as they refused to perform the necessary handoff of control.
Currently, the DAO Committee Polygon Multisig is the sole owner of the Point of Interest contract and is the only entity authorized to add or remove items from the POI list. This has created a governance deadlock where the DAO cannot execute approved POI proposals despite having community support.
Five new POI proposals have already passed through the DAO voting process, while six groups in total are awaiting delivery. The community remains unaware that these approved proposals cannot be executed due to the technical control issue.
The only viable solution without the DAO Committee’s cooperation would be to deploy an entirely new Points of Interest contract that the DAO can control, followed by updating the platform/clients to point to this new contract. The council has reached out to the Foundation to provide visibility on this issue and explore potential paths forward.
3. RFI Submission Delay
The council noted that the delay involving MetaBeast’s RFI submission resulted from the wrong form being reviewed. Fehz acknowledged responsibility for the delay, and MetaBeast was notified through the forum.
A new RFI round will open after a response has been sent. To prevent similar delays, a bot notification will be configured to alert the team whenever a new RFI form is submitted.
4. 2030 Plan
For the past several months, the council has been actively developing a comprehensive framework for the 2030 plan. This work has involved extensive research, analysis of current project trajectories, and consideration of potential future scenarios for the ecosystem. Building on this progress, the council has agreed to schedule a meeting next week to continue working on the plan.