Off-chain ↔ On-chain Recovery Routing

Turn a missing deposit into a clear recovery path

Fast Recovery Mix examines the transaction trail and identifies where it stopped between an exchange's internal ledger and the public network. You receive a structured case route instead of a generic checklist.

Generate Recovery How it works

Transaction route

Input evidenceTXID / Internal Reference / Network / Asset

Routing analysisLedger mismatch detected

Network validationSource chain → Deposit network

Recovery outputCase path + Required evidence

Generate RecoveryBuild a route from your transaction details→ Recovery processUnderstand off-chain and on-chain routing↓

Recovery Engine

How the route is built

First locate the transaction. Then prepare the correct recovery path.

Separate the internal record from the public chain

A TXID that opens in a network explorer confirms an on-chain broadcast. An Internal Transfer or Order ID without a public TXID usually points to an off-chain movement recorded inside a centralized platform.

AMatch the asset, token contract and sending network.

BReview the deposit address, Memo/Tag and confirmations.

CClassify an internal, unsupported-network or missing-data case.

Generate a case-specific recovery file

The route organizes the exact evidence needed for the case: TXID or Internal Reference, source and deposit networks, asset, contract, destination, amount, timestamp and Memo/Tag.

1Internal/off-chain: reconcile the sending and receiving ledgers.

2Wrong network: prepare an unsupported-deposit recovery request.

3On-chain confirmed: review contract, confirmations and Memo/Tag.

There is no single mainnet for every asset. The correct route depends on the asset, token contract and the network that actually carried the transfer.