Off-ramp map, where the funds left the chain:

• crownledger 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 crownledger is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for crownledger, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the crownledger casefile.

Recovery sequence, from on-chain reading to filed packet:

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

Reading-list, chains and exchanges in scope:

• Deposit-side chains in crownledger casefiles, typically the major chains (BTC, ETH) and the high-throughput stablecoin chains (Tron USDT, BSC USDT), with bridge crossings noted.
• Off-ramps named in crownledger packets, centralised exchanges that accept regulator-grade compliance filings.
• Filing options on crownledger, IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Boundaries on every crownledger casefile, never crossed:

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