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

Tag: scam help

  • Office Hours on GREENFX

    // FROM THE CASEFILE — GREENFX

    When deposits to GREENFX via greenfx.ltd 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.

    The annotation reads — wallet trace:

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

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

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

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

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    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: Trader500

    // FROM THE CASEFILE — TRADER500

    When a deposit ledgered to Trader500 at trader500.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 trader500.com:

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

    • Off-ramp endpoint for Trader500 resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Trader500’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Trader500 is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Trader500 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 review on Trader500 — reading the submission against the no-go list.
    2. Trace mapping on Trader500 — pathway documented to chain-of-custody standard.
    3. Off-ramp naming on Trader500 — exchange endpoint identified.
    4. Packet filing on Trader500 — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
    5. Documented follow-through on Trader500.

    What we read in a Trader500 casefile:

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

    Recovery scammers do these things; the Professor never does:

    • What the Professor will not do on Trader500 — ask for a seed phrase.
    • What the Professor will not do on Trader500 — request remote-access logins.
    • What the Professor will not do on Trader500 — demand cash up front.
    • What the Professor will not do on Trader500 — promise a guarantee.
    • What the Professor will not do on Trader500 — 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 Starekco

    // FROM THE CASEFILE — STAREKCO

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

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

    From the lectern — off-ramp identification:

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

    What the Professor tracks across Starekco casefiles:

    • Chains the Starekco 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 Starekco — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
    • Filings the Starekco packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • ALAN KIRKHOPE GROUP — Annotated by the Professor

    // FROM THE CASEFILE — ALAN KIRKHOPE GROUP

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

    Reading the wallets — ALAN KIRKHOPE GROUP casefile:

    • Initial deposit hashes to the ALAN KIRKHOPE GROUP receiving address at alankirkhopegroup.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    The Professor’s off-ramp note:

    • ALAN KIRKHOPE GROUP’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 ALAN KIRKHOPE GROUP off-ramp wallet against historical laundering throughput.
    • The ALAN KIRKHOPE GROUP packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
    • Escalation pathways for ALAN KIRKHOPE GROUP, 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. Casefile triage on ALAN KIRKHOPE GROUP — the submission is read; a written assessment is delivered.
    2. Forensic trace on ALAN KIRKHOPE GROUP — every hop in the deposit pathway is captured and hashed.
    3. Off-ramp identification — the ALAN KIRKHOPE GROUP endpoint is named.
    4. Recovery filing on ALAN KIRKHOPE GROUP — packet delivered to IC3, state AG, off-ramp compliance, and civil discovery as applicable.
    5. Continuing review of ALAN KIRKHOPE GROUP — the Professor follows the casefile until next-step documentation exists.

    What the Professor tracks across ALAN KIRKHOPE GROUP casefiles:

    • Chains tracked on ALAN KIRKHOPE GROUP — 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 ALAN KIRKHOPE GROUP — named exchange counterparties with public compliance contacts.
    • Filings supported on ALAN KIRKHOPE GROUP — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

    What is never asked of a claimant:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Exprime — Annotated by the Professor

    // FROM THE CASEFILE — EXPRIME

    Funds you sent to Exprime (exprime.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.

    The annotation reads — wallet trace:

    • Deposit transaction hashes from the claimant wallet to the Exprime 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 — Exprime casefile:

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

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

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

    What we read in a Exprime casefile:

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

    Recovery scammers do these things; the Professor never does:

    • Recovery scammers do these things on Exprime; the Professor never does — request seed phrases.
    • Recovery scammers do these things on Exprime; the Professor never does — request remote logins.
    • Recovery scammers do these things on Exprime; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on Exprime; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on Exprime; 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

  • Office Hours on DURBAN TRADEFX

    // FROM THE CASEFILE — DURBAN TRADEFX

    DURBAN TRADEFX, operating from durbantradefx.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    Trace summary — funds that left durbantradefx.com:

    • Deposit transaction hashes from the claimant wallet to the DURBAN TRADEFX 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 reading — exchange counterparty for DURBAN TRADEFX:

    • Off-ramp endpoint for DURBAN TRADEFX resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • DURBAN TRADEFX’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for DURBAN TRADEFX is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the DURBAN TRADEFX 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. Submission triage — DURBAN TRADEFX casefile reviewed against the no-go list, written reply within one business day.
    2. Pathway trace — DURBAN TRADEFX deposit and forwarding wallets captured.
    3. Endpoint identification — DURBAN TRADEFX off-ramp wallet named.
    4. Filing — DURBAN TRADEFX packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
    5. Ongoing follow — DURBAN TRADEFX stays on file until a documented next step is reached.

    What the on-chain reading covers:

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

    What the Professor will never do — by policy:

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

    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

  • Office Hours on 7Option

    // FROM THE CASEFILE — 7OPTION

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

    • Deposit transaction hashes from the claimant wallet to the 7Option 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 reading — exchange counterparty for 7Option:

    • On the 7Option 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 7Option is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the 7Option casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, 7Option escalates to IC3, state AG, and civil-discovery overlay.

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

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

    What the on-chain reading covers:

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

    Lines the Professor will not cross:

    • Recovery scammers do these things on 7Option; the Professor never does — request seed phrases.
    • Recovery scammers do these things on 7Option; the Professor never does — request remote logins.
    • Recovery scammers do these things on 7Option; the Professor never does — demand upfront cash.
    • Recovery scammers do these things on 7Option; the Professor never does — guarantee a recovery.
    • Recovery scammers do these things on 7Option; 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

  • HBCEC — Annotated by the Professor

    // FROM THE CASEFILE — HBCEC

    When deposits to HBCEC via highbitcapitalexpertcloudmining.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 highbitcapitalexpertcloudmining.com:

    • Deposit transaction hashes from the claimant wallet to the HBCEC 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:

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

    The Professor’s recovery note for HBCEC:

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

    Reading-list — chains and exchanges in scope:

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

    What is never asked of a claimant:

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

    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

  • From the Lectern: Liberty Invested Limited

    // FROM THE CASEFILE — LIBERTY INVESTED LIMITED

    Liberty Invested Limited is a casefile under reading. The deposits to libertyinvestedlimitedltd.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.

    The annotation reads — wallet trace:

    • Deposit confirmations from the claimant to Liberty Invested Limited’s receiving wallet at libertyinvestedlimitedltd.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 map — where the funds left the chain:

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

    What the Professor tracks across Liberty Invested Limited casefiles:

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

    Lines the Professor will not cross:

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

  • Office Hours on Evergreen Prime Capital

    // FROM THE CASEFILE — EVERGREEN PRIME CAPITAL

    Evergreen Prime Capital, operating from evergreenprimecapital.com, leaves a chain trail whether the platform answers email or not. The Professor reads that trail as a primary source — annotated, dated, cited.

    On-chain reading — wallet flow for Evergreen Prime Capital:

    • Initial deposit hashes to the Evergreen Prime Capital receiving address at evergreenprimecapital.com.
    • Hop-by-hop forwarding wallets across the deposit chain, captured with chain-of-custody hashes.
    • Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
    • Obfuscation events through mixer contracts and privacy services.
    • Centralised-exchange off-ramp wallets — the named counterparty that holds compliance leverage.

    The Professor’s off-ramp note:

    • On the Evergreen Prime Capital 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 Evergreen Prime Capital is run against chain-analytics datasets and the Professor’s own compliance feeds.
    • A regulator-ready packet is delivered to the named counterparty — the Evergreen Prime Capital casefile is built to the off-ramp’s compliance standard.
    • Where the off-ramp will not engage, Evergreen Prime Capital escalates to IC3, state AG, and civil-discovery overlay.

    The Professor’s recovery note for Evergreen Prime Capital:

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

    Reading-list — chains and exchanges in scope:

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

    Lines the Professor will not cross:

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

    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