Bridge FAQ

puddli loads current EVM mainnets from its routing catalog and also keeps dedicated configurations for certain networks. the visible list can change as live provider support changes.

no. a chain can be selectable while a specific token pair, amount or direction has no executable route. puddli only enables execution after a current quote succeeds.

yes. Robinhood Chain is included in puddli’s EVM chain registry and can appear in the chain selector. the exact transfer is only enabled when current routing data supports the selected tokens, direction and amount.

the labels come from the best live activity source currently available. when bridge-flow data is available, puddli can rank chains using bridge volume and active bridge wallets; otherwise supported chains can be ranked from recent active-address data. the labels are not manually assigned.

token lists are loaded for the selected chain from current provider data. a token can be missing because the provider does not index it, the contract is unsupported, liquidity is unavailable or the chain catalog has not exposed it yet.

check the selected network, token symbol and contract address. identical symbols can refer to different contracts, canonical assets or bridged variants on different chains.

different networks can have native USDC, older bridged USDC or other wrapped variants with separate contract addresses. verify the exact contract and destination asset before signing.

yes when the selected source and destination have a live route for native ETH or a route that converts native ETH into the requested destination asset. keep enough source-chain native balance for transaction gas.

liquidity, token support, provider coverage, amount limits, temporary network conditions or a missing source-to-destination connection can prevent a quote. changing the amount, token or destination can produce a different result.

timing depends on the selected route, source-chain finality and provider execution. use the current estimate shown by the bridge rather than a fixed time from a static page.

request a fresh quote before signing. output, route availability and execution data can change, so an old quote should not be treated as current.

the source transaction must be submitted from your wallet on the source network. keep enough of that network’s native gas asset available so the transaction can be executed.

yes. use the custom destination option when available and verify the destination EVM address carefully before requesting the final quote.

do not submit a duplicate source transfer just because delivery is taking longer than expected. check the source transaction, open puddli activity and refresh or resume tracking so the current provider status can be requested.

open the bridge activity view to see locally saved transfers and their latest known status. transaction hashes can also be checked on the relevant source and destination explorers.

no. puddli is non-custodial. you control the wallet and sign the transactions required by the selected route or dedicated bridge adapter.

verify the source chain, source token, destination chain, destination token, recipient, expected receive amount and the wallet transaction being requested. do not sign a transaction if those details do not match what you intended.

first check whether the source transaction was actually submitted. then use activity and provider status to determine whether the transfer is pending, failed or requires recovery. avoid creating a second transfer until the state of the first one is clear.

not always. configured Base and Arc transfers use a dedicated Circle Gateway flow and depend on Arc RPC health plus active Circle domain support, so their availability is checked separately.