Reading the wallets, NorthUnion casefile:

• Claimant deposit hashes, provided in the case submission and verified against the public ledger for NorthUnion.
• Forwarding wallets on the deposit chain, each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint, the centralised exchange deposit address holding the compliance lever.

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

1. First read on NorthUnion, incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on NorthUnion, deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification, the off-ramp endpoint for NorthUnion is named to a centralised exchange wallet.
4. Packet filing on NorthUnion, IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through, the Professor stays with NorthUnion until a documented outcome or escalation step is on file.

Reading-list, chains and exchanges in scope:

• Chains in scope for NorthUnion, the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for NorthUnion, named centralised exchanges with compliance leverage.
• Filings supported on NorthUnion, IC3, state AG, off-ramp desk, civil discovery as applicable.

Boundaries on every NorthUnion casefile, never crossed:

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