Wallet trace — what the Professor maps:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Joytrust.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

Off-ramp summary — Joytrust casefile:

• Endpoint counterparty in the Joytrust casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Joytrust’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 Joytrust packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Joytrust 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.

How a Joytrust casefile becomes a regulator-ready filing:

1. Submission triage — Joytrust casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — Joytrust deposit and forwarding wallets captured.
3. Endpoint identification — Joytrust off-ramp wallet named.
4. Filing — Joytrust packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — Joytrust stays on file until a documented next step is reached.

Reading-list — chains and exchanges in scope:

• Chains the Professor reads for Joytrust casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in Joytrust — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on Joytrust — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Lines the Professor will not cross:

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

From the marginalia — the deposit pathway:

• Deposit transaction hashes from the claimant wallet to the Binance Center AI platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

From the lectern — off-ramp identification:

• Binance Center AI 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 Binance Center AI is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for Binance Center AI — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the Binance Center AI casefile.

Recovery sequence — from on-chain reading to filed packet:

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

What the casefile records — chains and counterparties:

• Chains the Binance Center AI casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
• Off-ramps relevant to Binance Center AI — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Binance Center AI packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

What is never asked of a claimant:

• Boundary on Binance Center AI — seed phrases are off-limits.
• Boundary on Binance Center AI — remote logins are off-limits.
• Boundary on Binance Center AI — upfront cash retainers are off-limits.
• Boundary on Binance Center AI — guaranteed-recovery promises are off-limits.
• Boundary on Binance Center AI — unsolicited outbound contact is off-limits.

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the Raiseforex platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

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

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

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

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

What we read in a Raiseforex casefile:

• Chains the Professor reads for Raiseforex casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in Raiseforex — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on Raiseforex — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

What is never asked of a claimant:

• Boundary on Raiseforex — seed phrases are off-limits.
• Boundary on Raiseforex — remote logins are off-limits.
• Boundary on Raiseforex — upfront cash retainers are off-limits.
• Boundary on Raiseforex — guaranteed-recovery promises are off-limits.
• Boundary on Raiseforex — unsolicited outbound contact is off-limits.

On-chain reading — wallet flow for Mayfair Exchange Mayfair Finance:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Mayfair Exchange Mayfair Finance.
• Forwarding wallets on the deposit chain — each hop documented with the forwarding tx hash and the consolidating wallet.
• Bridge events into chains where the operator can off-ramp at scale.
• Mixer or privacy-service interactions, where present, listed with the contract address and the deposit/withdraw side.
• Off-ramp endpoint — the centralised exchange deposit address holding the compliance lever.

From the lectern — off-ramp identification:

• Mayfair Exchange Mayfair Finance off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Mayfair Exchange Mayfair Finance off-ramp address is matched to known compliance feeds — the Professor’s standing dataset plus chain-analytics references.
• Compliance leverage is applied at the named counterparty for Mayfair Exchange Mayfair Finance — the packet meets the off-ramp’s published compliance standard.
• When the Mayfair Exchange Mayfair Finance off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

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

1. Submission triage — Mayfair Exchange Mayfair Finance casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — Mayfair Exchange Mayfair Finance deposit and forwarding wallets captured.
3. Endpoint identification — Mayfair Exchange Mayfair Finance off-ramp wallet named.
4. Filing — Mayfair Exchange Mayfair Finance packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — Mayfair Exchange Mayfair Finance stays on file until a documented next step is reached.

Chains and off-ramps the Professor follows:

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

Lines we never cross — by published policy:

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

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the AlphaStocking platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

The annotation continues — off-ramp endpoint:

• AlphaStocking 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 AlphaStocking is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for AlphaStocking — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the AlphaStocking casefile.

How a AlphaStocking casefile becomes a regulator-ready filing:

1. Casefile review on AlphaStocking — reading the submission against the no-go list.
2. Trace mapping on AlphaStocking — pathway documented to chain-of-custody standard.
3. Off-ramp naming on AlphaStocking — exchange endpoint identified.
4. Packet filing on AlphaStocking — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on AlphaStocking.

What the on-chain reading covers:

• Chains tracked on AlphaStocking — 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 AlphaStocking — named exchange counterparties with public compliance contacts.
• Filings supported on AlphaStocking — 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:

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

Trace summary — funds that left blacksuitbrokers.com:

• Deposit transaction hashes from the claimant wallet to the FCS Bussiness Solutions platform receiving address.
• Forwarding wallets the platform consolidated through — typically two to four hops on the deposit chain (BTC / ETH / USDT-TRC20 / BSC / Polygon / Arbitrum / Optimism / Avalanche).
• Bridge crossings between chains, where the operator moves value into a chain with deeper liquidity ahead of the off-ramp.
• Mixer interactions — Tornado-Cash variants, Sinbad, and the smaller obfuscation services that operators rotate through under regulatory pressure.
• Final off-ramp wallet — the centralised exchange deposit address that received the consolidated funds.

Off-ramp reading — exchange counterparty for FCS Bussiness Solutions:

