The Professor’s off-ramp note:

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

1. Casefile review on SmartFX Bot, reading the submission against the no-go list.
2. Trace mapping on SmartFX Bot, pathway documented to chain of custody standard.
3. Off-ramp naming on SmartFX Bot, exchange endpoint identified.
4. Packet filing on SmartFX Bot, to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on SmartFX Bot.

Reading-list, chains and exchanges in scope:

• Chains tracked on SmartFX Bot, 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 SmartFX Bot, named exchange counterparties with public compliance contacts.
• Filings supported on SmartFX Bot, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Boundaries on every SmartFX Bot casefile, never crossed:

• Boundary on SmartFX Bot, seed phrases are off-limits.
• Boundary on SmartFX Bot, remote logins are off-limits.
• Boundary on SmartFX Bot, upfront cash retainers are off-limits.
• Boundary on SmartFX Bot, guaranteed-recovery promises are off-limits.
• Boundary on SmartFX Bot, unsolicited outbound contact is off-limits.