bridge FAQ
EVM bridge questions and answers
find direct answers about selecting chains, identifying tokens, requesting routes, reviewing fees, signing transactions and tracking delivery.
- chain and token discovery
- route availability and timing
- fees, slippage and gas
- wallet safety and failed route recovery
frequently asked questions
what EVM chains are available in puddli?
puddli requests the current EVM mainnet list from LI.FI. the visible count can change as provider support changes.
does appearing in the chain list guarantee a route?
no. puddli requires a successful executable quote for the exact source token, destination token, amount and recipient.
what is the puddli fee?
the required puddli integrator fee is 0.5% of the source amount. a LI.FI route is rejected when the executable quote does not confirm it.
are provider and gas fees separate?
yes. route details show provider costs and estimated gas separately from the puddli integrator fee.
does puddli hold user funds?
puddli is non-custodial. users sign transactions from their connected wallet and funds move through the selected provider contracts.
how do i verify a token?
verify the chain, symbol and contract address. the same symbol may represent different contracts or bridged variants.
why is a route unavailable?
liquidity, provider coverage, token support, amount limits, rate limits or temporary network conditions can prevent a quote.
can i send to another wallet?
yes. enable the custom destination option and verify the EVM address before requesting the quote.
how do i track an unfinished bridge?
activity is stored locally with provider, chain, token and transaction information. use resume tracking to request the latest status.
is Arc handled like other EVM chains?
no. Base ↔ Arc uses a dedicated Circle Gateway adapter and requires both Arc RPC access and active Circle domain support.