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

Tag: real recovery company

  • Professor’s Brief: Wolves Trades

    // FROM THE CASEFILE — WOLVES TRADES

    Wolves Trades, operating from wolvestrades.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 wolvestrades.com:

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

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

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

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

    What the casefile records — chains and counterparties:

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

    Boundaries on every Wolves Trades casefile — never crossed:

    • Wolves Trades policy — seed phrases are never requested.
    • Wolves Trades policy — remote-access logins are never requested.
    • Wolves Trades policy — no upfront cash retainer to scope.
    • Wolves Trades policy — no guaranteed-recovery language. None.
    • Wolves Trades 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

  • Reading the Chain: EasyTradeAPP

    // FROM THE CASEFILE — EASYTRADEAPP

    When deposits to EasyTradeAPP via easytradeapp.co 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-to-platform deposit transactions on the deposit chain used by EasyTradeAPP.
    • 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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    Reading-list — chains and exchanges in scope:

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

    Boundaries on every EasyTradeAPP casefile — never crossed:

    • EasyTradeAPP policy — seed phrases are never requested.
    • EasyTradeAPP policy — remote-access logins are never requested.
    • EasyTradeAPP policy — no upfront cash retainer to scope.
    • EasyTradeAPP policy — no guaranteed-recovery language. None.
    • EasyTradeAPP 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

  • Reading the Chain: Pluto500

    // FROM THE CASEFILE — PLUTO500

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

    Reading the wallets — Pluto500 casefile:

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

    The annotation continues — off-ramp endpoint:

    • Off-ramp endpoint for Pluto500 resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
    • Pluto500’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
    • The compliance packet for Pluto500 is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
    • If the Pluto500 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 Pluto500:

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

    What the Professor tracks across Pluto500 casefiles:

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

    What is never asked of a claimant:

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

  • Casefile Accessplanet — The Professor’s Note

    // FROM THE CASEFILE — ACCESSPLANET

    When deposits to Accessplanet via access-planet.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 access-planet.com:

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

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

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

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

    Chains and off-ramps the Professor follows:

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

    What is never asked of a claimant:

    • Accessplanet policy — seed phrases are never requested.
    • Accessplanet policy — remote-access logins are never requested.
    • Accessplanet policy — no upfront cash retainer to scope.
    • Accessplanet policy — no guaranteed-recovery language. None.
    • Accessplanet 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

  • Professor’s Brief: capital partnersgroup.com

    // FROM THE CASEFILE — CAPITAL PARTNERSGROUP.COM

    When deposits to capital partnersgroup.com via capital-partnersgroup.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.

    Wallet trace — what the Professor maps:

    • Deposit transaction hashes from the claimant wallet to the capital partnersgroup.com 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:

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the Professor tracks across capital partnersgroup.com casefiles:

    • Chains the Professor reads for capital partnersgroup.com casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
    • Off-ramps named in capital partnersgroup.com — major centralised venues with compliance desks that accept regulator-grade packets.
    • Filing pathways available on capital partnersgroup.com — 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:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Reading the Chain: Crets Beheer

    // FROM THE CASEFILE — WORLD MARKETS

    When deposits to Crets Beheer 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.

    On-chain reading — wallet flow for Crets Beheer:

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

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

    Recovery pathway — how this casefile moves toward filing:

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

    What the on-chain reading covers:

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

    Crets Beheer has been flagged as a Credit fraud by FSMA Belgium. FSMA warning 11/02/2026. 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

  • From the Lectern: AxePro Group

    // FROM THE CASEFILE — AXEPRO GROUP

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

    The annotation reads — wallet trace:

    • Initial deposit hashes to the AxePro Group receiving address at axeprogroup.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.

    From the lectern — off-ramp identification:

    • Endpoint counterparty in the AxePro 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.
    • AxePro 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 AxePro Group packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
    • If the AxePro 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.

    How a AxePro Group casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

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

    What the Professor will never do — by policy:

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

    Open a free consultation

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

    Open a Free Case Consultation   Submit Wallet for Trace

  • Professor’s Brief: Invetra

    // FROM THE CASEFILE — INVETRA

    When deposits to Invetra via invetra.co.id 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:

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

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

    What the Professor tracks across Invetra casefiles:

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

    Recovery scammers do these things; the Professor never does:

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

  • Reading the Chain: Horizon Gold

    // FROM THE CASEFILE — HORIZON GOLD

    Horizon Gold is a casefile under reading. The deposits to thehorizon-gol 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 — Horizon Gold casefile:

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

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

    What the Professor tracks across Horizon Gold casefiles:

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

    Lines we never cross — by published policy:

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

    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 Cappiterra-Options — The Professor’s Note

    // FROM THE CASEFILE — BERKAT FD SDN BHD

    The Professor opens the file on Cappiterra-Options 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 Cappiterra-Options.
    • 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:

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

    How a Cappiterra-Options casefile becomes a regulator-ready filing:

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

    Reading-list — chains and exchanges in scope:

    • Deposit-side chains in Cappiterra-Options 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 Cappiterra-Options packets — centralised exchanges that accept regulator-grade compliance filings.
    • Filing options on Cappiterra-Options — 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 Cappiterra-Options casefile — never request a seed phrase. Ever.
    • On the Cappiterra-Options casefile — never request remote-access logins to a wallet or exchange.
    • On the Cappiterra-Options casefile — never demand an upfront cash retainer to scope the matter.
    • On the Cappiterra-Options casefile — never promise a guaranteed recovery. The trail does not promise one.
    • On the Cappiterra-Options 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

    Cappiterra-Options 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/