• Endpoint counterparty in the FCS Bussiness Solutions casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• FCS Bussiness Solutions’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 FCS Bussiness Solutions packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the FCS Bussiness Solutions 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. Triage on FCS Bussiness Solutions — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on FCS Bussiness Solutions — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on FCS Bussiness Solutions — off-ramp endpoint matched to a named exchange counterparty.
4. File the FCS Bussiness Solutions packet — IC3, state AG (where loss meets state thresholds), off-ramp compliance desk, and civil-discovery overlay where dollar value supports it.
5. Follow-through on FCS Bussiness Solutions — the Professor stays on the casefile until a documented next step exists.

Chains and off-ramps the Professor follows:

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

What is never asked of a claimant:

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

Reading the wallets — BANEX CAPITAL LTD casefile:

• Claimant-to-platform deposit transactions on the deposit chain used by BANEX CAPITAL LTD.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet — the named centralised-exchange endpoint.

The Professor’s off-ramp note:

• BANEX CAPITAL LTD 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 BANEX CAPITAL LTD is matched against compliance and chain-analytics datasets the Professor reads daily.
• Compliance leverage applied to the named off-ramp for BANEX CAPITAL LTD — the packet is delivered in compliance-desk format.
• Non-cooperative off-ramps trigger IC3 + state-AG + civil-discovery escalation on the BANEX CAPITAL LTD casefile.

Recovery sequence — from on-chain reading to filed packet:

1. Casefile review on BANEX CAPITAL LTD — reading the submission against the no-go list.
2. Trace mapping on BANEX CAPITAL LTD — pathway documented to chain-of-custody standard.
3. Off-ramp naming on BANEX CAPITAL LTD — exchange endpoint identified.
4. Packet filing on BANEX CAPITAL LTD — to the named off-ramp, IC3, state AG; civil discovery overlay as applicable.
5. Documented follow-through on BANEX CAPITAL LTD.

What we read in a BANEX CAPITAL LTD casefile:

• Chains tracked on BANEX CAPITAL LTD — 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 BANEX CAPITAL LTD — named exchange counterparties with public compliance contacts.
• Filings supported on BANEX CAPITAL LTD — IC3, state AG, off-ramp compliance, civil discovery — selected by the dollar value and the off-ramp’s responsiveness.

What the Professor will never do — by policy:

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

Wallet trace — what the Professor maps:

• Claimant-to-platform deposit transactions on the deposit chain used by VRN Capitals.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet — the named centralised-exchange endpoint.

The annotation continues — off-ramp endpoint:

• VRN Capitals’s off-ramp endpoint, in this casefile, is the centralised exchange that holds compliance leverage — typically named in the packet alongside the deposit address.
• Chain-analytics datasets cross-reference the VRN Capitals off-ramp wallet against historical laundering throughput.
• The VRN Capitals packet is delivered to the off-ramp compliance desk in a format the desk’s reviewers act on.
• Escalation pathways for VRN Capitals, where needed: IC3, the relevant state AG, and a civil-discovery overlay for KYC on the off-ramp wallet.

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

1. Submission triage — VRN Capitals casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — VRN Capitals deposit and forwarding wallets captured.
3. Endpoint identification — VRN Capitals off-ramp wallet named.
4. Filing — VRN Capitals packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — VRN Capitals stays on file until a documented next step is reached.

Chains and off-ramps the Professor follows:

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

Recovery scammers do these things; the Professor never does:

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

From the marginalia — the deposit pathway:

• Claimant-to-platform deposit transactions on the deposit chain used by UBanker.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet — the named centralised-exchange endpoint.

The Professor’s off-ramp note:

• Endpoint counterparty in the UBanker casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• UBanker’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 UBanker packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the UBanker 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.

The Professor’s recovery note for UBanker:

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

What the Professor tracks across UBanker casefiles:

• Chains the Professor reads for UBanker casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in UBanker — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on UBanker — IC3 for US claimants, state AG offices, off-ramp compliance, and civil-discovery overlay for high-value loss.

Lines we never cross — by published policy:

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

Trace summary — funds that left valorica.io:

• Claimant-to-platform deposit transactions on the deposit chain used by VALORICA.
• Operator-controlled forwarding wallets where deposits consolidate ahead of laundering or off-ramping.
• Cross-chain bridge events to chains with deeper exchange liquidity.
• Privacy-service interactions, where present in the trail.
• Off-ramp wallet — the named centralised-exchange endpoint.

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

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

The Professor’s recovery note for VALORICA:

1. Submission triage — VALORICA casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — VALORICA deposit and forwarding wallets captured.
3. Endpoint identification — VALORICA off-ramp wallet named.
4. Filing — VALORICA packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — VALORICA stays on file until a documented next step is reached.

What the casefile records — chains and counterparties:

• Chains the VALORICA casefile may touch — Bitcoin and Ethereum at the deposit side, Tron USDT-TRC20 in stablecoin pathways, BNB Smart Chain and the L2s (Arbitrum, Optimism, Polygon, Base) where bridges link them.
• Off-ramps relevant to VALORICA — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the VALORICA packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

What the Professor will never do — by policy:

• What the Professor will not do on VALORICA — ask for a seed phrase.
• What the Professor will not do on VALORICA — request remote-access logins.
• What the Professor will not do on VALORICA — demand cash up front.
• What the Professor will not do on VALORICA — promise a guarantee.
• What the Professor will not do on VALORICA — call you out of the blue.