Security

Security model and swap checks

Betelgeuse prepares routes; your connected wallet remains the approval boundary. Security depends on verifying the assets, networks, addresses and transaction before signing.

Wallet-controlled execution

A quote does not move funds. The source wallet must approve the transaction prepared for the selected route. Read the wallet request and reject anything that does not match your intended trade.

Never share a seed phrase or private key. Betelgeuse does not need either one to prepare a quote.

Token and address verification

Symbols can be duplicated. Verify the network and token contract or Solana mint, particularly when using search or pasting an address.

Cross-chain routes also require a valid destination address for the receiving ecosystem. An EVM address and a Solana address use different formats.

Route and protocol risk

On-chain swaps can involve token contracts, liquidity pools, route providers, bridges and destination protocols. Smart-contract, bridge, liquidity and market risks cannot be eliminated by the interface.

Start with an amount appropriate for your risk tolerance and confirm route completion before repeating a transaction.

Practical checklist

Pause before the wallet signature and confirm the details.

  • Use the official betelgeuse.fi domain.
  • Verify network and token identity.
  • Check the destination address.
  • Review approvals and spending scope.
  • Keep enough native gas.
  • Track cross-chain routes to destination completion.

Common questions

Before you continue

Will Betelgeuse ask for my seed phrase?

No legitimate swap flow needs your seed phrase or private key. Never provide it to a website or support account.

Why should I verify a contract address?

Different tokens can use the same or similar symbols. The contract or mint identifies the actual asset.

Are cross-chain routes risk-free?

No. They can add bridge, provider and destination-protocol risks beyond a same-chain transaction.