Trace summary, funds that left qfswealthmanagement.live:

• Deposit confirmations from the claimant to growbot.io’s receiving wallet at qfswealthmanagement.live.
• 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.

The annotation continues, off-ramp endpoint:

• growbot.io casefiles end at a centralised exchange, Bybit, KuCoin, OKX, or Gate.io are common; the casefile names the actual deposit address that received the consolidated funds.
• Off-ramp wallet for growbot.io is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for growbot.io, the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the growbot.io casefile.

The Professor’s recovery note for growbot.io:

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

What the on-chain reading covers:

• Chains tracked on growbot.io, Bitcoin and Ethereum at the deposit side; Tron USDT-TRC20 and BSC at the consolidation side; bridges crossed where the operator chases liquidity.
• Off-ramps tracked on growbot.io, named exchange counterparties with public compliance contacts.
• Filings supported on growbot.io, IC3, state AG, off-ramp compliance, civil discovery, selected by the dollar value and the off-ramp’s responsiveness.

Lines the Professor will not cross:

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