Allbridge supports native stablecoin transfers through Core and broader token swaps through Next
Allbridge moves assets between blockchains through products that differ in their supported token types. Core handles native stablecoin transfers through established cross-chain standards. Next combines bridging with token conversion, while deprecated Classic supported native and wrapped assets and is scheduled to stop in November 2026.
Token Type and Destination Asset
The asset that you hold and the token that you need on the destination chain determine which transfer model fits. The products differ in how they move value and what token representation arrives. Route support varies by product as well as by token type.
Core for Native Stablecoins
Core focuses on dollar-pegged USDC, USDT, and USDe through their supported native transfer standards. Its model delivers the stablecoin that the selected route supports without creating an Allbridge-wrapped asset.
Next for Token Conversion
Next supports stablecoins and native gas tokens, with swapping and bridging available in a combined flow. Its send and receive selections matter when the task involves changing the asset as well as the chain. That scope differs from Core's native stablecoin transfer model.
Classic for Legacy Representations
Classic supported both native and wrapped token transfers across EVM and non-EVM chains. A wrapped token represents an asset through a separate token deployment. Classic's legacy routes therefore involved token-representation choices that Core's native model avoids.
Core Transfer Standards
Core selects the transfer mechanism available for the chosen asset and blockchain pair. Its contracts prepare the transfer and collect fees, while the underlying protocol handles token movement. The native transfer model has no liquidity-pool exchange rate or price impact: its protocols move token units, with displayed fees determining the deductions.
USDC Through CCTP
Circle's Cross-Chain Transfer Protocol, or CCTP, uses a burn-and-mint mechanism for USDC. Core supports CCTP and CCTP V2 where the route provides them. The protocol establishes the source and destination token movements; Core supplies the transfer interface around that mechanism.
USDC-Backed Assets Through xReserve
Circle's xReserve supports routes involving USDC-backed stablecoins, so the destination asset can be a backed token rather than USDC itself. This distinction matters when an application requires a particular stablecoin deployment. A backing relationship does not make two token identities interchangeable.
USDT and USDe Through OFT
USDT and USDe transfers use LayerZero's Omnichain Fungible Token, or OFT, standard. Core connects to the supported deployments for the selected route. Each mechanism governs token movement and verification for its supported routes.
Next Swaps and Cross-Chain Gas
Next combines asset conversion with bridging when a supported task requires a different destination token. This expands the choice beyond transferring a stablecoin through its native standard. Native gas-token transfers and destination top-ups also support activity on the receiving chain. Its routing can use OFT, CCTP, or intents. The selected pair determines the applicable route and quoted cost. Next's available send and receive options determine which token and chain pairs you can use.
Which Networks Support Core Transfers?
Core supports EVM networks and several non-EVM ecosystems, including Tron, Solana, Sui, and Stacks. Its EVM coverage includes Ethereum, Polygon, Avalanche, Arbitrum, Base, Optimism, and Unichain. EVM refers to the Ethereum Virtual Machine environment, which these networks support.
A chain's inclusion does not establish support for every stablecoin or direction. The asset, source chain, destination chain, and available native mechanism jointly define a route. Stellar support in Core is temporarily unavailable while its Stellar CCTP implementation awaits an audit. Core includes Tron USDT, which Classic did not support. Next lists Stellar among its supported networks.
Fees, Fee Tokens, and Destination Gas
Core separates the percentage service charge from the cost of destination execution. The route quote gives the applicable breakdown before signing.
Service and Relayer Charges
Core's published service fee for native transfers is 0.1% of the transferred amount. The relayer fee covers destination execution and varies with that chain's transaction costs. A percentage alone therefore cannot express the complete transfer cost.
Fee Payment and Gas Top-Ups
Relayer fees and optional gas purchases can use the source gas token, transferred stablecoin, or ABR0. ABR0 provides a relayer-fee discount. A gas top-up supplies destination gas for later transactions; its cost is separate from the stablecoin transfer's service charge.
A Hypothetical Core Fee Calculation
Consider a hypothetical 742 USDC transfer on a supported Core route, with the service charge deducted from the amount. Applying the published 0.1% rate gives 742 multiplied by 0.001, or 0.742 USDC.
Subtracting the service charge leaves 741.258 USDC before other deductions. This subtotal excludes the variable relayer charge and any optional gas purchase. The actual received-amount quote incorporates the selected fee-payment settings. Changing the transfer amount changes the percentage charge; changing destination execution costs can change the relayer charge independently.
How Does a Core Transfer Reach the Recipient?
A Core transfer reaches its recipient after source processing, protocol verification, and destination execution, following the rules of its selected transfer standard. The source contract collects fees and passes tokens to the underlying mechanism, which burns or locks them as its design requires. A confirmed source transaction enables protocol verification; signing alone does not establish submission or completed destination delivery.
Protocol verification connects the source action to the destination action. Circle supplies attestation for CCTP and xReserve routes, while LayerZero provides verification for OFT routes. Relayers then submit the destination transaction that releases tokens to the specified recipient. This arrangement separates the user's source transaction from the execution that delivers funds on the receiving chain.
The app tracks transfer progress and retains past transfers in its history.
Core Explorer exposes transfer details, including chains and messaging protocols. A source transaction identifier points to the initial transaction. A successful destination transaction records the later token movement. Reading those records as separate stages helps distinguish a confirmed send from a completed cross-chain transfer.
Pool Closure and Product-Specific Security
Core discontinued its liquidity pools in July 2026 following a security incident. Its native-transfer model operates without intermediate bridge-owned liquidity pools. Liquidity provision through the discontinued pools is separate from the active native transfer service. Former liquidity providers have a dedicated compensation page; that process is separate from an ordinary transfer.
Security reviews concern specific implementations. Quarkslab reviewed Core's Soroban implementation, and Blaize Security reviewed its Sui bridge. Kudelski Security also reviewed Core. An audit of one implementation does not establish another route's availability or eliminate the risks of its underlying contracts. Core's non-custodial architecture assigns token movement to CCTP, xReserve, and OFT contracts, so those protocol dependencies remain relevant.
Classic's Deprecation and Legacy Token Models
Classic supported native-to-native, native-to-wrapped, wrapped-to-native, and wrapped-to-wrapped transfers between compatible blockchains. Those routes distinguished the token sent from the representation received. A destination application's accepted token therefore mattered alongside chain support. Each token deployment also had its own compatibility requirements.
Classic is deprecated. Allbridge Classic is scheduled to stop in November 2026.
Classic's fee system included reductions through source-chain ABR staking. Core's ABR0 relayer-fee discount belongs to a different payment model and has separate terms.
Developer Interfaces and Embedded Transfers
The Core SDK supports adding cross-chain transfers to another protocol or application. The SDK, integration guidelines, and technical reference address programmatic use, implementation examples, and the underlying interface. Together, these resources support an embedded transfer entry point alongside the standalone app. An integration still needs the supported source and destination assets, the recipient address, and applicable fee information. Changing the surrounding interface does not create an unsupported route or change a token's identity. The native transfer mechanism remains responsible for token movement, while the application presents the transfer task and its necessary inputs.
Recipient Compatibility Before Signing
The receiving address and delivered token must fit the selected destination blockchain. An EVM-compatible address does not establish compatibility with a non-EVM destination. The token's chain deployment also matters when funds will enter another application. A matching ticker can describe different native, backed, or wrapped representations.
Recipient and token compatibility belong before transaction confirmation. Fee-payment choices determine which balance pays the applicable charges, and destination gas affects later wallet activity. A completed transfer can still leave an application unable to use the asset if it does not accept the delivered token.
Things people ask
How Long Does an Allbridge Core Transfer Take?
Core's interface provides an estimated transfer time for the selected route. That estimate reflects historical transfer data rather than a fixed completion deadline. Source confirmation, protocol verification, and destination execution affect progress, so a recorded source transaction alone cannot establish that the destination transfer has finished.
Do I Need to Connect a Destination Wallet for a Core Transfer?
Core accepts a pasted destination address as an alternative to connecting the receiving wallet. Its relayers execute the destination transaction, so the recipient does not need destination gas merely to receive the transfer. Optional gas top-ups concern subsequent transactions that the recipient wants to make on that chain.
What Does an EVM Token Approval Authorize in Core?
A token approval permits the bridge contract to access the authorized token amount. The Core app requests approval for the exact amount needed, and most wallets let you review that amount before confirming. Approval and sending are separate operations: permission to access tokens does not establish that a cross-chain transfer has completed.
Does non-custodial Mean That Allbridge Transfers Are Confidential?
Non-custodial describes control of funds; it does not promise confidential transfer amounts or routes. Next presents confidential transfers as a forthcoming feature. Its ordinary bridging flow should not be assumed to conceal the transferred amount or cross-chain route.
Are Core Bridge Fees the Same as Source Blockchain Gas Charges?
Core's bridge-fee breakdown and the source blockchain's transaction charge are separate cost inputs. The wallet confirmation shows the blockchain charge for the transaction being signed. Paying a relayer fee in a stablecoin does not mean that the source blockchain transaction has no gas cost.
Can a stablecoin's Dollar Value Change Even When Core Has No Price Impact?
Core's no-price-impact property describes its transfer mechanism, not a guarantee of the stablecoin's market price. Native transfers do not use a liquidity-pool exchange rate. Fees affect the token amount received, while a stablecoin's dollar value remains a separate property of the asset.