Recovery Doctrine: chain-of-custody · verifiable on-chain trail · regulator-ready packets verification chain: Etherscan · SlowMist · CertiK
45 claims under active investigation 92 wallet routes mapped this month Open a Free Recovery Consultation →

Tag: real recovery help

  • Professor’s Brief: EXCO

    // FROM THE CASEFILE — EXCO

    The Professor opens the file on EXCO the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    On-chain reading — wallet flow for EXCO:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for EXCO.
    • Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
    • Bridge events into chains where the operator can off-ramp at scale.
    • Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
    • Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

    The annotation continues — off-ramp endpoint:

    • Endpoint counterparty in the EXCO casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • EXCO’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the EXCO packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the EXCO off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    How a EXCO casefile becomes a regulator-ready filing:

    1. Casefile triage on EXCO — the submission is read; a written assessment is delivered.
    2. Forensic trace on EXCO — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the EXCO endpoint is named.
    4. Recovery filing on EXCO — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of EXCO — the Professor follows the casefile until next-step documentation exists.

    What the casefile records — chains and counterparties:

    • Chains in scope for EXCO — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for EXCO — named centralised exchanges with compliance leverage.
    • Filings supported on EXCO — IC3, state AG, off-ramp desk, civil discovery as applicable.

    What is never asked of a claimant:

    • Boundary on EXCO — seed phrases are off-limits.
    • Boundary on EXCO — remote logins are off-limits.
    • Boundary on EXCO — upfront cash retainers are off-limits.
    • Boundary on EXCO — guaranteed-recovery promises are off-limits.
    • Boundary on EXCO — unsolicited outbound contact is off-limits.

    Open a free consultation

    Submit your wallet for a forensic reading — /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Mega Trader FX — The Professor’s Note

    // FROM THE CASEFILE — MEGA TRADER FX

    Mega Trader FX, operating from megatraderforex.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Reading the wallets — Mega Trader FX casefile:

    • Deposit transaction hashes from the claimant wallet to the Mega Trader FX platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    The annotation continues — off-ramp endpoint:

    • Off-ramp endpoint for Mega Trader FX resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Mega Trader FX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Mega Trader FX is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Mega Trader FX off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

    Filing pathway — the next step after the off-ramp is identified:

    1. Read the Mega Trader FX submission — written go/no-go returned.
    2. Map the Mega Trader FX wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the Mega Trader FX off-ramp — endpoint counterparty identified.
    4. Build and file the Mega Trader FX recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the Mega Trader FX file — until written next steps exist.

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Mega Trader FX casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Mega Trader FX packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Mega Trader FX — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    What is never asked of a claimant:

    • What the Professor will not do on Mega Trader FX — ask for a seed phrase.
    • What the Professor will not do on Mega Trader FX — request remote-access logins.
    • What the Professor will not do on Mega Trader FX — demand cash up front.
    • What the Professor will not do on Mega Trader FX — promise a guarantee.
    • What the Professor will not do on Mega Trader FX — call you out of the blue.

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Grimbix — Annotated by the Professor

    // FROM THE CASEFILE — GRIMBIX

    When a deposit ledgered to Grimbix at grimbix.io stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Trace summary — funds that left grimbix.io:

    • Deposit transaction hashes from the claimant wallet to the Grimbix platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    Off-ramp summary — Grimbix casefile:

    • Off-ramp endpoint for Grimbix resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Grimbix’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Grimbix is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Grimbix off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

    Pathway to recovery — what happens after the trail is mapped:

    1. Casefile triage on Grimbix — the submission is read; a written assessment is delivered.
    2. Forensic trace on Grimbix — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Grimbix endpoint is named.
    4. Recovery filing on Grimbix — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Grimbix — the Professor follows the casefile until next-step documentation exists.

    What we read in a Grimbix casefile:

    • Deposit-side chains in Grimbix casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Grimbix packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Grimbix — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Boundaries on every Grimbix casefile — never crossed:

    • Recovery scammers do these things on Grimbix; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Grimbix; the Professor never does — request remote logins.
    • Recovery scammers do these things on Grimbix; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Grimbix; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Grimbix; the Professor never does — call you unsolicited.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: FAN HUA GROUP

    // FROM THE CASEFILE — FAN HUA GROUP

    When a deposit ledgered to FAN HUA GROUP at fanhuagroup.vip stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Trace summary — funds that left fanhuagroup.vip:

    • Claimant-to-platform deposit transactions on the deposit chain used by FAN HUA GROUP.
    • Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
    • Cross-chain bridge events to chains with deeper exchange liquidity.
    • Privacy-service interactions, where present in the trail.
    • Off-ramp wallet — the named centralised-exchange endpoint.

    Off-ramp map — where the funds left the chain:

    • On the FAN HUA GROUP casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for FAN HUA GROUP is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the FAN HUA GROUP casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, FAN HUA GROUP escalates to IC3, state AG, and civil-discovery overlay.

    Recovery pathway — how this casefile moves toward filing:

    1. Casefile review on FAN HUA GROUP — reading the submission against the no-go list.
    2. Trace mapping on FAN HUA GROUP — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on FAN HUA GROUP — exchange endpoint identified.
    4. Packet filing on FAN HUA GROUP — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on FAN HUA GROUP.

    What the casefile records — chains and counterparties:

    • Chains the Professor reads for FAN HUA GROUP casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in FAN HUA GROUP — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on FAN HUA GROUP — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

    Lines we never cross — by published policy:

    • Recovery scammers do these things on FAN HUA GROUP; the Professor never does — request seed phrases.
    • Recovery scammers do these things on FAN HUA GROUP; the Professor never does — request remote logins.
    • Recovery scammers do these things on FAN HUA GROUP; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on FAN HUA GROUP; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on FAN HUA GROUP; the Professor never does — call you unsolicited.

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Tandexo — The Professor’s Note

    // FROM THE CASEFILE — TANDEXO

    Funds you sent to Tandexo (tandexo.com) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    On-chain reading — wallet flow for Tandexo:

    • Deposit confirmations from the claimant to Tandexo’s receiving wallet at tandexo.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    The Professor’s off-ramp note:

    • Tandexo off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Tandexo off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for Tandexo — the packet meets the off-ramp’s published compliance standard.
    • When the Tandexo off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    Pathway to recovery — what happens after the trail is mapped:

    1. Casefile triage on Tandexo — the submission is read; a written assessment is delivered.
    2. Forensic trace on Tandexo — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Tandexo endpoint is named.
    4. Recovery filing on Tandexo — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Tandexo — the Professor follows the casefile until next-step documentation exists.

    What the casefile records — chains and counterparties:

    • Deposit + forwarding chains for Tandexo — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
    • Off-ramps the Tandexo casefile may resolve to — centralised exchanges that respond to compliance filings.
    • Filing pathways on Tandexo — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

    Lines the Professor will not cross:

    • Tandexo policy — seed phrases are never requested.
    • Tandexo policy — remote-access logins are never requested.
    • Tandexo policy — no upfront cash retainer to scope.
    • Tandexo policy — no guaranteed-recovery language. None.
    • Tandexo policy — no unsolicited calls. The Professor responds in writing only.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: LC Markt

    // FROM THE CASEFILE — LC MARKT

    Funds you sent to LC Markt (lc-markt.co) are still recorded on the public ledger; the question is no longer whether the money moved but where the off-ramp opened — and that is what the Professor reads.

    On-chain reading — wallet flow for LC Markt:

    • Deposit confirmations from the claimant to LC Markt’s receiving wallet at lc-markt.co.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    From the lectern — off-ramp identification:

    • LC Markt off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The LC Markt off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
    • Compliance leverage is applied at the named counterparty for LC Markt — the packet meets the off-ramp’s published compliance standard.
    • When the LC Markt off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    Recovery sequence — from on-chain reading to filed packet:

    1. Triage on LC Markt — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on LC Markt — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on LC Markt — off-ramp endpoint matched to a named exchange counterparty.
    4. File the LC Markt packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on LC Markt — the Professor stays on the casefile until a documented next step exists.

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in LC Markt casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in LC Markt packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on LC Markt — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines we never cross — by published policy:

    • On the LC Markt casefile — never request a seed phrase. Ever.
    • On the LC Markt casefile — never request remote-access logins to a wallet or exchange.
    • On the LC Markt casefile — never demand an upfront cash retainer to scope the matter.
    • On the LC Markt casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the LC Markt casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

    The Professor reads claims at no charge to begin — open a consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Endow Bull Trading — Annotated by the Professor

    // FROM THE CASEFILE — ENDOW BULL TRADING

    The Professor opens the file on Endow Bull Trading the same way every casefile is opened — by treating the wallet history as text and the off-ramp endpoint as the citation a regulator can verify.

    From the marginalia — the deposit pathway:

    • Deposit transaction hashes from the claimant wallet to the Endow Bull Trading platform receiving address.
    • Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
    • Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
    • Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
    • Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

    The annotation continues — off-ramp endpoint:

    • Endpoint counterparty in the Endow Bull Trading casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Endow Bull Trading’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
    • Leverage is applied to that named counterparty — the Endow Bull Trading packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Endow Bull Trading off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

    The Professor’s recovery note for Endow Bull Trading:

    1. Casefile review on Endow Bull Trading — reading the submission against the no-go list.
    2. Trace mapping on Endow Bull Trading — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Endow Bull Trading — exchange endpoint identified.
    4. Packet filing on Endow Bull Trading — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Endow Bull Trading.

    What the Professor tracks across Endow Bull Trading casefiles:

    • Deposit-side chains in Endow Bull Trading casefiles — typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT) — with bridge crossings noted.
    • Off-ramps named in Endow Bull Trading packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Endow Bull Trading — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Recovery scammers do these things; the Professor never does:

    • Boundary on Endow Bull Trading — seed phrases are off-limits.
    • Boundary on Endow Bull Trading — remote logins are off-limits.
    • Boundary on Endow Bull Trading — upfront cash retainers are off-limits.
    • Boundary on Endow Bull Trading — guaranteed-recovery promises are off-limits.
    • Boundary on Endow Bull Trading — unsolicited outbound contact is off-limits.

    Open a free consultation

    Open a free first consultation — /contact-us/ — written response within one business day.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: KLMFX

    // FROM THE CASEFILE — KLMFX

    When a deposit ledgered to KLMFX at klmfx.org stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Wallet trace — what the Professor maps:

    • Deposit-side hashes from claimant wallets into KLMFX’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    Off-ramp reading — exchange counterparty for KLMFX:

    • On the KLMFX casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for KLMFX is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the KLMFX casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, KLMFX escalates to IC3, state AG, and civil-discovery overlay.

    The Professor’s recovery note for KLMFX:

    1. Triage on KLMFX — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on KLMFX — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on KLMFX — off-ramp endpoint matched to a named exchange counterparty.
    4. File the KLMFX packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on KLMFX — the Professor stays on the casefile until a documented next step exists.

    Reading-list — chains and exchanges in scope:

    • Chains in scope for KLMFX — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for KLMFX — named centralised exchanges with compliance leverage.
    • Filings supported on KLMFX — IC3, state AG, off-ramp desk, civil discovery as applicable.

    Lines the Professor will not cross:

    • KLMFX policy — seed phrases are never requested.
    • KLMFX policy — remote-access logins are never requested.
    • KLMFX policy — no upfront cash retainer to scope.
    • KLMFX policy — no guaranteed-recovery language. None.
    • KLMFX policy — no unsolicited calls. The Professor responds in writing only.

    Open a free consultation

    Send the wallet for trace — /submit-a-case/ — the Professor responds in writing.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile InvestMarkets — The Professor’s Note

    // FROM THE CASEFILE — INVESTMARKETS

    When a deposit ledgered to InvestMarkets at investmarkets.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    Trace summary — funds that left investmarkets.com:

    • Deposit confirmations from the claimant to InvestMarkets’s receiving wallet at investmarkets.com.
    • Forwarding-wallet pathway documented hop-by-hop with chain-of-custody hashes.
    • Cross-chain bridge transactions where the operator routed value out of the deposit chain.
    • Mixer or coin-join interactions, where applicable.
    • Final off-ramp at a centralised exchange — the compliance counterparty named in the recovery filing.

    The Professor’s off-ramp note:

    • On the InvestMarkets casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for InvestMarkets is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the InvestMarkets casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, InvestMarkets escalates to IC3, state AG, and civil-discovery overlay.

    Filing pathway — the next step after the off-ramp is identified:

    1. Read the InvestMarkets submission — written go/no-go returned.
    2. Map the InvestMarkets wallet trail — every hop captured with chain-of-custody hashes.
    3. Name the InvestMarkets off-ramp — endpoint counterparty identified.
    4. Build and file the InvestMarkets recovery packet — to IC3, state AG, off-ramp compliance, civil-discovery overlay.
    5. Stay on the InvestMarkets file — until written next steps exist.

    What the Professor tracks across InvestMarkets casefiles:

    • Chains the InvestMarkets casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
    • Off-ramps relevant to InvestMarkets — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the InvestMarkets packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    Lines we never cross — by published policy:

    • On the InvestMarkets casefile — never request a seed phrase. Ever.
    • On the InvestMarkets casefile — never request remote-access logins to a wallet or exchange.
    • On the InvestMarkets casefile — never demand an upfront cash retainer to scope the matter.
    • On the InvestMarkets casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the InvestMarkets casefile — never call the claimant unsolicited. Written-only.

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Gravity Trade — The Professor’s Note

    // FROM THE CASEFILE — GRAVITY TRADE

    When a deposit ledgered to Gravity Trade at gravity-trade.com stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    The annotation reads — wallet trace:

    • Deposit-side hashes from claimant wallets into Gravity Trade’s receiving addresses.
    • Operator forwarding wallets — deposit consolidation documented to chain-of-custody standards.
    • Inter-chain bridge transactions when value moves toward off-ramp liquidity.
    • Mixer/obfuscation events the operator routed through, where present.
    • Final off-ramp endpoint and named counterparty exchange.

    The annotation continues — off-ramp endpoint:

    • On the Gravity Trade casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
    • The off-ramp wallet for Gravity Trade is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Gravity Trade casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Gravity Trade escalates to IC3, state AG, and civil-discovery overlay.

    Filing pathway — the next step after the off-ramp is identified:

    1. Triage on Gravity Trade — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Gravity Trade — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Gravity Trade — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Gravity Trade packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
    5. Follow-through on Gravity Trade — the Professor stays on the casefile until a documented next step exists.

    What the casefile records — chains and counterparties:

    • Chains in scope for Gravity Trade — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
    • Off-ramps in scope for Gravity Trade — named centralised exchanges with compliance leverage.
    • Filings supported on Gravity Trade — IC3, state AG, off-ramp desk, civil discovery as applicable.

    Boundaries on every Gravity Trade casefile — never crossed:

    • Boundary on Gravity Trade — seed phrases are off-limits.
    • Boundary on Gravity Trade — remote logins are off-limits.
    • Boundary on Gravity Trade — upfront cash retainers are off-limits.
    • Boundary on Gravity Trade — guaranteed-recovery promises are off-limits.
    • Boundary on Gravity Trade — unsolicited outbound contact is off-limits.

    Open a free consultation

    Book a reading of your wallet — file at /submit-a-case/.

    Open a Free Case Consultation   Submit Wallet for Trace