Trace summary — funds that left lunboux.com:

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

• On the Lunboux casefile, the off-ramp endpoint resolves to a centralised exchange — Bitfinex, MEXC, or Crypto.com seen often in this segment, with the larger venues routed through under stress.
• The off-ramp wallet for Lunboux is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A regulator-ready packet is delivered to the named counterparty — the Lunboux casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Lunboux escalates to IC3, state AG, and civil-discovery overlay.

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

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

What the on-chain reading covers:

• Deposit-side chains in Lunboux 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 Lunboux packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Lunboux — IC3 (US), state AG, off-ramp compliance desk, civil-discovery KYC where the dollar value warrants it.

Boundaries on every Lunboux casefile — never crossed:

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