> For the complete documentation index, see [llms.txt](https://productcommittee.docs.intersectmbo.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/20th-february-2025-3.md).

# 12th August 2025

The session was run in the related [miro board](https://miro.com/app/board/uXjVKro_lxs=/).&#x20;

📽️ The meeting recording can be found [here](https://drive.google.com/file/d/16obeywAQbyUGl2o4tkZzpj37NpDB4V4G/view?usp=sharing).

## Participants

| Name                    | Role                               | Attendance |
| ----------------------- | ---------------------------------- | ---------- |
| Samuel Leathers         | Chair                              | Yes        |
| Lorenzo Bruno           | Secretary                          | No         |
| Alexandre Maaza         | Voting Seat (Vice-Chair Appointee) | Yes        |
| Juan Sierra             | Voting Seat                        | Yes        |
| Yoram Ben-Zvi           | Voting Seat                        | No         |
| Alexa C. (Thyme Studio) | Voting Seat                        | Yes        |
| James Meidinger         | Voting Seat                        | Yes        |
| Christian Schmitz       | Voting Seat                        | No         |
| Giorgio Zinetti         | Voting Seat                        | No         |
| Samir Idris             | Voting Seat                        | Yes        |

## Agenda

* Review actions and updates
  * Product Research milestone updates from Wada, Tymfa and NexTrium
* Product Research presentation from Ben
* Discuss the Ecosystem Funding Working Group based on Alex’s document
* Review the KPI survey as the Product Committee

## Updates

* **Review actions and updates**
  * **Product Research milestone updates from Wada, Tymfa and NexTrium**
    * The Chair reported that three Product Research projects had completed their first milestones for Committee review, while six of the seven research contracts had been signed.
* **Product Research presentation from Ben**
  * The Committee received an update on the vertical approach research, including work to define and assess potential verticals, develop a framework for their progression, and test it against Bitcoin DeFi, agricultural supply chains and government use cases.
* **Discuss the Ecosystem Funding Working Group based on Alex’s document**
  * The Committee reviewed the ecosystem funding architecture work, including the completed ecosystem diagnostic, development of the draft architecture, stakeholder consultation and plans to hand the work over for broader community engagement through Intersect.
* **Review the KPI survey as the Product Committee**
  * The Committee reviewed the KPI survey, identified adoption and utility as its primary relevant pillar, discussed limitations in measuring existing KPIs including monthly active wallets, and considered additional measures including economic value settled on-chain and agentic activity.

## Outcomes & Recommendations

N/A

## Decisions Recorded

N/A


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://productcommittee.docs.intersectmbo.org/committee-meeting-notes/2026/20th-february-2025-3.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
