The annotation reads, wallet trace:

• Initial deposit hashes to the Saham Berjaya receiving address at sahamberjaya.com.
• Hop-by-hop forwarding wallets across the deposit chain, captured with chain of custody hashes.
• Cross-chain bridge events that move value into the chain where liquidity supports the eventual off-ramp.
• Obfuscation events through mixer contracts and privacy services.
• Centralised-exchange off-ramp wallets, the named counterparty that holds compliance leverage.

From the lectern, off-ramp identification:

• On the Saham Berjaya 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 Saham Berjaya is run against chain-analytics datasets and the Professor’s own compliance feeds.
• A evidence packet is delivered to the named counterparty, the Saham Berjaya casefile is built to the off-ramp’s compliance standard.
• Where the off-ramp will not engage, Saham Berjaya escalates to IC3, state AG, and civil-discovery overlay.

How a Saham Berjaya casefile becomes a evidence filing:

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

What we read in a Saham Berjaya casefile:

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

Lines we never cross, by published policy:

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