Celodex
Celodex's 2021 design paired pool-based swaps with planned exchange aggregation
Celodex's 2021 design paired an automated market maker with plans to find swap routes across other Celo exchanges. An automated market maker, or AMM, uses pooled tokens and programmed pricing rules to support exchanges. The proposed aggregator would look for routes involving Ubeswap and SushiSwap. Both functions addressed token swaps, with different relationships to the liquidity behind a trade. Comparing them meant considering the available pools, the proposed exchange path, and the final output after applicable costs. PolyDEX introduced this design in its November 6, 2021 announcement. That historical plan doesn't establish which services or routes are accessible today.
Pool pricing and route selection had different roles
The AMM supplied a pool-based exchange mechanism; the planned aggregator extended route selection to supported liquidity venues on Celo.
Pricing against pooled assets
The AMM connected an exchange price to tokens held in liquidity pools. A pool's available assets constrained the trades that it could support. Liquidity providers supplied those assets, and the launch design linked their earnings to trading fees.
Selecting exchange paths
The proposed aggregator would search beyond a single exchange's liquidity. Its initial targets were Ubeswap and SushiSwap on Celo, with further integrations planned. Multi-routing described the search for exchange paths through supported venues. The announcement's ambition to find competitive rates didn't establish that aggregation would outperform the AMM for every trade size or token pair.
Swapping, providing liquidity, and compounding served different tasks
For a trader, a proposed route through Ubeswap would identify a source of liquidity for the swap. CeloVAULT had a separate proposed role in compounding income from liquidity.
| 2021 option | Role of liquidity |
|---|---|
| AMM token swap | Liquidity in the AMM's pools supported the exchange path. |
| Planned aggregated swap | The proposed route would use liquidity from supported Celo venues, initially Ubeswap and SushiSwap. |
| Providing liquidity | Providers supplied pool assets and could earn trading fees from swaps. |
| Proposed CeloVAULT compounding | The planned service concerned automatic compounding on liquidity, separately from swap routing. |
A route preview involving another exchange therefore described the intended swap path. It didn't, by itself, establish a farming deposit or participation in CeloVAULT.
What did Celodex's route preview show?
The November 6, 2021 announcement described an interface that displayed multi-routing paths before a trader confirmed a transaction.
The preview described an intended exchange path. Seeing that path didn't demonstrate a completed swap or fix its eventual execution price.
Swap quotes needed the same cost basis
Comparing the same tokens and trade size gave AMM and aggregator quotes a common basis, before considering liquidity and costs.
Slippage and price impact
Price impact is the price change caused by a trade's effect on pool liquidity. Slippage is the difference between the expected price and the execution price. Both matter when interpreting a promise of a better swap rate. The aggregator plan sought lower slippage through multi-routing, but that objective didn't quantify an improvement for any particular exchange.
A route could only use the liquidity available through its supported venues. A venue's inclusion in the plan didn't establish that every token pair had a usable route.
Trading costs and received output
Any applicable trading fee, aggregator charge, and network cost belongs in the comparison. The quote's treatment of those costs matters: an amount before fees and an amount after fees are different quantities. A higher quoted output can lose its advantage when a comparison accounts for additional charges.
The initial venue list described a starting scope
Ubeswap and SushiSwap were the named initial aggregation targets in the 2021 plan, which also proposed adding other Celo exchanges. It didn't rank the venues by execution quality or identify the best one for every possible trade.
Plans for expansion don't establish which additional integrations subsequently appeared. Similarly, an old interface description doesn't confirm present access, pool liquidity, or executable quotes. Those changing conditions would decide a current choice between an AMM route and an aggregated one.
AMM ancestry and network coverage were separate facts
Celodex's announced deployment context was Celo, while its AMM description referenced designs associated with other networks. Shared design ancestry doesn't itself move a balance between chains or establish a cross-chain swap route. The proposed aggregator's initial integrations concerned exchanges on Celo. The announcement identified the AMM's foundations as PancakeSwap on Binance Smart Chain and PolyDEX on Polygon.
Common questions about Celodex
Did the 2021 announcement specify a fixed Celodex swap fee?
The 2021 launch announcement didn't specify a numerical Celodex swap fee. Its description of PolyDEX's trading fee as attractive didn't set a fee for the Celo exchange. Any applicable AMM fees, aggregation charges, and network costs would need their own treatment in a comparison of actual trade costs.
Was the AMM's stated ancestry evidence of a completed security audit?
Design ancestry alone doesn't establish a security audit of a particular deployment. The 2021 announcement referenced PancakeSwap and PolyDEX as foundations for the AMM, without identifying an audit's scope or findings.
Could a farming multiplier measure the savings on a swap?
Farming multipliers described the allocation weight of CLX incentives, not a discount on a swap. In the 2021 plan, the CELO/CLX pool carried X10. That weight didn't mean a trader received ten times the output, a tenfold return, or a particular reduction in trading fees.
Were CeloVAULT performance fees intended as a rebate to every swapper?
The 2021 CeloVAULT plan described support for CLX and PLX through performance fees, without defining a per-swap rebate. That proposal concerned the separate yield-optimization service. Supporting ecosystem tokens didn't specify an individual payment recipient, a rebate amount, or a discount that applied to every token exchange.
How was CeloLAUNCH different from the proposed swap aggregator?
CeloLAUNCH's planned role was project fundraising, separate from the aggregator's token-swap routing. The launchpad proposal connected projects seeking capital with potential participants. Its inclusion in the wider ecosystem didn't make it another exchange venue in the initial routing plan that named Ubeswap and SushiSwap.
Does the term multi-routing specify how many transactions a swap needs?
Multi-routing describes exchange paths without specifying a fixed transaction count. The 2021 announcement discussed displaying those paths before confirmation, but didn't define a transaction count or approval sequence. Its description therefore doesn't establish one on-chain transaction per venue or another particular execution arrangement.
Last updated -