Wallet trace — what the Professor maps:

• Deposit-side hashes from claimant wallets into Multivest’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 map — where the funds left the chain:

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

How a Multivest casefile becomes a regulator-ready filing:

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

What the Professor tracks across Multivest casefiles:

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

Lines we never cross — by published policy:

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