The annotation reads, wallet trace:

• Deposit confirmations from the claimant to Primebitts’s receiving wallet at primebitts.net.
• 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 reading, exchange counterparty for Primebitts:

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

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