The annotation reads, wallet trace:

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

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

How a Inefex casefile becomes a evidence filing:

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

Boundaries on every Inefex casefile, never crossed:

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