docs: answer recurring assistant questions on availability, rewards, programs and facilitator trust - #2352
Conversation
…ewards, programs, partnerships and facilitator trust Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…e builder programs Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
palango
left a comment
There was a problem hiding this comment.
Thanks for picking these up from the assistant reports. Three things need fixing before this goes in.
The MiniPay availability link returns 404 in both places it is used. The MiniPay docs site serves that page at https://docs.minipay.xyz/getting-started/availability.html, which is also how build-on-celo/build-on-minipay/overview.mdx links into that site. The content behind it is right (Nigeria is available on Android, iOS and Opera Mini), so it's only the URL.
"Celo does not run a rewards or points program" is not true as written. CELO holders earn epoch rewards for locking and voting (/home/protocol/epoch-rewards/index, and self-custody.mdx walks through it), and Celo Devs runs Proof of Ship as a monthly builder rewards pool (https://www.celopg.eco/programs/proof-of-ship). The "As a Builder" section the sentence points to doesn't mention Proof of Ship either. I'd say Celo has no points or task-reward program, link epoch rewards for holders, and name Proof of Ship under builders.
The new facilitator checklist asks readers to confirm a facilitator's source is public, but line 74 of the same page says the Celo facilitator's source is a private repo. So the recommended default fails the first check, and the assistant will run into that when someone asks whether the facilitator can be trusted. Either drop the public-source criterion or say plainly that the Celo facilitator's source is private and that trust rests on transferWithAuthorization being non-custodial.
Smaller points are inline. One is whether X DMs to @celo are really where partnership requests should go; I couldn't confirm that, and it's a channel scammers like to imitate.
| - [Homepage](https://www.opera.com/products/minipay) | ||
| - Platforms: [Android](https://play.google.com/store/apps/details?id=com.opera.minipay), [iOS](https://apps.apple.com/de/app/minipay-easy-global-wallet/id6504087257?l=en-GB), inside [Opera Mini](https://play.google.com/store/apps/details?id=com.opera.mini.native) in Ghana, Nigeria, Kenya, South Africa, and Uganda | ||
| - Platforms: [Android](https://play.google.com/store/apps/details?id=com.opera.minipay), [iOS](https://apps.apple.com/de/app/minipay-easy-global-wallet/id6504087257?l=en-GB), and inside [Opera Mini](https://play.google.com/store/apps/details?id=com.opera.mini.native) | ||
| - Availability by country, platform and Opera Mini: the [MiniPay availability list](https://docs.minipay.xyz/getting-started/availability) |
There was a problem hiding this comment.
This URL returns 404 when loaded directly. The MiniPay docs serve the page at https://docs.minipay.xyz/getting-started/availability.html (their own nav links it that way).
|
|
||
| - [**Explore Projects on Celo:**](https://celo.org/ecosystem) Start using and engaging with Celo apps. | ||
| - [**Follow updates from Celo Core Co on Twitter**](https://x.com/Celo) | ||
| - **Rewards:** Celo does not run a rewards or points program. Individual apps, including Mini Apps in MiniPay, run their own reward programs, so ask the app. Builders can find programs under [As a Builder](#as-a-builder). To check where MiniPay is available, see the [MiniPay availability list](https://docs.minipay.xyz/getting-started/availability). |
There was a problem hiding this comment.
CELO holders do earn protocol rewards for locking and voting (/home/protocol/epoch-rewards/index), and Celo Devs runs Proof of Ship for builders, so "does not run a rewards or points program" will mislead. Suggest something like: "Celo has no points or task-reward program. CELO holders can earn epoch rewards by locking CELO and voting for a group. Rewards inside apps, including MiniPay, are run by those apps." The MiniPay link here also needs the .html suffix (it 404s without it).
| - **Introduce your project** in the [**Celo Forum**](https://forum.celo.org/) in the founders' category. | ||
| - **Explore grant opportunities:** Apply for [Prezenti Grants](https://www.prezenti.xyz/). | ||
| - [**Subscribe to the Celo Developers newsletter:**](https://celo-devs.beehiiv.com/subscribe) Get developer programs, grants, and builder updates in your inbox. | ||
| - **Developer programs:** follow [Celo Devs on X](https://x.com/CeloDevs) for announcements. |
There was a problem hiding this comment.
Naming Proof of Ship here (https://www.celopg.eco/programs/proof-of-ship) would answer the "what programs are there" question directly. The rewards bullet above sends readers to this section, and right now it doesn't list any rewards program.
| - **Explore grant opportunities:** Apply for [Prezenti Grants](https://www.prezenti.xyz/). | ||
| - [**Subscribe to the Celo Developers newsletter:**](https://celo-devs.beehiiv.com/subscribe) Get developer programs, grants, and builder updates in your inbox. | ||
| - **Developer programs:** follow [Celo Devs on X](https://x.com/CeloDevs) for announcements. | ||
| - **Partnerships:** send partnership requests to [Celo on X](https://x.com/Celo). |
There was a problem hiding this comment.
Is @celo on X actually where partnership requests are triaged? I couldn't find that stated anywhere. Telling people to DM a brand account also helps impersonators. If there is a form or an address, link that instead.
| ## Other facilitators | ||
| ## Trust and other facilitators | ||
|
|
||
| The Celo facilitator at `https://api.x402.celo.org` is built and run by Celo, and it never custodies funds: `transferWithAuthorization` moves tokens directly payer → payee inside the token contract. |
There was a problem hiding this comment.
Line 66 says this is built on the open-source x402-rs, so "run by Celo, built on x402-rs" is more accurate than "built and run by Celo". The non-custody clause repeats line 66 word for word.
|
|
||
| A facilitator you do not know deserves the same checks as any other service that submits transactions for you: | ||
|
|
||
| - Confirm who operates it and that its source is public. |
There was a problem hiding this comment.
Line 74 says the Celo facilitator's source is a private repo, so the recommended default fails this check. Either drop "source is public" or address it directly for the Celo facilitator.
| A facilitator you do not know deserves the same checks as any other service that submits transactions for you: | ||
|
|
||
| - Confirm who operates it and that its source is public. | ||
| - Before your server accepts a payment, check the asset, amount and `payTo` address against what you priced. Do not rely on the facilitator's response alone. |
There was a problem hiding this comment.
Worth adding that you should confirm the settlement transaction on-chain before delivering anything valuable. A facilitator can't redirect funds, because the payer signs to and value, but it can claim a settlement that never happened.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
|
Review points addressed in ddf14c2.
I left out any statement about what Celo staff will or won't ask over direct messages, since nothing on the site states such a policy.
|
palango
left a comment
There was a problem hiding this comment.
Thanks, this covers everything I raised. The MiniPay link resolves, the rewards line is accurate and points holders at epoch rewards, and the facilitator checklist no longer contradicts the page. You're right about Proof of Ship: the repo was archived in June, so please ignore that suggestion. This merges cleanly with #2349 and #2350, and after #2350 the availability link sits on the end-user wallet page, where it belongs.
Two optional nits inline on x402.mdx.
|
|
||
| <Note> | ||
| Source: `celo-org/x402-facilitator` (private repo). The endpoints below are live at `https://api.x402.celo.org` (mainnet) and `https://api.x402.sepolia.celo.org` (Celo Sepolia). | ||
| The endpoints below are live at `https://api.x402.celo.org` (mainnet) and `https://api.x402.sepolia.celo.org` (Celo Sepolia). |
There was a problem hiding this comment.
With the source line gone, this Note only repeats the base URLs from line 71 and the endpoint list below it. I'd drop it.
| ## Other facilitators | ||
| ## Trust and other facilitators | ||
|
|
||
| The Celo facilitator at `https://api.x402.celo.org` is run by Celo and built on [`x402-rs`](https://github.com/x402-rs/x402-rs). |
There was a problem hiding this comment.
Optional: someone will ask whether the Celo facilitator is open source, and the page no longer says. If we're comfortable stating publicly how much of it is upstream x402-rs, a short clause here would answer that. Fine to leave as is.
Refs #2314, #2320, #2324, #2343
Answers the recurring in-scope questions from the assistant's unanswered-question reports that need a statement rather than a new page.
What changed
home/wallets: MiniPay entry links the MiniPay availability list (https://docs.minipay.xyz/getting-started/availability.html, by country, platform and Opera Mini) instead of the hand-written five-country subset.contribute-to-celo/index: states that Celo has no points or task-reward program, links epoch rewards for locking CELO and voting, and says rewards inside apps (including MiniPay Mini Apps) are run by those apps; links the MiniPay availability list; developer programs point to Celo Devs on X; partnerships go through the Celo Discord or X (Celo, Celo Devs).build-on-celo/build-with-ai/x402: "Other facilitators" becomes "Trust and other facilitators": the Celo facilitator is run by Celo and built on x402-rs; a short checklist for any other facilitator (confirm the operator, check asset/amount/payTobefore accepting, confirm the settlement transaction on-chain before delivering anything valuable, test on Celo Sepolia). The page no longer names or describes the facilitator's source repository.No new addresses or numbers; the Celo facilitator URLs were already on the page.
Verification
The three changed pages were also viewed under
mint devwith Playwright, and the MiniPay availability URL returns 200.Overlap
#2349 and #2350 also edit
home/wallets.mdx(frontmatter and a different section); this PR touches only the MiniPay entry.🤖 Generated with Claude Code