Trace summary, funds that left beebroker.io:

• Deposit-side hashes from claimant wallets into BeeBroker’s receiving addresses.
• Operator forwarding wallets, deposit consolidation documented to chain of custody standards.
• Inter-chain bridge transactions when value moves toward off-ramp liquidity.
• Mixer/obfuscation events the operator routed through, where present.
• Final off-ramp endpoint and named counterparty exchange.

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

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

Filing pathway, the next step after the off-ramp is identified:

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

What the on-chain reading covers:

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

Boundaries on every BeeBroker casefile, never crossed:

• Hard line on BeeBroker, no seed-phrase requests, period.
• Hard line on BeeBroker, no remote logins requested.
• Hard line on BeeBroker, no upfront cash retainer.
• Hard line on BeeBroker, no guarantee language.
• Hard line on BeeBroker, no unsolicited phone outreach.