Investigate a Bridge Arrival Using Public Evidence
A source-chain success message is a starting point for a bridge investigation. Arrival requires evidence on the intended destination chain and a match to the intended recipient and asset.
Build a two-chain timeline
Start with the original source chain, public transaction hash and observation time. Check the source receipt status on the corresponding explorer. Keep the external route’s transfer identifier separately if one exists: it may not be a blockchain transaction hash. Record any reported destination hash with its own chain label. This timeline prevents a source transaction from being searched on the destination explorer or mistaken for final delivery.
Identify the pending stage
Consult the route’s current official documentation to learn whether source confirmation, message processing, proof, claim or finalization remains. For example, Base’s canonical withdrawals distinguish initiation, proving and finalization on Ethereum. Other bridges can use different mechanisms. Do not impose the waiting period of one design on another or assume every delay is a failed transaction. An unavailable provider status page also does not settle the underlying chain state.
Inspect destination identity and balance evidence
When a destination transaction is reported, compare its recipient, output contract and execution result with the original route specification. A successful receipt for an unrelated transaction is insufficient. Inspect the recipient’s relevant native or token balance and any matching transfer records. Wallet display updates may lag behind indexed evidence. Conversely, a token with a similar symbol can appear in the wallet while the expected contract’s balance remains unchanged; verify the exact asset before concluding that the route completed.
Escalate with bounded evidence
If the published route requirements appear unmet, prepare a concise record of public hashes, chains, expected asset and observed stage for the provider’s independently verified reporting channel. Never send recovery data or authorize a new transfer to “unlock” an old one. Avoid repeating the source action while completion is uncertain. RunixCoin does not operate this bridge or provide a recovery guarantee. Its public quote form neither initiates a bridge nor verifies external arrival, so use chain-specific evidence for the investigation.
References and verification
Reviewed . Product limits reflect inspected public interface code. These are educational checklists, not reports of tested mainnet transactions; browser behavior and execution were not verified.