Allbridge

Allbridge Classic used separate send and receive transactions to complete token transfers

Allbridge Classic used separate send and receive transactions to transfer native and wrapped tokens between blockchains. It is deprecated and scheduled to stop in November 2026. For a route still supported before closure, source confirmation must be followed by destination receipt, either manually or through a supported bridge-operated receiving method.

Source Requests and Destination Receipts

Classic's source-side transaction initiated the transfer, while its destination-side transaction delivered the selected token representation to the receiving address. Those actions belonged to different blockchains. A successful source transaction therefore established only that part of the transfer, even when the sending wallet already showed a lower balance.

The source request included the recipient address and transfer amount. In the smart-contract transfer model, Send locked native tokens or burned wrapped tokens. An off-chain validator checked that event before signing authorization for destination delivery. During Receive, the destination contract unlocked native tokens or minted wrapped tokens for the recipient.


Native and Wrapped Outputs

Classic's native and wrapped categories described the asset representation at each endpoint. A wrapped token was a minted representation, with its own identity on the receiving blockchain. Here, native described the original asset in that transfer model; it did not automatically mean the currency that paid network gas.

The supported transfer types covered native-to-native, native-to-wrapped, wrapped-to-native, and wrapped-to-wrapped movements. The selected route determined the applicable combination. Holding a wrapped asset therefore did not, by itself, establish whether another transfer would deliver an original token or another wrapped representation.

The receiving token mattered for subsequent use. An application that accepted one deployment did not necessarily accept a similarly named wrapped token. Match the destination asset to the token that the intended application accepts before authorizing a transfer. A shared ticker does not identify a token contract.

A completed wrapped-token delivery also did not perform an additional market swap. Converting that representation into another asset was a separate task.


Select the Route and Recipient

The route selection established the source blockchain, destination blockchain, and asset before the wallet authorized any transfer. Classic's interface used From, To, and Choose asset fields for those choices. For a transfer still available before shutdown, the wallet network and selected source asset must match that route.

The Recipient address field identified the destination account. In the manual receiving flow, access to a compatible destination wallet was necessary to submit Receive. Prepare that access and the required gas before Send. An address from another chain is suitable only if it also identifies the intended recipient on the destination chain; connecting a wallet later does not establish that the earlier address was correct.

Allbridge Classic: Select the Route and Recipient - diagram

View image file


Approval and the Send Transaction

The sending wallet needed any required token-spending authorization before the Send transaction could transfer the asset. Classic's MetaMask instructions included that approval before the first send. Connecting the wallet, approving token spending, and confirming Send represented different permissions and actions.

A spending approval authorized contract access to tokens. It did not establish destination delivery, and its transaction ID was not the Send transaction ID needed for Classic's receiving interface.

The send form recorded the chosen recipient and amount. After Send and wallet confirmation, the interface displayed a waiting screen with access to the source block explorer. That record provided the transaction's blockchain status. A wallet prompt disappearing or a browser tab closing supplied no equivalent confirmation.

Retain the successful Send record before moving to the receiving action. If multiple wallet requests appeared, distinguish an approval from a transfer and distinguish a successful transfer from a failed attempt. The relevant record is the one that actually initiated the movement toward the recorded recipient.

Bridge Fees and Network Gas

The Classic fee calculation depended on the source blockchain and any applicable staking reduction. Classic charged the bridge fee on the Send transaction. That fee used the transferred token. The amount and fee shown for the selected transfer need their own units; a charge in the transferred asset differs from a network gas charge.

A manually completed transfer required gas for both the source and destination transactions. Where ABR staking was available on the source chain, the fee reduction depended on the xABR pool-share tokens held by the sending wallet. A lower bridge fee did not remove network gas costs. Where receiving delegation was enabled, the destination contract deducted an additional execution fee from the unlocked or minted tokens before delivering the remainder.


Manual and Bridge-Operated Receiving

The destination chain and enabled receiving options determined who submitted the receiving transaction. Classic supported manual receiving except on XRP Ledger, optional delegation where enabled, and bridge-operated receiving for XRP Ledger destinations. Delegation used Finish for me and added a fee for destination execution. On XRP Ledger, the Receive action initiated the bridge-operated delivery process. In the documented SOLO flow from BNB Chain to XRP Ledger, the account needed a trust line to receive that token; without it, the interface requested a destination-wallet connection.


A Manual Wrapped-Token Receipt

In this hypothetical native-to-wrapped transfer, a manual route remains available before Classic's closure, the recipient controls the destination wallet, and sufficient destination gas is already present.

