Streamlining Mento Reserve Pairs

Governance Governance Proposals
,
1

Summary

This proposal seeks to optimize the current set of trading pairs within the Mento Protocol by simplifying the asset routing architecture. Specifically, we propose to deprecate several lower-utilization pairs that have become operationally burdensome and instead consolidate liquidity routing through a cUSD-centric model. Additionally, this proposal introduces new core pairs with cUSD and updates several protocol parameters (like spreads, limits, circuit breakers, etc.) following a holistic review of the current system.

Motivation

As the number of assets and pairs supported by the Mento Protocol has grown, maintaining them individually—especially those with lower usage—has introduced increasing operational and technical complexity. Additionally, many of these pairs require dedicated oracle feeds and liquidity calibration, which do not yield commensurate utility.

We propose a shift toward a more streamlined architecture where all major assets are routed through cUSD, which is already the most liquid and widely used stable asset on Celo. This shift allows us to:

  • Improve maintainability and monitoring across the Mento Protocol

  • Unify swap paths over cUSD (e.g., cREAL → cUSD → USDC instead of cREAL → USDC directly)

  • Minimize redundant oracle dependencies

  • Preserve the ability to swap between any two assets via composed two-hop routes

Importantly, these changes will not remove any user-facing functionality; all swaps will remain possible through the updated routing logic.

Specification

Pairs to Remove

The following pairs are proposed for deprecation:

  • cEUR / CELO

  • cREAL / CELO

  • eXOF / CELO

  • cREAL / USDC

  • cEUR / USDC

  • cEUR / axlUSDC

  • cREAL / axlUSDC

  • eXOF / axlEUROC

These pairs will no longer be directly maintained, but all swaps will remain executable through intermediate routing via cUSD.

Pairs to Add

To enable complete swap coverage via cUSD, we propose adding the following base pairs:

  • cUSD / cEUR

  • cUSD / cREAL

  • cUSD / eXOF

These additions ensure that all stable assets in the Mento Protocol can route to one another in two hops or fewer.

Parameter Review

In conjunction with this proposal, Mento Labs has conducted a comprehensive review of all active pair parameters. Based on this analysis, we will propose adjustments to:

  • Trading spreads

  • Trading limits

  • Oracle circuit breakers

  • Reference asset volatility thresholds

These parameter changes are intended to enhance market efficiency, reduce slippage, and strengthen Reserve robustness.

Next Steps

We plan to present this proposal in more detail during the upcoming Celo Governance Call and share the exact proposed parameters in a follow up forum post. Feedback from the community will be incorporated before submitting the on-chain governance proposal.

We look forward to engaging with the Celo community on this proposal and welcome your thoughts, questions, and suggestions in the forum thread below.

5 Likes
2

Hi @n-mlabs is this a Mento governance proposal or a proposal aimed only for the Celo Governance?

3

Hey @0xGoldo, this will be a Celo Governance proposal only

1 Like
4

One question regarding fees, is the user charged twice if there are two hops, or just once per trade?

2 Likes
5

Good question @martinvol!

6

I understood the idea but it is important to review the financial consequences!

7

Fees in pools will function similarly to any other DEX, where using a router to perform multiple hops will incur multiple pool fees. With this update, we’re focusing on security first and improving the way we can offer these pools without risk to the LPs (currently the Mento Reserve, but in the upcoming Mento V3, anybody will be able to provide liquidity).

We will explore fee optimisation further in V3, depending on how this impacts our users. However, in general, and also in off-chain FX markets, most trading occurs through a unified quote currency, and when hopping, you will incur a spread from both A/USD and B/USD. The alternative is liquidity fragmentation across many-to-many asset pools; however, for high-throughput paths, we can explore spinning up specialized pools.

7 Likes
8

Thanks @n-mlabs and team for the proposal, at my end this proposal is fulfilling all the requirements:

  • Post a proposal in the Celo Forum and leave it for discussion at least for seven (7) days.
  • Present Proposal in a Governance Call and address the feedback received: Proposal was presented during Celo Governance Call #69 | Jun 12th, 2025

With the above said, from my end the proposal is ready to move into the voting phase when proposer wants to move forward or consider is appropriate.

:bangbang: Remember Current Celo Governance Overview & Procedures

To proceed to the submission and voting phase at least two Celo Governance Guardians must post explicitly that the proposal fulfills the requirements to be able to move into the Voting Stage in the proposal thread on the Celo Forum.

Remember next steps

  • Submission of PR to Celo Governance Repository
    Proposers needs to fork the Celo Governance Repository and add a PR including the proposal .md file and json file.
  • Approval of PR by Celo governance Guardians and merge into main branch of Celo Governance Repository.
    Celo Guardians are responsible for conducting a comprehensive review of every Pull Request (PR) to ensure that there is complete alignment and consistency between the final proposal posted in the forum post and the specific files that are being requested to be merged.
    This review process is strictly technical in nature, focusing solely on verifying the authenticity and good faith of the proposers. It does not involve any personal opinions or biases regarding the merits or content of the proposal itself. To maintain the integrity of the Celo Governance repository, it is mandatory to obtain approval from a minimum of two Governance Guardians for each PR before it can be merged into the main branch.
  • OnChain Submission of Proposal
    After PR is merged into main Governance Repo the proposers needs to fork locally the Celo Governance Repository and submit the proposal onchain using the guidelines described in the Celo Docs.

CC: Governance Working Group (@annaalexa @Wade @0xGoldo)

1 Like
9

Thanks to @n-mlabs and the crew—this proposal ticks every box:

  • Forum post has been live for the required 7 + days.
  • Presented on Governance Call #69 (12 June 2025).

From my perspective, it’s ready for the voting phase whenever the proposer chooses.

2 Likes
10

Hi folks! CGP-187 (Streamlining Mento Reserve Pairs) is currently live and on the voting stage:

https://mondo.celo.org/governance/cgp-187

Hello everyone! For some reason I’m not able to post the verification steps for the proposal as we usually do, so please find them under the following notion page: