The annotation reads, wallet trace:

• Deposit-side hashes from claimant wallets into AixCad’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.

The annotation continues, off-ramp endpoint:

• AixCad casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for AixCad is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for AixCad, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the AixCad casefile.

The Professor’s recovery note for AixCad:

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

Boundaries on every AixCad casefile, never crossed:

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