On 18 and 19 May 2026, Iranian state-affiliated reporting in Fars news agency and follow-up coverage in Al Jazeera and the United States insurance trade publication Claims Journal disclosed that the Iranian government has begun offering maritime war-risk and protection-and-indemnity insurance for vessels transiting the Strait of Hormuz, under the brand name “Hormuz Safe.” The arrangement is presented as a state-backed insurance product covering cargo and hull war risks for vessels using the corridor administered by the Persian Gulf Strait Authority, with premiums and claims settled in cryptocurrency.
The launch lands one day after the formal announcement of the PGSA itself, analysed in the post on the PGSA on the Suez/Panama yardstick. The site has been arguing since the 11 May war-risk underwriters post that the most important commercial gatekeeper to Hormuz reopening is the global underwriter market, not the operational or diplomatic posture of the principal parties, and that the underwriter posture cannot move structurally without an institutional configuration to underwrite against. Hormuz Safe is Iran’s institutional answer to the same problem from the opposite direction. This post reads what Hormuz Safe actually does, where it sits in the global underwriter market, and what it would have to do to replace the function the International Group P&I Clubs presently are not performing.
What Hormuz Safe is, in the public record
The publicly available description of Hormuz Safe in the Fars reporting and the Claims Journal piece indicates the following design elements. The product is offered through a website branded “Hormuz Safe” accessible to vessel operators who have completed the PGSA vetting process. The product covers maritime cargoes transiting the strait and immediately adjacent Gulf waters. Premiums are quoted and paid in cryptocurrency, with Bitcoin, USDT (Tether), and yuan-stable instruments cited as the supported settlement channels. The underwriter standing behind the product is the Iranian state, in some combination of the Bonyad-affiliated Central Insurance of Iran, IRGC-controlled financial intermediaries, and possibly the Supreme National Security Council’s administrative apparatus. The Iranian government characterises the product as providing “encrypted verification capability” for cover certification, a phrase that is plausibly a reference to on-chain certificate-of-insurance issuance and verification.
What Hormuz Safe is not, on the same public record, is a member of the International Group of Protection and Indemnity Clubs. The International Group is the global mutual-insurance arrangement of twelve P&I clubs that, between them, cover approximately ninety per cent of the world’s ocean-going tonnage. The Group operates on a reinsurance pool that aggregates large casualty exposures and prices them across the global membership. Hormuz Safe is a separate, state-backed insurance product operating outside the International Group’s pool, with no reinsurance integration into the global mutual-insurance architecture and no published participation in the salvage, casualty-management, and dispute-resolution arrangements the International Group runs.
What Hormuz Safe does not replace
The work the International Group P&I Clubs do for the operator class is, in shorthand, three things: (1) it provides the standard liability cover that protects the shipowner against the long-tail catastrophic-loss exposures (pollution, salvage, wreck removal, cargo total loss, crew injury, third-party damages) that flag-state, port-state, and counterparty jurisdictions require for lawful operation; (2) it provides the global reinsurance pool that makes that cover economically viable at premiums the operator class can afford to pay; (3) it provides the standing institutional infrastructure for casualty management, salvage coordination, evidentiary collection, and dispute resolution that the underwriters rely on for loss-control.
Hormuz Safe, on its present design, can perform the first function in a limited way — it can issue policies that nominally cover the relevant exposures for vessels operating under the PGSA arrangement. It cannot, however, perform the second function (reinsurance) without integration into the global reinsurance market, which it does not have. The economic viability of Hormuz Safe coverage at the premium levels the Iranian government is plausibly willing to charge depends on either an extremely small loss experience (so the premiums are sufficient on a one-pot basis) or an implicit Iranian state guarantee (which converts the insurance product into a sovereign-credit instrument with the Iranian state as the counterparty). Either possibility is workable for a small subset of the operator class for a limited period; neither scales to replacing the International Group P&I cover for the global tanker fleet.
Hormuz Safe cannot perform the third function (institutional casualty-management infrastructure) without standing relationships with the International Maritime Organisation, the International Salvage Union, the International Tanker Owners Pollution Federation, and the operator-side institutional bodies that the existing underwriters rely on. Those relationships do not exist for Hormuz Safe on the public record, and the relationships the Iranian state does have with those bodies are presently strained for reasons that the 25 April ICS statement post documented.
The crypto-settlement layer
The cryptocurrency settlement design of Hormuz Safe interacts with the channel-leg analysis the site set out in the Tether stablecoin settlement post and reinforced in the China Blocking Rules post. The 24 April Tether wallet-freeze action of the United States Treasury demonstrated that the stablecoin settlement layer is not, as is sometimes claimed in the cryptocurrency policy discussion, beyond the reach of OFAC compliance pressure. Tether responded to the OFAC designations by freezing the named wallets within hours. Bitcoin, on the same analysis, is also subject to chain-analytics-based identification of designated counterparties, and the major exchanges, on/off ramps, and OTC desks subject themselves to OFAC compliance pressure.
Hormuz Safe’s choice of crypto settlement is therefore not, in the institutional sense, a free move. It is a move that places the channel leg of the insurance arrangement under the same compliance pressure that the channel leg of the PGSA toll arrangement and the channel leg of the Iranian crude buyer arrangement face. The leg can operate inside the China-tolerant subset of the operator class that has the necessary banking, exchange, and compliance arrangements to settle in crypto without triggering OFAC enforcement against their counterparties. It does not operate at scale for the global tanker fleet that needs to transact with the broader dollar-system financial infrastructure for everything from wages and bunkers to charter hire and registration.
The certificate-of-insurance question
A specific operational question Hormuz Safe will have to answer for the operator class is the certificate-of-insurance acceptance question. In normal commercial operation, a P&I certificate from an International Group member is accepted by port-state authorities, by counterparties, by classification societies, by charterers, and by lenders as evidence of lawful cover. A certificate from Hormuz Safe, on its present design, is not accepted by any of those parties as equivalent. Vessels operating under Hormuz Safe cover face the same downstream commercial questions that vessels operating without any cover face: whether their next port of call will admit them, whether their charterers will accept the cargo, whether their classification will be maintained, whether their lenders will continue to fund the vessel.
The “encrypted verification capability” the Iranian reporting cites is plausibly an attempt to address part of this question through cryptographic certificate-of-insurance issuance and verification. The technical problem is solvable; on-chain certificate issuance and verification is a routine application of public-key cryptography. The institutional problem is not solvable through cryptography alone: the certificate has to be accepted by the relying parties, and acceptance is a relationship question that the cryptographic infrastructure cannot, on its own, produce. The relying parties have to be persuaded that Hormuz Safe’s underwriting capacity, reinsurance arrangements, casualty-management infrastructure, and claims-paying record meet the standards they would otherwise apply to International Group P&I cover. The persuasion work is institutional, and it is at the same starting line as the PGSA’s institutional persuasion work analysed in the PGSA post.
What the underwriter market would do under a treaty-backed authority
The site’s reading of the underwriter market under a Suez/Panama-equivalent chokepoint authority configuration was set out in the 11 May war-risk underwriters post. The relevant point for Hormuz Safe is that the underwriter market does not, in normal operation at Suez and Panama, require a chokepoint-authority-issued insurance product. It requires a chokepoint authority that provides the institutional casualty-management infrastructure the standard commercial P&I cover relies on. Suez and Panama operate that infrastructure. The International Group P&I cover operates against it. Premiums are at the standard commercial level because the institutional baseline does the loss-control work.
A treaty-backed Hormuz authority on the Suez/Panama model would not, in this reading, need to offer its own insurance product. It would need to operate the institutional infrastructure that allows the existing International Group cover to be priced at standard commercial levels for Hormuz transits. The work the chokepoint authority does is institutional, not insurance: it provides the standing salvage-and-pilotage coordination, the published transit protocol, the dispute-resolution forum, the casualty-investigation procedure, and the relationship with the IMO, the IG, and the operator-side bodies that the underwriter market needs as the institutional baseline. Hormuz Safe, in this frame, is performing the wrong function. It is offering insurance the operator class does not need from this counterparty; what it should be offering, if the present institutional configuration were a working authority, is the institutional baseline that makes the existing International Group cover applicable.
What follows for the operator class
The operational consequence of Hormuz Safe’s launch is bounded. A subset of the operator class — vessels operating under the PGSA arrangement, in the China-, Malaysia-, Egypt-, South Korea-, and India-tolerant categories of the five-tier vetting system documented in the PGSA post — will use Hormuz Safe as the marginal cover that fills in some of the gap left by the International Group P&I withdrawal. The larger part of the operator class, with the majority of the global tonnage, will continue to wait outside the PGSA corridor for the institutional configuration that the International Group can accept as the operating baseline for standard commercial cover. The bifurcation analysed in the PGSA post deepens, with two parallel insurance markets developing alongside the two parallel transit arrangements.
The institutional question the site has been carrying — what configuration would close the gap and produce a single working market for transit traffic at Hormuz on terms the global operator class can use — is not answered by Hormuz Safe any more than it is answered by the PGSA itself. The configuration that closes the gap is the treaty-backed authority on the Suez or Panama model, with a civilian administering body, a published equal-access tariff, dollar-denominated settlement, monthly statistical bulletins, and a recognised dispute-resolution forum, the structure that the comparison page walks through, with the tariff on the rates page and the per-transit pricing in the calculator. Hormuz Safe is the insurance side of the institutional configuration the site has been documenting Tehran constructing for two months. The site’s reading of the configuration’s structural limitations applies to the insurance leg as it does to the transit-fee leg.
Sources: Al Jazeera, “Iran plans to offer insurance for Hormuz transit: Will it work?” 18 May 2026; Claims Journal, “Iran Starts Bitcoin-Backed Ship Insurance for Hormuz Strait,” 19 May 2026; Fars News Agency reporting on the Hormuz Safe insurance product and crypto settlement design, 18-19 May 2026; Jerusalem Post, “Islamic regime launches Persian Gulf Strait Authority, ships reportedly start paying tolls,” May 2026; World Economic Forum, “What stopping war-risk insurance in the Strait of Hormuz tells us,” April 2026; Khaleej Times, “Strait of Hormuz reopening won’t mean cheaper shipping as insurance premiums surge”; this site’s prior analyses on the cost stack (23 April), the UNCLOS vacuum (24 April), the Tether stablecoin settlement post (25 April), the ICS statement (25 April), the war-risk underwriters post (11 May), the China Blocking Rules post (11 May), and the PGSA on the Suez/Panama yardstick (19 May).