The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into Bit Galaxy’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

Off-ramp summary, Bit Galaxy casefile:

• Off-ramp endpoint for Bit Galaxy resolves to a named centralised counterparty, the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Bit Galaxy’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Bit Galaxy is structured the way an off-ramp compliance reviewer expects to receive evidence, header, hashes, narrative, ask.
• If the Bit Galaxy off-ramp counterparty does not respond inside the published window, escalation routes through IC3, state AG, and civil discovery.

Recovery pathway, how this casefile moves toward filing:

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

Chains and off-ramps the Professor follows:

• Chains tracked on Bit Galaxy, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on Bit Galaxy, named exchange counterparties with public compliance contacts.
• Filings supported on Bit Galaxy, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Boundaries on every Bit Galaxy casefile, never crossed:

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