Methodology

How Betelgeuse routing works

Betelgeuse uses the source and destination you choose to request an appropriate route, then presents the result before wallet approval.

Same-chain EVM swaps

For a supported EVM network, Betelgeuse evaluates the configured same-chain route and returns the quote and execution details. The wallet may first approve an ERC-20 input and then sign the swap.

The route is not executed until the wallet confirms the transaction.

Cross-chain routes

For supported EVM-to-EVM and EVM-to-Solana directions, Betelgeuse requests a LI.FI route. A route can contain source swapping, bridging and destination execution.

The displayed destination estimate comes from the current provider response and can expire as conditions change.

Solana routes

Same-chain Solana swaps use Jupiter quote and transaction building. Solana-to-EVM routes use the cross-chain path and are signed through a compatible Solana wallet.

Network choice, token identity, wallet address and amount are inputs to the route—not interchangeable labels.

What you should verify

Routing reduces the work needed to assemble a transaction, but it does not remove the need to inspect it.

  • Source and destination networks
  • Token names and contracts or mints
  • Expected and minimum output
  • Slippage setting
  • Receiving address
  • Wallet transaction details

Common questions

Before you continue

Does Betelgeuse guarantee the displayed quote?

No. Quotes are estimates from current routing conditions and can change before execution.

Which providers does Betelgeuse use?

The app uses its configured EVM routing path, LI.FI for supported cross-chain routes and Jupiter for same-chain Solana swaps.

Who approves the transaction?

The user reviews and signs the transaction in the connected source wallet.