# MiniPay Update Q1 2026

**URL:** <https://forum.celo.org/t/minipay-update-q1-2026/13273>\
**Category:** DeFi For The People\
**Created:** [May 5, 2026, 11:01am UTC](https://forum.celo.org/t/minipay-update-q1-2026/13273 "2026-05-05T11:01:58Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![camilosaka](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.celo.org/camilosaka/32/11644_2.png) [@camilosaka](https://forum.celo.org/u/camilosaka)\
**Post date:** [July 19, 2026, 6:00pm UTC](https://forum.celo.org/t/minipay-update-q1-2026/13273/2 "2026-07-19T18:00:30Z")

</div>

Hi @opera_minipay team — great update.

As someone helping bring builders into the Celo and MiniPay ecosystem in Colombia, I think one small resource could make a big difference: a public, lightweight wishlist of problems or Mini App categories that the MiniPay team would like builders to explore.

Today, builders often receive direct MiniPay feedback only after they have already built and submitted their app. Celopedia and Proof of Ship help earlier in the journey, but they cannot know which user needs MiniPay is currently observing or which categories are already sufficiently covered.

The wishlist could be as simple as:

- Problem or opportunity

- Relevant users or markets

- Current status: open, being built, covered or blocked

- Existing related Mini Apps

- Last updated date

As new Mini Apps launch, each opportunity could simply change status rather than disappear, since having an app does not always mean the problem has been fully solved.

Celopedia could surface this information to builders, while Proof of Ship helps the strongest teams move from idea to execution.

Would MiniPay consider maintaining a simple public wishlist like this?

---

_[View the full topic](https://forum.celo.org/t/minipay-update-q1-2026/13273)._