The annotation reads, wallet trace:

• Deposit confirmations from the claimant to MariganzFX’s receiving wallet at mariganz.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 Professor’s off-ramp note:

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

Recovery pathway, how this casefile moves toward filing:

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

What the Professor will never do, by policy:

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