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: investment scam

  • The Lion Market — Annotated by the Professor

    // FROM THE CASEFILE — THE LION MARKET

    When a deposit ledgered to The Lion Market at thelionmarket.live stops responding, the trail does not stop with the silence — the on-chain record is the syllabus, and the Professor reads it carefully.

    On-chain reading — wallet flow for The Lion Market:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for The Lion Market.
    • 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.

    Off-ramp reading — exchange counterparty for The Lion Market:

    • Endpoint counterparty in the The Lion Market casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • The Lion Market’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 The Lion Market packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the The Lion Market 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.

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

    1. First read on The Lion Market — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on The Lion Market — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for The Lion Market is named to a centralised exchange wallet.
    4. Packet filing on The Lion Market — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with The Lion Market until a documented outcome or escalation step is on file.

    What the casefile records — chains and counterparties:

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

    Boundaries on every The Lion Market casefile — never crossed:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Office Hours on Alfadigitancy

    // FROM THE CASEFILE — ALFADIGITANCY

    When deposits to Alfadigitancy via alfadigitancy.com go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    From the marginalia — the deposit pathway:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Alfadigitancy.
    • 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:

    • Alfadigitancy’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Alfadigitancy off-ramp wallet against historical laundering throughput.
    • The Alfadigitancy packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Alfadigitancy, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

    1. Submission triage — Alfadigitancy casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — Alfadigitancy deposit and forwarding wallets captured.
    3. Endpoint identification — Alfadigitancy off-ramp wallet named.
    4. Filing — Alfadigitancy packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — Alfadigitancy stays on file until a documented next step is reached.

    What the casefile records — chains and counterparties:

    • Chains tracked on Alfadigitancy — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on Alfadigitancy — named exchange counterparties with public compliance contacts.
    • Filings supported on Alfadigitancy — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

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

    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

  • Office Hours on XferCapital

    // FROM THE CASEFILE — BTCUSDT INVESTMENT

    When deposits to XferCapital via this platform go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the XferCapital 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 Professor’s off-ramp note:

    • XferCapital’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the XferCapital off-ramp wallet against historical laundering throughput.
    • The XferCapital packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for XferCapital, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

    How a XferCapital casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

    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

    Why this platform is on our casefile

    XferCapital has been flagged as a Fraudulent online trading platforms by FSMA Belgium. FSMA warning 19/03/2025. Jurisdiction: BE. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.fsma.be/en/warnings/companies-operating-unlawfully-in-belgium

  • Casefile Pelican Capital Investment — The Professor’s Note

    // FROM THE CASEFILE — PELICAN CAPITAL INVESTMENT

    Pelican Capital Investment is a casefile under reading. The deposits to pelicancapitalinvestment.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    Reading the wallets — Pelican Capital Investment casefile:

    • Deposit-side hashes from claimant wallets into Pelican Capital Investment’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 Professor’s off-ramp note:

    • Pelican Capital Investment’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
    • Chain-analytics datasets cross-reference the Pelican Capital Investment off-ramp wallet against historical laundering throughput.
    • The Pelican Capital Investment packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for Pelican Capital Investment, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

    1. First read on Pelican Capital Investment — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Pelican Capital Investment — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Pelican Capital Investment is named to a centralised exchange wallet.
    4. Packet filing on Pelican Capital Investment — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Pelican Capital Investment until a documented outcome or escalation step is on file.

    Reading-list — chains and exchanges in scope:

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

    Recovery scammers do these things; the Professor never does:

    • Boundary on Pelican Capital Investment — seed phrases are off-limits.
    • Boundary on Pelican Capital Investment — remote logins are off-limits.
    • Boundary on Pelican Capital Investment — upfront cash retainers are off-limits.
    • Boundary on Pelican Capital Investment — guaranteed-recovery promises are off-limits.
    • Boundary on Pelican Capital Investment — 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

  • Office Hours on Flint Markets

    // FROM THE CASEFILE — FLINT MARKETS

    Flint Markets is a casefile under reading. The deposits to flintmarkets.com sit on-chain, immutable; the wallet pathway is the primary source, and the off-ramp endpoint is the conclusion the Professor’s marginalia points toward.

    On-chain reading — wallet flow for Flint Markets:

    • Claimant deposit hashes — provided in the case submission and verified against the public ledger for Flint Markets.
    • 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.

    Off-ramp reading — exchange counterparty for Flint Markets:

    • Endpoint counterparty in the Flint Markets casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Flint Markets’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 Flint Markets packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Flint Markets 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 Flint Markets:

    1. Triage on Flint Markets — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
    2. Trace on Flint Markets — deposit pathway mapped across chains, captured with chain-of-custody hashes.
    3. Identify on Flint Markets — off-ramp endpoint matched to a named exchange counterparty.
    4. File the Flint Markets 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 Flint Markets — the Professor stays on the casefile until a documented next step exists.

    What the Professor tracks across Flint Markets casefiles:

    • Chains tracked on Flint Markets — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on Flint Markets — named exchange counterparties with public compliance contacts.
    • Filings supported on Flint Markets — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Boundaries on every Flint Markets casefile — never crossed:

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

    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

  • Reading the Chain: CashSpiner

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to CashSpiner via https: go quiet, the on-chain record stays loud. The Professor’s reading begins where the platform’s silence does — with the wallet that received the funds and the path it took afterward.

    On-chain reading — wallet flow for CashSpiner:

    • Claimant-to-platform deposit transactions on the deposit chain used by CashSpiner.
    • 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 reading — exchange counterparty for CashSpiner:

    • CashSpiner casefiles end at a centralised exchange — Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
    • Off-ramp wallet for CashSpiner is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for CashSpiner — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the CashSpiner casefile.

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on CashSpiner — Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
    • Off-ramps tracked on CashSpiner — named exchange counterparties with public compliance contacts.
    • Filings supported on CashSpiner — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    Recovery scammers do these things; the Professor never does:

    • On the CashSpiner casefile — never request a seed phrase. Ever.
    • On the CashSpiner casefile — never request remote-access logins to a wallet or exchange.
    • On the CashSpiner casefile — never demand an upfront cash retainer to scope the matter.
    • On the CashSpiner casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the CashSpiner 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

    Why this platform is on our casefile

    CashSpiner has been flagged as a fake broker/platform by IOSCO I-SCAN (British Columbia – British Columbia Securities Commission). reported 2026-06-25. Jurisdiction: British Columbia. It appears on an official regulator or fraud-warning list, which is a strong indicator of a scam operation. Treat any contact from this entity with caution. Reference: https://www.iosco.org/i-scan/

  • Casefile Altex Group — The Professor’s Note

    // FROM THE CASEFILE — ALTEX GROUP

    Funds you sent to Altex Group (altex-group.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.

    Reading the wallets — Altex Group casefile:

    • Deposit transaction hashes from the claimant wallet to the Altex Group 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 map — where the funds left the chain:

    • Endpoint counterparty in the Altex Group casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • Altex Group’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 Altex Group packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the Altex Group 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.

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

    1. First read on Altex Group — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on Altex Group — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for Altex Group is named to a centralised exchange wallet.
    4. Packet filing on Altex Group — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with Altex Group until a documented outcome or escalation step is on file.

    What the Professor tracks across Altex Group casefiles:

    • Chains the Professor reads for Altex 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 Altex Group — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on Altex Group — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

    What is never asked of a claimant:

    • Hard line on Altex Group — no seed-phrase requests, period.
    • Hard line on Altex Group — no remote logins requested.
    • Hard line on Altex Group — no upfront cash retainer.
    • Hard line on Altex Group — no guarantee language.
    • Hard line on Altex Group — no unsolicited phone outreach.

    Open a free consultation

    Bring the casefile to office hours — open a free consultation at /contact-us/.

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile GKMTECH — The Professor’s Note

    // FROM THE CASEFILE — GKMTECH

    GKMTECH, operating from g-global.me, 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 — GKMTECH casefile:

    • Deposit confirmations from the claimant to GKMTECH’s receiving wallet at g-global.me.
    • 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.

    Off-ramp reading — exchange counterparty for GKMTECH:

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

    The Professor’s recovery note for GKMTECH:

    1. First read on GKMTECH — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
    2. Wallet trace on GKMTECH — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
    3. Counterparty identification — the off-ramp endpoint for GKMTECH is named to a centralised exchange wallet.
    4. Packet filing on GKMTECH — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
    5. Casefile follow-through — the Professor stays with GKMTECH until a documented outcome or escalation step is on file.

    What we read in a GKMTECH casefile:

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

    Lines the Professor will not cross:

    • Boundary on GKMTECH — seed phrases are off-limits.
    • Boundary on GKMTECH — remote logins are off-limits.
    • Boundary on GKMTECH — upfront cash retainers are off-limits.
    • Boundary on GKMTECH — guaranteed-recovery promises are off-limits.
    • Boundary on GKMTECH — 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

  • Office Hours on GEX Finance

    // FROM THE CASEFILE — GEX FINANCE

    GEX Finance, operating from gexforex.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 — GEX Finance casefile:

    • Deposit transaction hashes from the claimant wallet to the GEX Finance 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 map — where the funds left the chain:

    • Endpoint counterparty in the GEX Finance casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
    • GEX Finance’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 GEX Finance packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the GEX Finance 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 GEX Finance:

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

    Chains and off-ramps the Professor follows:

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

    Boundaries on every GEX Finance casefile — never crossed:

    • GEX Finance policy — seed phrases are never requested.
    • GEX Finance policy — remote-access logins are never requested.
    • GEX Finance policy — no upfront cash retainer to scope.
    • GEX Finance policy — no guaranteed-recovery language. None.
    • GEX Finance policy — no unsolicited calls. The Professor responds in writing 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

  • Aquilamsv — Annotated by the Professor

    // FROM THE CASEFILE — AQUILAMSV

    When a deposit ledgered to Aquilamsv at aquilamsv.com 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 Aquilamsv’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 Professor’s off-ramp note:

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

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

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

    What the Professor tracks across Aquilamsv casefiles:

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

    Lines the Professor will not cross:

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

    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