How TrueCost is calculated
Calculation version truecost-v3. Every displayed total can be traced back to raw provider fields via the calculation trace on each route card.
How amounts are valued
When source and destination are provably the same asset — an exact contract-address match in our reviewed registry, never a symbol guess — both sides are valued at one consistent reference price, so sending 1,000 USDC and receiving 997.5 USDC always shows the real ~2.5 USDC loss. When assets differ, both sides are valued from one fresh, timestamp-checked independent price snapshot. Provider-side fiat values are not used for ranking when that snapshot is missing or stale. If the valuation evidence still conflicts, the cost is shown as unavailable rather than as a misleadingly precise number.
What we compare
For each candidate route we value, in your chosen comparison currency (EUR via the ECB daily reference rate, or USD):
- Input value — the market value of what you send, at quote time.
- Expected output value — the market value of what is expected to arrive.
- Separately paid gas — network fees paid on top from your native balance.
On each result, conversion, route and included costs is the value lost between what you send and what arrives. It already contains any provider charges that are taken from the transfer, so those are never added again. Network gas paid separately is the only cost added on top.
value loss = max(0, input value − output value)
all-in cost = value loss + separately paid gas
net outcome = output value − separately paid gas
effective cost (bps) = all-in cost ÷ input value × 10,000
Why fees are not simply added up
Provider fee line items are usually already deducted from the amount that arrives. Adding them to the value loss would count them twice. Fee components are therefore an explanatory breakdown of the value loss; only separately paid gas is added on top, exactly once.
Data quality
- All arithmetic uses arbitrary-precision decimals; rounding happens only at display.
- The minimum received amount is never rounded upward; sub-cent values show as <$0.01.
- Routes with missing prices or inconsistent fee data are marked cost data incomplete and excluded from cost and output sorting.
- Estimates expire after at most 60 seconds and their exact age is always displayed.
- Powered by CoinGecko. CoinGecko supplies the independent reference prices used for cross-asset estimates and does not recommend or endorse any displayed route. The price data must be no more than 120 seconds old, with no more than 30 seconds between the two observations.
Sorting — you choose
Routes are ordered only by the criterion you select: highest estimated value after gas, lowest estimated all-in cost, fastest estimated time, or fewest estimated steps. “Highest estimated value after gas” compares the estimated value of what arrives, in your comparison currency, minus network gas paid separately. It is a value comparison, not a count of tokens received. Each result is a different provider or technical route for the same requested outcome. Mugano never labels a route “best”, “recommended”, “suitable”, “safest”, or “guaranteed cheapest”, and provider recommendation tags are removed from the data. If no route has reliable enough cost data for the selected financial sort, the page says that cost comparison is unavailable and shows the routes in neutral order.
Estimates, not offers
Mugano TrueCost provides independent cost estimates and analytics. Mugano does not connect to your wallet, prepare, recommend, route or execute the displayed transfer. Figures depend on third-party protocols and market conditions and are not guaranteed.