Reading the wallets, UnionTrust casefile:

• Deposit confirmations from the claimant to UnionTrust’s receiving wallet at uniontrustltd.com.
• Forwarding-wallet pathway documented hop-by-hop with chain of custody hashes.
• Cross-chain bridge transactions where the operator routed value out of the deposit chain.
• Mixer or coin-join interactions, where applicable.
• Final off-ramp at a centralised exchange, the compliance counterparty named in the recovery filing.

Off-ramp summary, UnionTrust casefile:

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

How a UnionTrust casefile becomes a evidence filing:

1. Read the UnionTrust submission, written go/no-go returned.
2. Map the UnionTrust wallet trail, every hop captured with chain of custody hashes.
3. Name the UnionTrust off-ramp, endpoint counterparty identified.
4. Build and file the UnionTrust recovery packet, to IC3, state AG, off-ramp compliance, civil-discovery overlay.
5. Stay on the UnionTrust file, until written next steps exist.

Boundaries on every UnionTrust casefile, never crossed:

• On the UnionTrust casefile, never request a seed phrase. Ever.
• On the UnionTrust casefile, never request remote-access logins to a wallet or exchange.
• On the UnionTrust casefile, never demand an upfront cash retainer to scope the matter.
• On the UnionTrust casefile, never promise a guaranteed recovery. The trail does not promise one.
• On the UnionTrust casefile, never call the claimant unsolicited. Written-only.