The annotation reads, wallet trace:

• Claimant-to-platform deposit transactions on the deposit chain used by Billionext.
• 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 map, where the funds left the chain:

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

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

Boundaries on every Billionext casefile, never crossed:

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