On-chain reading — wallet flow for META TRANSACTION:

• Deposit confirmations from the claimant to META TRANSACTION’s receiving wallet at metatransaction.org.
• 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 — META TRANSACTION casefile:

• Endpoint counterparty in the META TRANSACTION casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• META TRANSACTION’s off-ramp wallet is then matched against compliance feeds the Professor maintains a standing read on.
• Leverage is applied to that named counterparty — the META TRANSACTION packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the META TRANSACTION off-ramp is non-cooperative, the casefile escalates to IC3, the relevant state AG, and (where dollar value warrants) a civil-discovery overlay for KYC.

Pathway to recovery — what happens after the trail is mapped:

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

Chains and off-ramps the Professor follows:

• Deposit + forwarding chains for META TRANSACTION — Bitcoin, Ethereum, Tron USDT-TRC20, plus the smart-contract chains (BSC, Polygon, Avalanche, Arbitrum, Optimism) that cross via bridges.
• Off-ramps the META TRANSACTION casefile may resolve to — centralised exchanges that respond to compliance filings.
• Filing pathways on META TRANSACTION — IC3, state AG, off-ramp compliance, and civil-discovery overlay.

Boundaries on every META TRANSACTION casefile — never crossed:

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