Check network and token identity from an existing transfer record
Documentation-based guide · Updated
Build a matching record of chain, address and asset contract. Recognize what an address format or ticker cannot prove, and stop when identity is missing.
Before you start
- Collect the original sending record and the receiving service’s current network and asset details, if applicable.
- This guide checks existing records. It does not initiate a transfer, bridge, recovery or wallet connection.
1. Identify the actual network
Start with the sender’s recorded network and an explorer transaction on that chain. Ethereum, BSC and Base can all use 0x addresses, so visual address similarity cannot establish network compatibility.
Where a chain ID is available, keep it with the record: Ethereum mainnet is 1, BSC mainnet is 56 and Base mainnet is 8453. The onsite network selector chooses among configured networks; it does not autodetect a network from a hash or address.
Check: Write down the full network name and its chain ID when verified. Do not infer them from a ticker.
2. Identify the asset on that network
Distinguish the native asset from a contract token. A token’s useful identifier is the network plus full contract address. Its symbol is optional metadata and can be reused by unrelated contracts.
Use the issuer’s official network-specific record for comparison. Wrapped or bridged forms may have different contracts and conditions. A familiar logo, matching symbol or explorer label alone does not establish issuer support.
Check: Match the full contract and chain, or explicitly identify the native asset. Record any missing official reference.
3. Match the actual recipient
For contract calls, compare the asset-transfer recipient rather than assuming the top-level transaction To is the beneficiary. Keep the full address in your evidence, even when a results card abbreviates it.
For a hosted account, compare the receiving service’s current address and supported network/asset combination. This comparison checks identity; it does not prove that the service credited its internal ledger or that recovery is available.
Check: Record chain, asset and actual recipient as matched, mismatched or unknown separately.
4. Stop at a mismatch or missing evidence
If the record is on one network and the receiving service supports another, document the mismatch. A successful source-chain transaction does not become a destination-chain receipt merely because both chains use the same address format.
If a cross-chain protocol was used, retain its original message identifier and check its documented destination stage. Do not invent a recovery route or promise that another transfer will fix a mismatch.
Check: Produce a factual record that another person can reproduce, with unknown fields preserved.
Worked example: matching address, mismatched network
- Illustrative case: the existing transaction record identifies BSC mainnet, chain ID 56.
- The receiving service’s saved instructions identify Ethereum mainnet, chain ID 1. The displayed recipient string is identical in both records.
Conclusion: The network condition does not match. The shared address format does not prove supported delivery, private-key control or recoverability. Preserve the original evidence and obtain the receiving service’s actual position.
Decision & failure branches
| Observation | What it means | Next check |
|---|---|---|
| Only the symbol matches | Asset identity is incomplete. | Compare chain and full token contract against an official reference. |
| Address matches, network differs | The intended receiving-network condition is not met. | Preserve the mismatch and check the receiving service’s published handling of this existing case. |
| Chain, contract and recipient match | Identity is consistent; execution and credit remain separate checks. | Inspect the transaction receipt and actual asset movement, then receiving-service credit. |
| Cross-chain source succeeded | Only the source stage is established. | Locate the original protocol’s destination or message record; otherwise mark destination unresolved. |
Completion checklist
- Save network, chain ID if verified, full asset identity, recipient, original hash and time.
- Separate a format match from verified identity, successful movement and platform credit.