A clear record gives a bridge team the facts to trace a stuck transfer. Save the details as soon as you notice a delay or missing funds, while the transaction is easy to find.
Record both sides of the transfer before asking for help
Start with the chain you sent from and the chain you expected to receive on. Add the asset, amount, approximate time, sending address, and destination address. These details distinguish your transfer from other activity in the same wallet.
If you used Manta bridge, record the source transaction identifier and the destination details you entered. Save the destination transaction identifier too if one appears. Cross-chain transfers can involve separate actions on each chain, so one identifier may show only the first part.
Think of the identifiers as parcel tracking numbers: each belongs to a particular leg of the trip. On Ethereum, the transaction hash identifies a transaction; its receipt reports whether execution succeeded or failed. The Ethereum.org transaction and JSON-RPC documentation describe these fields. A successful source transaction alone does not prove the destination funds arrived.
Keep the original transaction identifier exactly as shown. BTC transactions use a transaction ID, often called a txid; the Bitcoin Developer Reference explains that an output number can also identify which part of a transaction matters. Don’t shorten or retype a long identifier when you can copy it.
Use records that let someone check the transaction
A useful recovery packet is a small, readable note with evidence attached. Include the wallet address, source and destination chains, asset and amount, time with your time zone, source identifier, destination address, and any destination identifier. Add the exact error text if you saw one.
Save a transaction explorer record or wallet history entry showing the status and details. A screenshot can help explain what you saw, but it should supplement the copied identifier. If the transfer is still pending, say so; an Ethereum receipt may not exist until the transaction is included.
For example, if your wallet shows a successful source transaction but no destination credit, state those two facts separately. Include the source identifier and the receiving address you intended. If you later find a destination transaction, record its identifier too. This helps distinguish a delayed destination step from a transfer sent to an unintended address.
Keep the record focused on public transaction details. Never include a recovery phrase, private key, or wallet password; those secrets can give someone control of your funds. Check every address against your own transaction record before sending the request.
Choose the next step from what the record shows
Use the source status to decide what evidence is missing. If it failed, include the failure status and do not describe it as a completed transfer. If it succeeded but funds have not arrived, provide the source record and ask what can be traced on the destination side.
If you are comparing ways to make a new cross-chain transfer, mantabridge.org lets you bridge and swap assets across chains in one flow. That can suit someone who wants to move funds and change assets as part of the same transfer.
When you contact the service involved, send the concise record and answer follow-up questions with the matching identifier. Manta bridge is relevant when your transfer used that service; the same source-and-destination record helps explain exactly where the issue appeared.
Choose the next step by matching the evidence: a failed source needs its failure details, while a successful source with no arrival needs both sides traced.