Write the identifier’s role next to the identifier
| Reference from an interface | What to establish | What not to infer from its appearance |
|---|---|---|
| Filecoin message CID | Whether it is the actual message for the intended FIL payment | That every CID on a storage screen is a payment |
| Ethereum-style transaction hash in a Filecoin tool | Its Filecoin transaction context and corresponding record | That the payment happened on Ethereum mainnet |
| Stored-file or dataset CID | Which content it identifies in the storage workflow | That the storage identifier proves an exchange deposit |
| Bitcoin payout reference | The separate BTC transfer to the intended recipient | That it is another representation of the FIL input |
Different reference formats can belong to the Filecoin workflow
The official Lotus interface defines methods for obtaining a Filecoin message CID corresponding to an Ethereum transaction hash and the reverse reference. That makes the source of an identifier important. An Ethereum-style field name in a Filecoin wallet is not evidence that you should search the payment on an unrelated Ethereum network.
This does not promise that every arbitrary CID can be mapped to a payment or that every explorer has the same lookup support. Keep the original reference and its wallet-provided link. If a second representation is needed, obtain it from the legitimate wallet, explorer or service that can explain the record rather than inventing a conversion by trimming characters.
Prepare one payment trace before another funding attempt
- Start from the sending wallet’s transaction history
Use the entry intended to pay the issued FIL recipient. Record the network, the displayed transaction or message reference, the recipient, amount and reported result. A recently copied CID elsewhere in a storage application may describe a different event entirely.
- Explain which representation your evidence uses
When asking for a payment review, include the original reference and a public link from the wallet when available. State whether the interface calls it a message CID or a transaction hash. Ask which representation the reviewer needs without editing the value by hand.
- Keep the BTC result in a separate row
Once the FIL input is identified, locate the Bitcoin payout through the exchange and receiving-wallet records. Do not search a FIL message reference as though it were the BTC transaction. The order connects the two legs, while their network references remain distinct.
If a stored file’s CID was supplied instead
- Return to the payment record
- IPFS documentation describes a content CID as identifying content. It is not a receipt for a transfer merely because Filecoin also uses CIDs. Find the actual sending entry before concluding that the exchange can or cannot locate a deposit.
- Do not expose private content to prove payment
- A public transaction trace is the relevant evidence for funding. Private files and wallet recovery material do not establish the missing payment stage and should not be sent as substitutes for it.
- Resolve the existing trace before paying again
- An unsuccessful lookup can reflect a reference-context mismatch. It does not prove that the first payment failed or that a repeat transfer is required. Check the existing sending result and intended recipient before any new attempt.
Questions about FIL payment references
- Does an Ethereum-style hash mean the FIL payment used Ethereum mainnet?
- Not by itself. Establish the network and transaction context from the Filecoin wallet record rather than from the string’s appearance.
- Can a stored-file CID prove that an exchange was paid?
- No. Identify the actual payment message or transaction. A content identifier answers a different question.
- Should I shorten or rewrite a message CID to fit a search field?
- No. Preserve the original reference and obtain a supported corresponding representation from the legitimate tool or service when needed.
Primary identifier references
- Lotus reference mappings for message CIDs and transaction hashes
- IPFS content identifiers and their role
Reviewed: