Wallet trace — what the Professor maps:

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

• VINTARIO INVEST off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The VINTARIO INVEST 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 VINTARIO INVEST — the packet meets the off-ramp’s published compliance standard.
• When the VINTARIO INVEST 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. Triage on VINTARIO INVEST — submission read against a no-go checklist, written go/no-go returned to the claimant inside one business day.
2. Trace on VINTARIO INVEST — deposit pathway mapped across chains, captured with chain-of-custody hashes.
3. Identify on VINTARIO INVEST — off-ramp endpoint matched to a named exchange counterparty.
4. File the VINTARIO INVEST 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 VINTARIO INVEST — the Professor stays on the casefile until a documented next step exists.

What the Professor tracks across VINTARIO INVEST casefiles:

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

What is never asked of a claimant:

• Recovery scammers do these things on VINTARIO INVEST; the Professor never does — request seed phrases.
• Recovery scammers do these things on VINTARIO INVEST; the Professor never does — request remote logins.
• Recovery scammers do these things on VINTARIO INVEST; the Professor never does — demand upfront cash.
• Recovery scammers do these things on VINTARIO INVEST; the Professor never does — guarantee a recovery.
• Recovery scammers do these things on VINTARIO INVEST; the Professor never does — call you unsolicited.

Reading the wallets — TitanWealth24 casefile:

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

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

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

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

What the casefile records — chains and counterparties:

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

Boundaries on every TitanWealth24 casefile — never crossed:

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

Reading the wallets — EquityTrade casefile:

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

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

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

What the casefile records — chains and counterparties:

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

What is never asked of a claimant:

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

The annotation reads — wallet trace:

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

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

How a GEMI INVESTMENTS casefile becomes a regulator-ready filing:

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

Reading-list — chains and exchanges in scope:

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

What is never asked of a claimant:

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

The annotation reads — wallet trace:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for Monolux Trade Group.
• 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.

The Professor’s off-ramp note:

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

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

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

Chains and off-ramps the Professor follows:

• Deposit-side chains in Monolux Trade Group 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 Monolux Trade Group packets — centralised exchanges that accept regulator-grade compliance filings.
• Filing options on Monolux Trade Group — 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:

• Recovery scammers do these things on Monolux Trade Group; the Professor never does — request seed phrases.
• Recovery scammers do these things on Monolux Trade Group; the Professor never does — request remote logins.
• Recovery scammers do these things on Monolux Trade Group; the Professor never does — demand upfront cash.
• Recovery scammers do these things on Monolux Trade Group; the Professor never does — guarantee a recovery.
• Recovery scammers do these things on Monolux Trade Group; the Professor never does — call you unsolicited.

The annotation reads — wallet trace:

• Claimant deposit hashes — provided in the case submission and verified against the public ledger for MARKET4S.
• 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.

The Professor’s off-ramp note:

• MARKET4S off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The MARKET4S 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 MARKET4S — the packet meets the off-ramp’s published compliance standard.
• When the MARKET4S off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

The Professor’s recovery note for MARKET4S:

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

What the on-chain reading covers:

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

Recovery scammers do these things; the Professor never does:

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

The annotation reads — wallet trace:

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

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

How a Forex Steady casefile becomes a regulator-ready filing:

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

What we read in a Forex Steady casefile:

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

What is never asked of a claimant:

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

Reading the wallets — BTI casefile:

• Claimant-to-platform deposit transactions on the deposit chain used by BTI.
• 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 summary — BTI casefile:

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

The Professor’s recovery note for BTI:

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

What we read in a BTI casefile:

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

Lines we never cross — by published policy:

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

Trace summary — funds that left genexfx.net:

• Initial deposit hashes to the Genex FX receiving address at genexfx.net.
• 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.

The annotation continues — off-ramp endpoint:

• Genex FX off-ramps consistently to centralised exchanges — Coinbase, Kraken, and Gemini appear less often than the offshore venues; the casefile names the actual endpoint.
• The Genex FX 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 Genex FX — the packet meets the off-ramp’s published compliance standard.
• When the Genex FX off-ramp does not respond, escalation runs through IC3 (for US claimants), state AG, and (above a dollar threshold) civil-discovery overlay.

Recovery pathway — how this casefile moves toward filing:

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

What the casefile records — chains and counterparties:

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

Lines we never cross — by published policy:

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

Trace summary — funds that left fergofx.com:

• Deposit confirmations from the claimant to FERGOFX’s receiving wallet at fergofx.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.

The annotation continues — off-ramp endpoint:

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

Recovery pathway — how this casefile moves toward filing:

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

What the Professor tracks across FERGOFX casefiles:

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

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