Fees, networks and risks

Supported networks and route availability

The current interface includes Base, Arbitrum, Ethereum, Optimism, Polygon, BNB Chain and Avalanche C-Chain. The stablecoin list is restricted to configured USDC, USDT and DAI contracts intersected with Bridgers’ live catalog. Not every stablecoin is available on every network, and a listed network does not guarantee every pair or amount has a route.

Five product-relevant directions were verified against the live catalog and validated read-only quotes for 100 source tokens on October 12, 2026. They were chosen from the existing interface, not from measured search-volume data. No approvals, orders or transactions were submitted.

A successful quote is a point-in-time result. Liquidity, provider limits and service availability can change; routes require fresh checks in the interface.

Fees and minimum received

• Provider fee: shown from the current Bridgers quote. There is no universal fixed fee asserted in these guides.
• Destination chain fee: shown in the destination token denomination supplied with the quote.
• Source network fees: presented by the wallet for approvals and the swap transaction. Approval may have a separate fee.
• Estimated output and minimum received: the estimate is the quoted output; the minimum reflects the reviewed quote and slippage settings. This is not an independent guarantee of provider delivery.

Use the displayed output and current wallet fee preview rather than manually adding quoted figures without understanding their inclusion. Network conditions, token amounts and the provider route affect costs. No fixed completion time is promised.

MetaMask may offer token-paid gas for eligible transactions on supported networks. Eligibility is determined by the wallet and its service; it is not guaranteed for every user or chain. Token-paid gas still has a cost. Native gas assets are ETH on Ethereum, Base, Arbitrum and Optimism; POL on Polygon; BNB on BNB Chain; AVAX on Avalanche C-Chain.

Provider routing and transaction status

SameSame integrates the Bridgers API for quotes and provider order information. SameSame’s interface is not itself a canonical network bridge, and the selected route must not be assumed to use a particular bridging protocol.

History uses locally saved orders for the connected wallet. Source confirmation and destination delivery are different. Delivery status is provider-reported, not an independent audit of destination settlement. Browser storage can be cleared, so local history is not a universal record across devices. Keep the provider order ID and source transaction hash for support.

Transaction risks and security-review scope

Smart-contract execution, approvals, provider settlement, receiving-address mistakes, network interruptions and stablecoin depegging can cause loss or delays. A token ticker or logo is not enough to identify a contract, especially for pegged or bridged representations.

The application retains transaction-intent checks, configured router and spender restrictions, duplicate-submission protection, recovery handling and wallet-scoped history. These controls do not amount to an independent security audit. Bridgers contract-code verification is not enabled in the current configuration; provider settlement guarantees and provider-side order authorization have not been independently verified. This SEO work does not change those controls or resolve those review gaps.

Public promotional calls to transact are held pending an appropriate independent review of the end-to-end swap workflow. Automated regression tests and read-only quotes alone are insufficient evidence of production readiness.

Support and order information

For provider order or delivery issues, use the official Bridgers website and its support options. Have the Bridgers order ID, source network and transaction hash available. Source explorer receipts and provider delivery status answer different questions.

For SameSame interface issues, contact @samesame_support on Telegram. Never disclose a seed phrase, private key or wallet recovery information to anyone claiming to offer support. Avoid publishing wallet addresses and order details unnecessarily.

Route guides and interface

SameSame interface — existing beta interface and product overview.