The cartography file on Fidelity Crypto opened the day the first victim hash arrived in our intake queue. The presented narrative — regulated counterparty, custodial protections, audited reserves — collided fast with the chain-side reality. What follows is a structured review of the entity’s chain footprint, jurisdictional posture, and recovery handles.
Observation log
Cluster identification. Receiving addresses associated with Fidelity Crypto group into a small number of high-velocity clusters. The cartographer flagged at least three distinct deposit-side identities and a smaller set of withdrawal-side endpoints — a configuration consistent with intermediated brokerage rather than direct custody.
Mixer proximity. A measurable share of outbound funds touched mixer or coinjoin services within four hops of the receiving address. The hop-count is not unusually short, which suggests routing infrastructure rather than ad-hoc obfuscation.
Jurisdictional posture. Public claims position Fidelity Crypto as licensed under one jurisdiction; the chain-side fund flow points consistently toward off-ramps registered in two others. The mismatch is not, by itself, evidence of fraud — but it is a chartable inconsistency the cartographer logs in every case file of this profile.
Recovery posture
The Fidelity Crypto map identified actionable handles at the off-ramp stage. Where on-chain inflow at compliance-cooperative exchanges is documented, freeze requests can be filed against specific receiving addresses with a clear evidentiary basis.
Have you been involved with this entity?
Cointiverse maintains the case file index as an active forensic resource. If your loss event intersects with Fidelity Crypto, the cartographer can review your specific transaction hashes against the existing map.
[Open a Case →](/submit-a-case/) · [Run a Wallet Check](/wallet-checker/)
Disclaimer: Listing in the Cointiverse case file index reflects forensic review of on-chain behavior and victim reports. It is not an assertion of criminal liability.