Allbridge Classic

Rejected venues wait the longest for re-review; a rejection has to earn another look before the scheduled date.

Allbridge Classic is a deprecated cross-chain bridge that official documentation says “will be stopped in mid-2026” in favor of Allbridge Core. As of 2026-08-15, however, the live coverage endpoint still reported about $1.12M, concentrated on Ethereum with smaller nonzero Solana, Terra, Binance and Near balances, while retaining thirteen chain records, and official pages still publish Classic contracts and transfer guides. No primary record establishes the exact stop transaction, final withdrawal deadline or disposition of residual assets. Size cannot resolve whether a discontinued bridge claim is executable. The active rejected v1 memo therefore remains an individual lifecycle disposition until the deprecation, residual balances and chain-by-chain unwind are reconciled.

Kill criteria: the events that revoke this verdict
• Allbridge publishes an exact Classic stop timestamp or transaction, final route list and residual-asset withdrawal, migration or claims process, and every nonzero counted chain balance is reconciled to an executable or legally documented exit
• Classic resumes supported operation with TVL sustained above $100M for 30 days and passes a fresh bridge, chain, contract, signer, incident and stressed-exit review

The research file

Mechanism and deprecated identity

Allbridge Classic moves native or wrapped assets between EVM and non-EVM chains through separate send and receive transactions. Official Classic documentation now labels the product deprecated and directs users to Allbridge Core, while continuing to publish the legacy architecture, network contracts, fees and bridging guides. Classic and Core are therefore separate lifecycle identities.

Current observation and lifecycle conflict

The DefiLlama protocol API read on 2026-08-16 continued to classify Allbridge Classic as a Bridge and reported approximately $1.12M, including about $1.06M Ethereum, $0.044M Solana, $0.009M Terra, $0.006M Binance and a small Near balance; eight other retained chain records were zero. Its current adapter still queries the published Classic contracts rather than a closed historical snapshot. Official docs continue to say Classic “will be stopped in mid-2026” after that period began, but provide no exact stop timestamp or transaction, final route list, withdrawal deadline, migration transaction, claims process or signed reconciliation of residual assets.

Control, loss and exit applicability

A transfer requires source and destination transactions and depends on Classic contracts, validators or signers, token liquidity and both settlement chains. Deprecation adds migration, paused-route and residual-asset risk: published contract addresses prove historical or residual deployment, not current route availability. Holders need chain-by-chain evidence that bridging, withdrawal or claim functions remain executable; aggregate TVL cannot substitute for that exit test.

Authority and incident evidence boundary

The reviewed documentation describes the transfer sequence and publishes legacy contracts, but it does not provide a current Classic signer or validator roster, threshold and rotation history, pause and upgrade administrators, chain-by-chain route status, or a closure-specific incident and loss reconciliation. Those omissions matter independently of code availability: a contract can retain assets while its destination liquidity, signer service or receive transaction is unavailable. A final disposition needs signed protocol evidence or onchain events connecting each administrator and nonzero balance to a callable withdrawal, migration or claim, plus confirmation that no unresolved exploit, loss or operational incident remains in the residual perimeter.

Decision, incidents and Core comparison

Coverage still treats the slug as live, so deleting or archiving it would create an omission and falsely imply residual claims disappeared. Nor can a below-materiality rule decide whether a deprecated bridge receipt or wrapped asset has a callable exit. The individual lifecycle memo stays rejected until the exact stop and residual-asset process are published and every nonzero balance is reconciled to an executable withdrawal, migration or legally documented claim. Any renewed operation requires a fresh Classic-specific signer, contract and incident review and comparison with Allbridge Core; Core’s current status does not prove Classic claims migrated or closed.

Sources

The claims above trace to these. Where a number could not be independently verified, the thesis says so.

• Allbridge Classic — deprecation notice and product identity · primary · accessed 2026-08-15
  Supports: deprecated status, planned mid-2026 stop, Classic identity, Core successor, bridge mechanism
• Allbridge Classic — bridge contracts · primary · accessed 2026-08-15
  Supports: deprecated status, planned stop, legacy contract addresses, chain deployments
• Allbridge Classic — transfer mechanism · primary · accessed 2026-08-15
  Supports: send transaction, receive transaction, native and wrapped tokens, cross-chain dependency
• Allbridge Classic — bridge fees and route availability · primary · accessed 2026-08-15
  Supports: chain fees, route availability, source transaction, destination gas, deprecated notice
• DefiLlama adapter — Allbridge Classic live contract accounting · secondary · accessed 2026-08-16
  Supports: current contract addresses, chain accounting, staking balances, residual asset measurement
• DefiLlama — Allbridge Classic survey record · secondary · accessed 2026-08-15
  Supports: current residual TVL, thirteen chain records, Bridge category, active coverage identity

Inherited controls

The verdict above grades the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The least safe layer sets the position’s grade, and the position table names which one that is.