Trace summary — funds that left fxstockmarketglobal.com:

• Initial deposit hashes to the FX STOCK MARKET GLOBAL receiving address at fxstockmarketglobal.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.

Off-ramp reading — exchange counterparty for FX STOCK MARKET GLOBAL:

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

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

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

What the Professor tracks across FX STOCK MARKET GLOBAL casefiles:

• Chains the Professor reads for FX STOCK MARKET GLOBAL casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in FX STOCK MARKET GLOBAL — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on FX STOCK MARKET GLOBAL — 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:

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

The annotation reads — wallet trace:

• Deposit-side hashes from claimant wallets into NeoProFx’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.

The annotation continues — off-ramp endpoint:

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

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

1. Triage on NeoProFx — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on NeoProFx — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on NeoProFx — off-ramp endpoint matched to a named exchange counterparty.
4. File the NeoProFx 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 NeoProFx — the Professor stays on the casefile until a documented next step exists.

Chains and off-ramps the Professor follows:

• Chains the Professor reads for NeoProFx casefiles — BTC, ETH, Tron USDT, BNB Smart Chain, Avalanche, Polygon, Arbitrum, Optimism, plus the cross-chain bridges that link them.
• Off-ramps named in NeoProFx — major centralised venues with compliance desks that accept regulator-grade packets.
• Filing pathways available on NeoProFx — 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 NeoProFx — seed phrases are off-limits.
• Boundary on NeoProFx — remote logins are off-limits.
• Boundary on NeoProFx — upfront cash retainers are off-limits.
• Boundary on NeoProFx — guaranteed-recovery promises are off-limits.
• Boundary on NeoProFx — unsolicited outbound contact is off-limits.

Reading the wallets — Fundzo casefile:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Fundzo.
• 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 map — where the funds left the chain:

• Endpoint counterparty in the Fundzo casefile is named — typically a major venue such as OKX or Bybit, sometimes Gate.io or KuCoin, occasionally Binance or Huobi when liquidity allows.
• Fundzo’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 Fundzo packet is assembled to a standard the off-ramp’s compliance desk reads and acts on.
• If the Fundzo 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 Fundzo — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on Fundzo — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on Fundzo — off-ramp endpoint matched to a named exchange counterparty.
4. File the Fundzo 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 Fundzo — the Professor stays on the casefile until a documented next step exists.

What the casefile records — chains and counterparties:

• Chains the Fundzo 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 Fundzo — the major venues including OKX, Bybit, Binance and KuCoin, plus the regional venues operators rotate through under regulatory stress.
• Filings the Fundzo packet supports — IC3, the appropriate state attorney general, the off-ramp’s compliance desk, and a civil-discovery overlay where dollar value justifies it.

Recovery scammers do these things; the Professor never does:

• On the Fundzo casefile — never request a seed phrase. Ever.
• On the Fundzo casefile — never request remote-access logins to a wallet or exchange.
• On the Fundzo casefile — never demand an upfront cash retainer to scope the matter.
• On the Fundzo casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the Fundzo casefile — never call the claimant unsolicited. Written-only.

The annotation reads — wallet trace:

• Deposit transaction hashes from the claimant wallet to the Expert FX Brokers 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 summary — Expert FX Brokers casefile:

• Off-ramp endpoint for Expert FX Brokers resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Expert FX Brokers’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Expert FX Brokers is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Expert FX Brokers 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 Expert FX Brokers:

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

What the on-chain reading covers:

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

What the Professor will never do — by policy:

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

Reading the wallets — TradePower casefile:

• Deposit transaction hashes from the claimant wallet to the TradePower 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:

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

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

1. Triage on TradePower — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on TradePower — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on TradePower — off-ramp endpoint matched to a named exchange counterparty.
4. File the TradePower 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 TradePower — the Professor stays on the casefile until a documented next step exists.

What we read in a TradePower casefile:

• Chains in scope for TradePower — the chains that handle the volume of casefile activity in this segment (BTC, ETH, Tron, BSC, plus L2s).
• Off-ramps in scope for TradePower — named centralised exchanges with compliance leverage.
• Filings supported on TradePower — IC3, state AG, off-ramp desk, civil discovery as applicable.

What the Professor will never do — by policy:

• On the TradePower casefile — never request a seed phrase. Ever.
• On the TradePower casefile — never request remote-access logins to a wallet or exchange.
• On the TradePower casefile — never demand an upfront cash retainer to scope the matter.
• On the TradePower casefile — never promise a guaranteed recovery. The trail does not promise one.
• On the TradePower casefile — never call the claimant unsolicited. Written-only.

Reading the wallets — MetaForeignOptions casefile:

• Initial deposit hashes to the MetaForeignOptions receiving address at metaforeignoption.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.

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

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

The Professor’s recovery note for MetaForeignOptions:

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

Chains and off-ramps the Professor follows:

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

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

On-chain reading — wallet flow for CRYPTOTECKY:

• Deposit-side hashes from claimant wallets into CRYPTOTECKY’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:

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

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

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

Reading-list — chains and exchanges in scope:

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

Lines we never cross — by published policy:

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

Trace summary — funds that left abmsecurities-pk.com:

• Deposit-side hashes from claimant wallets into ABM Securities’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:

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

Recovery pathway — how this casefile moves toward filing:

1. First read on ABM Securities — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on ABM Securities — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for ABM Securities is named to a centralised exchange wallet.
4. Packet filing on ABM Securities — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with ABM Securities until a documented outcome or escalation step is on file.

What the Professor tracks across ABM Securities casefiles:

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

Recovery scammers do these things; the Professor never does:

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

Wallet trace — what the Professor maps:

• Deposit confirmations from the claimant to Leading Alliance’s receiving wallet at leading-alliance.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 reading — exchange counterparty for Leading Alliance:

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

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

1. First read on Leading Alliance — incoming submission is reviewed against the no-go list and a written go/no-go is returned in writing.
2. Wallet trace on Leading Alliance — deposit-to-off-ramp pathway is mapped across chains with verifiable hashes.
3. Counterparty identification — the off-ramp endpoint for Leading Alliance is named to a centralised exchange wallet.
4. Packet filing on Leading Alliance — IC3, state AG, off-ramp compliance desk; civil discovery if dollar value justifies it.
5. Casefile follow-through — the Professor stays with Leading Alliance until a documented outcome or escalation step is on file.

What we read in a Leading Alliance casefile:

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

What the Professor will never do — by policy:

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

Reading the wallets — Unicapital casefile:

• Initial deposit hashes to the Unicapital receiving address at unicapital.az.
• 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:

• Off-ramp endpoint for Unicapital resolves to a named centralised counterparty — the venue varies casefile to casefile, but the resolution always names a real exchange wallet.
• Unicapital’s off-ramp address is matched against the Professor’s compliance feed and against external chain-analytics datasets.
• The compliance packet for Unicapital is structured the way an off-ramp compliance reviewer expects to receive evidence — header, hashes, narrative, ask.
• If the Unicapital 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. Submission triage — Unicapital casefile reviewed against the no-go list, written reply within one business day.
2. Pathway trace — Unicapital deposit and forwarding wallets captured.
3. Endpoint identification — Unicapital off-ramp wallet named.
4. Filing — Unicapital packet delivered to IC3, state AG, off-ramp compliance, civil discovery as needed.
5. Ongoing follow — Unicapital stays on file until a documented next step is reached.

Chains and off-ramps the Professor follows:

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

Boundaries on every Unicapital casefile — never crossed:

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