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

Tag: recovery company

  • Reading the Chain: Gafodex

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Gafodex via gafodex.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.

    On-chain reading — wallet flow for Gafodex:

    • Claimant-to-platform deposit transactions on the deposit chain used by Gafodex.
    • 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 Gafodex:

    • Gafodex 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 Gafodex is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Gafodex — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Gafodex casefile.

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

    • Chains tracked on Gafodex — 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 Gafodex — named exchange counterparties with public compliance contacts.
    • Filings supported on Gafodex — 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 Gafodex casefile — never request a seed phrase. Ever.
    • On the Gafodex casefile — never request remote-access logins to a wallet or exchange.
    • On the Gafodex casefile — never demand an upfront cash retainer to scope the matter.
    • On the Gafodex casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Gafodex 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

    Gafodex has been flagged as a fake broker/platform by IOSCO I-SCAN (New Zealand – Financial Markets Authority). reported 2025-09-15. Jurisdiction: New Zealand. 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/

  • From the Lectern: INVESTEFT

    // FROM THE CASEFILE — INVESTEFT

    When deposits to INVESTEFT via investeft.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.

    Reading the wallets — INVESTEFT casefile:

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

    • INVESTEFT off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The INVESTEFT 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 INVESTEFT — the packet meets the off-ramp’s published compliance standard.
    • When the INVESTEFT 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 review on INVESTEFT — reading the submission against the no-go list.
    2. Trace mapping on INVESTEFT — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on INVESTEFT — exchange endpoint identified.
    4. Packet filing on INVESTEFT — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on INVESTEFT.

    Chains and off-ramps the Professor follows:

    • Chains the INVESTEFT 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 INVESTEFT — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the INVESTEFT 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:

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

    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

  • Casefile Witler Finance Groups — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Witler Finance Groups 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:

    • Claimant-to-platform deposit transactions on the deposit chain used by Witler Finance Groups.
    • 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.

    From the lectern — off-ramp identification:

    • Witler Finance Groups off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Witler Finance Groups 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 Witler Finance Groups — the packet meets the off-ramp’s published compliance standard.
    • When the Witler Finance Groups off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Witler Finance Groups casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Witler Finance Groups 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 Witler Finance Groups packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Witler Finance Groups — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    What is never asked of a claimant:

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

    Why this platform is on our casefile

    Witler Finance Groups has been flagged as a Credit fraud by FSMA Belgium. FSMA warning 03/07/2023. 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

  • Reading the Chain: Safe Horizon

    // FROM THE CASEFILE — SAFE HORIZON

    The Professor opens the file on Safe Horizon 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.

    Wallet trace — what the Professor maps:

    • Claimant-to-platform deposit transactions on the deposit chain used by Safe Horizon.
    • 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 summary — Safe Horizon casefile:

    • Safe Horizon off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Safe Horizon 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 Safe Horizon — the packet meets the off-ramp’s published compliance standard.
    • When the Safe Horizon 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. Casefile triage on Safe Horizon — the submission is read; a written assessment is delivered.
    2. Forensic trace on Safe Horizon — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the Safe Horizon endpoint is named.
    4. Recovery filing on Safe Horizon — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of Safe Horizon — the Professor follows the casefile until next-step documentation exists.

    What the Professor tracks across Safe Horizon casefiles:

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

    Lines the Professor will not cross:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Casefile Blocvester — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Blocvester 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:

    • Claimant-to-platform deposit transactions on the deposit chain used by Blocvester.
    • 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.

    From the lectern — off-ramp identification:

    • Blocvester off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
    • The Blocvester 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 Blocvester — the packet meets the off-ramp’s published compliance standard.
    • When the Blocvester off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

    How a Blocvester casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Blocvester 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 Blocvester packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Blocvester — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    What is never asked of a claimant:

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

    Why this platform is on our casefile

    Blocvester has been flagged as a fake broker/platform by IOSCO I-SCAN (United Kingdom – Financial Conduct Authority). reported 2025-12-09. Jurisdiction: United Kingdom. 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 My Easy Tron Bot — The Professor’s Note

    // FROM THE CASEFILE — MY EASY TRON BOT

    My Easy Tron Bot, operating from myeasytronbot.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to My Easy Tron Bot’s receiving wallet at myeasytronbot.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.

    Off-ramp reading — exchange counterparty for My Easy Tron Bot:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What we read in a My Easy Tron Bot casefile:

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

    Recovery scammers do these things; the Professor never does:

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

    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 Slad Sie

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Slad Sie 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.

    Trace summary — funds that left https::

    • Deposit confirmations from the claimant to Slad Sie’s receiving wallet at https:.
    • 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:

    • Slad Sie 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 Slad Sie is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Slad Sie — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Slad Sie casefile.

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

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

    What the on-chain reading covers:

    • Deposit-side chains in Slad Sie 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 Slad Sie packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Slad Sie — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    Slad Sie has been flagged as a fake broker/platform by IOSCO I-SCAN (Thailand – Securities and Exchange Commission). reported 2025-11-18. Jurisdiction: Thailand. 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/

  • WBFX — Annotated by the Professor

    // FROM THE CASEFILE — WBFX

    WBFX is a casefile under reading. The deposits to wbfx.io 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.

    From the marginalia — the deposit pathway:

    • Deposit-side hashes from claimant wallets into WBFX’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 summary — WBFX casefile:

    • WBFX 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 WBFX is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for WBFX — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the WBFX casefile.

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

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

    Reading-list — chains and exchanges in scope:

    • Chains tracked on WBFX — 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 WBFX — named exchange counterparties with public compliance contacts.
    • Filings supported on WBFX — 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:

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

    // FROM THE CASEFILE — COINB

    The Professor opens the file on CoinB 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.

    Trace summary — funds that left pehjosf.com:

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

    • CoinB’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 CoinB off-ramp wallet against historical laundering throughput.
    • The CoinB packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for CoinB, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

    Recovery pathway — how this casefile moves toward filing:

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

    What the casefile records — chains and counterparties:

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

    Recovery scammers do these things; the Professor never does:

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

    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 Manelygest

    // FROM THE CASEFILE — CTK NETWORK

    When deposits to Manelygest via manelygest.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.

    Trace summary — funds that left manelygest.com:

    • Deposit confirmations from the claimant to Manelygest’s receiving wallet at manelygest.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.

    From the lectern — off-ramp identification:

    • Manelygest 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 Manelygest is matched against compliance and chain-analytics datasets the Professor reads daily.
    • Compliance leverage applied to the named off-ramp for Manelygest — the packet is delivered in compliance-desk format.
    • Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Manelygest casefile.

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

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

    What the on-chain reading covers:

    • Deposit-side chains in Manelygest 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 Manelygest packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Manelygest — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

    Lines we never cross — by published policy:

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

    Why this platform is on our casefile

    Manelygest has been flagged as a fake broker/platform by IOSCO I-SCAN (Switzerland – Swiss Financial Market Supervisory Authority). reported 2025-09-29. Jurisdiction: Switzerland. 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/