The recipient expects the route's wrapped token and wants to establish delivery before using it elsewhere. The source explorer shows a successful Send, while the destination wallet has no corresponding token balance. The recipient can proceed to Receive after confirming that it has not yet been submitted; destination delivery remains outstanding.

The recipient uses the successful Send transaction ID in the receiving interface, connects the destination wallet, and confirms Receive. The destination transaction succeeds and the recorded recipient holds the expected wrapped token. That receipt completes the bridge movement.

Graphic: Allbridge Classic - A Manual Wrapped-Token Receipt

View image file

Receipt establishes possession of that wrapped representation, without establishing its acceptance by every application. If the receiving route becomes unavailable, the earlier Send record does not itself deliver the wrapped token.


How Can an Unfinished Classic Transfer Be Completed?

An unfinished Classic transfer required the successful Send transaction ID and the remaining receiving action while its receiving route remained available. Classic's interface exposed unfinished transfers with a Finish option. The separate Receive interface also accepted a Send transaction ID, allowing the destination action to resume without initiating another source transfer.

The manual receiving interface required the destination wallet connection and confirmation of Receive. It displayed a waiting state and then a success screen after completion. If Receive had already been submitted, inspect that transaction's blockchain status before treating the transfer as still awaiting submission. A stale browser display and an unsuccessful blockchain transaction describe different situations.


Blockchain Confirmation and Transfer Timing

Classic's completion time depended on confirmation of the transactions on the participating blockchains. The source and destination confirmations concerned separate actions, so elapsed time after Send did not establish the status of Receive. A destination transaction that had not been submitted had no destination confirmation to await.

A countdown or waiting screen described the interface's progress indication. The transaction record established the blockchain outcome. Fixed times quoted for another route, an earlier demonstration, or another Allbridge product did not determine this transfer's completion time.

Blockchain Confirmation and Transfer Timing (Allbridge Classic)
Illustration: Blockchain Confirmation and Transfer Timing

View image file

Scheduled Closure and Remaining Route Support

Allbridge Classic is deprecated, with shutdown scheduled for November 2026. That scheduled month does not establish an exact final day or guarantee that every legacy route will remain available throughout the month. Before initiating a remaining transfer, establish that its sending and receiving paths are available, including any delegation option on which completion would rely.

Allbridge Core's native stablecoin transfers use a different product model. Compatibility with a Core route requires its supported asset representation and endpoints; possession of a Classic-wrapped token alone does not establish that fit. For an unfinished Classic transfer, a supported receiving path for the existing Send record remains the immediate requirement. The scheduled closure supplies no assurance of receiving availability afterward.

Everyday questions about Allbridge Classic

Can I Finish the Classic Receive Step in Another Browser?

Classic supported completing Receive in another browser when the destination wallet was installed there. The receiving interface needed the successful Send transaction ID, and the route still had to be available.

Where Can I Find the Classic Send Transaction ID After Closing the Bridge Tab?

The successful Send transaction ID can be retrieved from the sending wallet's transaction history or its source-chain block explorer. Classic's receiving interface used that identifier to locate the unfinished transfer. Select the actual Send record, since a wallet address, token contract address, or spending-approval identifier names a different object.

What Does an Unknown Token Entry Mean After Receiving Classic Assets?

An unknown token entry may be the received Classic asset if its contract matches the expected destination token. Check that contract and the recipient account; the display label alone cannot identify the asset.

Does a Node Error Confirm That a Classic Transfer Failed?

A node error can indicate a problem with the wallet's blockchain connection. It does not establish whether a submitted Classic transaction succeeded or failed; inspect that transaction's blockchain record.

Which Transaction ID Matters After Confirming Classic Send Twice?

Use the successful Classic Send transaction ID when duplicate confirmations produced a successful send followed by a failed attempt. The later failed record does not establish that the earlier transfer failed.

Do I Need ABR or xABR to Complete a Regular Classic Transfer?

A regular Classic transfer paid its bridge fee in the transferred token, so ABR or xABR was not a general transfer prerequisite. Classic's staking system used xABR as a pool-share token; its fee reduction required xABR in the sending wallet on an eligible source chain. That separate arrangement did not replace the gas needed for manual sending and receiving.

Is Classic's Scheduled Shutdown the Same Event as Core's Pool Closure?

Classic's scheduled November 2026 shutdown was separate from the discontinuation of Core's liquidity pools in July 2026. The pool closure concerned Core's earlier liquidity model. It did not establish the deadline for completing a Classic Receive transaction.

- last updated