Skip to content
Briefings are running a touch slower this week while we rebuild the foundations.See roadmap
European Tech Sovereignty
17MAY

Delhi stays silent seven days on OFAC designations

2 min read
14:28UTC

Lowdown Desk

TechnologyDeveloping
Key takeaway

Delhi has held seven days of silence on OFAC's Shamkhani designations as VLCCs gather at India-operated Chabahar.

India's Ministry of External Affairs (MEA) maintained public silence for seven days on the 15 April OFAC designations naming five Indian nationals and eight India-registered firms in the Shamkhani network . The first acknowledgement, whenever it comes, will land against a sharper operational backdrop than it would have a week ago.

Chabahar operational rights, held by India under a 2016 agreement with Tehran, create a direct India-US exposure as Windward detected seven VLCCs there on 20 April. The same MEA earlier summoned Iran's ambassador over IRGC fire on Sanmar Herald and Jag Arnav , , a quicker reflex when Indian-flagged bottoms were hit than when Indian nationals appeared on a US Treasury list. The silence is telling diplomatic economy: Delhi prefers to acknowledge neither the designations nor the Chabahar arithmetic on the same stage.

Deep Analysis

In plain English

On 15 April, the US Treasury's sanctions office named five Indian citizens and eight Indian companies as part of a network helping Iran's former national security adviser, Ali Shamkhani, move money. This is a serious step: it means those individuals and companies are now on a US blacklist, and any bank doing business with them faces potential US penalties. India's foreign ministry has not said a single word about this in seven days. They responded much faster , within 24 hours , when Iranian gunboats fired on Indian-flagged ships. Meanwhile, India holds the operating rights at Chabahar, the Iranian port where seven large oil tankers were detected on 20 April. If those ships are loading Iranian crude, India's operational role at the port puts it directly in the middle of US-Iran sanctions enforcement.

Deep Analysis
Root Causes

India's exposure on the Shamkhani designations has three structural components that the MEA cannot address simultaneously. The 2016 Chabahar agreement gives Delhi operational rights at a port where Iranian crude is now loading under conditions OFAC has not yet targeted but legally could.

The Shamkhani network designations name Indian nationals and firms in a sanctions list that creates secondary-sanctions liability for Indian banks processing those entities' transactions.

India's overall crude import diversification strategy, designed to reduce Gulf dependence, identified Iranian crude as one of three non-Gulf sources, a strategy US maximum-pressure policy directly undermines.

What could happen next?
  • Risk

    Delhi's silence becomes untenable if CENTCOM or OFAC targets Chabahar-loaded cargoes, forcing India to either enforce US sanctions at its own port or publicly oppose them , both options with significant economic and diplomatic cost.

First Reported In

Update #76 · Trump posts an exit Iran can't reach

Iran International· 22 Apr 2026
Read original
Different Perspectives
OpenForum Europe / open-source community
OpenForum Europe / open-source community
The EUR 350m Sovereign Tech Fund has no Commission host, no budget line, and no commissioner's name attached six weeks after the April conference, while Germany is already paying maintainers to staff international standards bodies. The CRA open-source guidance resolves contributor liability but leaves the financial-donations grey area open with the 11 September reporting clock running.
ASML / Christophe Fouquet
ASML / Christophe Fouquet
ASML's Q2 guidance miss of roughly EUR 300m below consensus reflects DUV revenue compression set by US export controls, not European policy. Fouquet said 2026 guidance accommodates potential outcomes of ongoing US-China trade discussions; a bipartisan US bill to tighten DUV sales further would accelerate the cross-subsidy thinning Chips Act II's equity authority is designed to address.
Anne Le Henanff / French G7 Presidency
Anne Le Henanff / French G7 Presidency
Le Henanff chairs the 29 May Bercy ministerial two days after Brussels adopts the Tech Sovereignty Package, making the G7 communique the first international read of the Omnibus enforcement split and CAIDA's scope. France's Cloud au Centre doctrine is already operational via the Scaleway Health Data Hub contract.
German federal government
German federal government
Berlin operationalises sovereignty through procurement mandates (the ODF requirement and the Sovereign Tech Standards programme) rather than waiting for Commission legislation. The Bundeskartellamt has still not received the Cohere-Aleph Alpha merger filing, leaving Germany's flagship AI champion in structural limbo six weeks after the deal resolved.
US Trade Representative
US Trade Representative
The USTR Section 301 investigation into EU digital rules closes with a 24 July 2026 final determination. CAIDA's public-sector cloud restriction sits within the criteria that triggered the 2020 Section 301 action against France's digital services tax, and the US has not signalled whether the Thales-Google S3NS arrangement resolves CLOUD Act jurisdiction concerns.
CISPE / Valentina Mingorance
CISPE / Valentina Mingorance
CISPE shipped its own pass-fail sovereignty badge in April to establish an industry-auditable floor the Commission could adopt. Whether CAIDA inherits the CISPE binary or the multi-tier SEAL approach will determine whether certification is enforceable by public contracting authorities or requires Commission discretion.