The annotation reads, wallet trace:

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

• Capital505 off-ramps consistently to centralised exchanges, Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Capital505 off-ramp address is matched to known compliance feeds, the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Capital505, the packet meets the off-ramp’s published compliance standard.
• When the Capital505 off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway, how this casefile moves toward filing:

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

What the Professor will never do, by policy:

• What the Professor will not do on Capital505, ask for a seed phrase.
• What the Professor will not do on Capital505, request remote-access logins.
• What the Professor will not do on Capital505, demand cash up front.
• What the Professor will not do on Capital505, promise a guarantee.
• What the Professor will not do on Capital505, call you out of the blue.