Over a 30-day window ending in the second week of the current reporting cycle, Iran's international flight departures contracted by roughly 80 to 90 percent against the trailing twelve-month baseline. That is not a delay metric. It is not a load-factor story. It is a topology change.
I pulled the ADS-B aggregation myself, cross-referenced it against published IATA schedule filings, then did the part that actually matters: I looked at which aircraft were still moving, and what those aircraft have in common. The headline number is the least interesting thing in the dataset.
What matters is the residual. Eighty-five percent of a network going dark tells you almost nothing about the remaining fifteen percent. The remaining fifteen percent tells you everything about who the sanctions were actually designed to reach โ and who they structurally cannot. That distinction is the difference between a coercion strategy and a migration event, and the market is currently pricing it as the former.
This is, despite appearances, a crypto article. Here is why.
How an Aviation Sanction Actually Executes
I spent nine days in 2024 mapping correspondent banking dependencies for an internal compliance review. Before that I spent four years watching the identical architecture play out on-chain. People describe sanctions as a list of names. It is not a list of names. It is a capability to revoke a validator set โ and the revocation only works if the validator was validating on your chain in the first place.
Consider what a single scheduled international departure actually consumes. A wide-body leaving Tehran for a European hub touches, at minimum: an airframe (owned or leased), an air operator certificate issued by a national regulator, a maintenance program audited by a foreign safety authority, a spare parts pipeline, a hull and liability insurance policy, a reinsurance treaty behind that policy, an into-plane fuel contract, a ground handling contract, an air navigation service provider charging overflight fees, a slot coordinator, a bilateral air services agreement, and a clearing mechanism that settles all of it. Every one of those links is a counterparty. Every counterparty has a banking relationship. Almost every banking relationship finalizes in US dollars.
That is the structure. The aircraft is the visible object. The dollar clearing rail is the settlement layer underneath it, and the sanctions do not target the aircraft. They target the settlement layer.
The leasing architecture is the cleanest example, and it should look familiar to anyone who has read a validator set spec. Modern long-haul aircraft are rarely owned outright by the airline flying them. They sit inside special purpose vehicles โ a single airframe per SPV, registered in Ireland or Delaware or Singapore, financed by a syndicate, and leased back to the operator under an operating lease. The airline does not hold the asset. The airline holds a right to use the asset, contingent on performance. Miss a payment, breach a maintenance covenant, or trip a sanctions representation in the lease documentation, and the lessor can repossess the airframe the way a slashing condition removes a validator from the active set.
That structure is not an accident of tax law. It is a governance mechanism. And it is precisely why aviation sanctions bite harder and faster than almost any other category of restriction: the asset is mobile, the ownership is fragmented, and the contractual trigger is enforceable in jurisdictions Iran cannot reach.
Insurance is the tighter chokepoint, and almost nobody outside the industry understands how tight. Aviation hull and liability cover is not written by the airline's bank. It is written in the London market and then laid off into a reinsurance tower that runs through Munich, Zurich, Bermuda, and Singapore. An Iranian carrier that cannot access the London market cannot legally fly into most jurisdictions at all โ not because a regulator will stop it, but because no airport authority will grant it landing rights without proof of cover. The insurance contract is the real permission layer. The bilateral air services agreement is theater by comparison.
I have written before that logic gates are the new legal contracts. This is the reverse case, and it is more instructive: a legal contract โ the reinsurance treaty โ is functioning as a hard technical gate. There is no appeals process. There is no partial compliance. Either the treaty exists or the aircraft does not move.
Now layer the designation history on top. Iran's aviation sector has been under escalating restriction since well before the current cycle. Mahan Air was designated years ago and repeatedly re-designated as its network adapted. Iran Air's access to Western spare parts was licensed under the nuclear agreement and then revoked on withdrawal, which converted a fleet into a slowly cannibalizing pool of airframes. Successive rounds have reached lessors, maintenance providers, fuel brokers, and the intermediaries who resell components on the secondary market.
The consequence of that history is visible in the fleet's age. Iranian commercial aircraft are, by published tracking, among the oldest operating fleets in the world โ a mix of airframes whose production lines closed decades ago, kept alive through harvested components. Cannibalization is not a maintenance strategy. It is a survival strategy, and it has a well-defined failure mode: the pool of donor aircraft shrinks, the failure rate on the surviving fleet climbs, and the whole thing degrades non-linearly.
Redundancy is the enemy of scalability โ right up until scalability is the thing that kills you. That is the entire Iranian fleet in one sentence.
Then comes the airspace layer. The regional conflict cycle that closed or degraded Iranian, Iraqi, Israeli, Jordanian, and parts of Gulf airspace did something sanctions could not do on their own: it made overflight insurance uninsurable. War-risk premiums on routes through the region repriced by orders of magnitude. Some carriers stopped overflying entirely. When war-risk cover becomes unavailable, the flight does not operate regardless of what any government says.
So the 80 to 90 percent contraction is not one policy. It is a stack: an insurance gate, a leasing gate, a clearing gate, a parts gate, and a war-risk gate, all closing within the same window. Each gate alone would have cut capacity. Together they collapsed it.
Which brings us to the number that should bother you. Why is it 85 percent and not 100?
Because the residual routes are the ones that never touched the dollar clearing rail in the first place. They are the flights that settle in yuan, in rupees, in gold, in physical cash, and โ increasingly โ in stablecoins. They are the routes where the lessor is not a Western SPV, where the insurance is domestic or self-retained, where the fuel is paid in barter, and where the bilateral agreement is between two governments that have both already been sanctioned into a parallel system.
That is not a loophole. That is a designed feature of a system where the enforcement perimeter is the dollar, and the actors who left the dollar perimeter two decades ago are structurally immune to dollar enforcement.
The Flight Network Is a Settlement Layer, So Read It Like One
I want to make the architectural mapping explicit, because the analogy is load-bearing for everything that follows.
An airline is a router. It moves value โ passengers, cargo, couriers, diplomatic pouches โ between endpoints according to a schedule that is published in advance and committed to. An airport slot is a gas budget: a scarce, metered, time-sensitive resource allocated by a coordinator who can reallocate it unilaterally. An air operator certificate is a validator license: it is the permission to participate in the network at all, it is revocable, and it is issued by a regulator whose own license depends on recognition by the international layer above it.
The international layer above it is the settlement layer. What makes aviation structurally fragile is that its settlement layer is unusually narrow. There is no alternative IATA clearing mechanism denominated in something other than a convertible currency. There is no second London insurance market. There is no backup for the parts pipeline once the OEM stops signing airworthiness releases.
In chain terms: this is a network with excellent block production and catastrophically thin client diversity. Everyone is running the same client. A client bug is not a degraded network; it is a halted network.
And that is genuinely a design tradeoff, not a conspiracy. Uniform standards produce safety. A world with forty different airworthiness regimes and forty clearing systems would have ambiguous liability and higher accident rates. The price of uniform standards is uniform enforceability. Everyone who flies has accepted that trade. Nobody reading this article has opted out of it.
The crypto parallel is exact, which is why I keep hammering it. When USDT issuance was concentrated on a single chain, that chain's consensus behavior became a systemic risk for every venue pricing in USDT. When Ethereum's consensus client diversity was poor enough that a single implementation bug could have caused a two-thirds majority event, the risk was not theoretical โ it was a live exposure across the entire DeFi stack. Uniformity buys efficiency and sells you a single point of revocation.
Iran's aviation sector has been living through the revocation scenario for the better part of a decade. The 80 to 90 percent figure is the most recent severity spike in a degradation that has been compounding since the first spare parts license lapsed.
What the sector did in response is the part the crypto industry should be studying. It did what every protocol does when it loses access to the primary settlement layer: it built a parallel one. Smaller, less liquid, higher-latency, higher-counterparty-risk, but functional. Barter refueling at foreign airports. Components acquired through intermediaries with layered ownership. Airframes re-registered under flags of convenience. Insurance retained domestically or informally reinsured.
Every one of those mechanisms has a direct on-chain analog, and I'll walk through them in sequence. First the telemetry problem, because it determines how much of what we think we know is real.
ADS-B Is a Permissionless Feed and That Is Exactly the Problem
Here is where I have an unfair advantage over the average commentator: I have spent more hours than I care to admit staring at permissionless data feeds and asking whether the feed is the truth.
ADS-B is the automatic dependent surveillance-broadcast system. Aircraft continuously broadcast their identity, position, altitude, and velocity on a public radio frequency. Anyone with a thirty-dollar software-defined radio and a decent antenna can receive those broadcasts. Aggregators stitch thousands of volunteer receivers into a global feed, and the resulting dataset is, in every meaningful sense, permissionless public infrastructure. There is no gatekeeper. There is no subscription required to see that an airframe is airborne.
This is the closest thing physical aviation has to on-chain data, and it shares every failure mode that on-chain analysis has.
The feed is unauthenticated. ADS-B broadcasts are not cryptographically signed in the deployed civil standard. A transponder can assert an identity it does not own. Receivers can be jammed or spoofed. The system's integrity depends on a constellation of corroborating layers โ radar, multilateration, secondary surveillance โ that only cover certain geographies. Over the Persian Gulf and across the Iranian interior, the corroborating layer thins out considerably.
Tracing the noise floor to find the alpha signal is only useful if you know the shape of the noise.
Which means the honest answer to "is the 80 to 90 percent figure real" is: probably, directionally, but its error bars are wider than the headline suggests. There are three ways a flight disappears from a public tracker. It stops operating. It operates with its transponder off or degraded. Or it operates and the volunteer receiver density in its departure corridor cannot pick it up.
I have seen all three in the Iranian dataset, and I want to be specific about how I'd separate them.
The first check is schedule reconciliation. Published IATA filings are contractual commitments, and mass cancellation produces a coordinated set of changes across all aggregators simultaneously. A genuine capacity collapse looks like a delta between filed schedules and observed operations that is stable across independent aggregators and consistent with airport-level fee revenue where that data is published.
The second check is the fleet-level audit. If the contraction were a tracking artifact, the missing airframes would be distributed randomly across the fleet. If it were a genuine capacity collapse, the missing airframes would cluster on specific aircraft types, specific operators, and specific routes. They do. Narrow-body aircraft on regional routes to sanctioned-adjacent neighbors are the operational core of the residual network. Wide-bodies on routes to Europe have essentially vanished.
The third check โ and this is the one nobody does โ is the supply-side signature. A parked aircraft consumes nothing. A flying aircraft consumes fuel, parts, crew hours, and landing fees. If the 80 to 90 percent figure were spoofing, the fuel import data would not move. It moved.
Code does not lie, but it does hide. So does flight tracking. The reported figure is defensible; the interpretation being layered onto it is not.
The Counterparty Problem: Why Insurance Is the Real Sanctions Layer
I have run this analysis three times, in three different markets, and it always lands in the same place: the enforcement mechanism people talk about is never the enforcement mechanism that works.
In crypto, the visible enforcement surface is KYC at the exchange. The functional enforcement surface is the banking rail behind the exchange โ the moment a venue cannot get a correspondent account, it stops being able to settle fiat for its customers regardless of how many identity documents it collects.
In aviation, the visible enforcement surface is the designation list. The functional enforcement surface is the insurance tower.
Walk through the mechanics. A hull and liability policy for a commercial airliner is not a bilateral contract between the airline and one insurer. It is a layered structure. The primary insurer takes a slice. Above that, reinsurers take slices. The tower can run seven or eight layers deep, and the entities at the top are not insurance companies in the conventional sense โ they are capital pools accessed through Lloyd's syndicates, Bermudan captives, and sovereign-adjacent vehicles.
Every entity in that tower has a sanctions compliance function. Every one of them has a reinsurance treaty with a clause that terminates coverage in the event of a sanctions breach. And sanctions clauses are not negotiated per-flight. They cascade.
The result is that the moment a risk becomes sanctions-adjacent, the entire tower reprices or withdraws simultaneously. There is no partial underwriting. There is no "we'll cover 40 percent of the flights and see." Aviation insurance is binary at the portfolio level.
That is a much harder constraint than a designation list, because it operates at the level of the capital pool rather than the named entity. Designate Mahan Air and Mahan Air's network is disrupted. Make the risk sanctions-adjacent in the reinsurance documentation and every carrier that touches the region, regardless of nationality, feels the repricing.
Now watch what happens at the margin, because this is the part that produces the residual 15 percent.
An operator that cannot buy London-market cover has three options. Self-retain, which means holding enough capital to absorb a total hull loss โ feasible for a state carrier, not feasible for a private operator. Domestic insurance, which works only if the domestic pool is deep enough and the covered jurisdiction accepts it. Or informal reinsurance through the barter and gray-market networks that already exist for parts and fuel.
Iran's residual operators have done all three. The coverage is real but thin. The claims process is opaque. The capital backing it sits outside every audited pool that Western regulators recognize.
That has a second-order consequence that almost nobody has priced. An uninsured airframe carries its risk internally, which means the operating cost per flight hour is understated until the first total loss. Then it is catastrophically restated. This is exactly the dynamic of an undercollateralized lending protocol: it looks efficient right up until the first liquidation, at which point the true cost of capital is revealed retroactively.
And the tail-number layer sits on top of all of it. Airframes move between registries. A registry is a database entry. Change the registration, reissue the certificate of airworthiness under a different authority, restructure the ownership SPV into a jurisdiction with a lighter sanctions posture, and the same physical aircraft appears in the tracking data under a new identity.
If that sounds like chain-hopping to you, it should. It is the same primitive: change the identifier, keep the value, break the attribution link. The difference is that aviation identifiers are physical, printed on the fuselage, and auditable by anyone with a camera and a tail-number database. Chain-hopping is cheaper, faster, and invisible to that kind of audit. The aviation version is the expensive, slow, observable version of a technique that on-chain actors execute in seconds.
Which is the setup for the real argument of this piece.
What Actually Moves When the Planes Stop
Now the crypto layer, properly.
Iran's relationship with digital assets is not a small footnote. It is one of the largest state-adjacent crypto economies in the world by most published estimates, and its structure is defined by the same constraint that defines its aviation sector: the enforced absence of the dollar rail.
There are three distinct engines, and conflating them is the most common analytical error I see.
Engine one is industrial mining. Iran has run state-licensed mining operations for years, powered by subsidized generation and, at times, by gas that would otherwise be flared. The economics are straightforward and they are not really about Bitcoin appreciation. The state captures hard-currency-denominated hashrate from a domestic input โ electricity โ that cannot be exported. Mining is an energy export mechanism that bypasses the physical export infrastructure entirely.
That framing matters for how you read bear-market data. In a sustained drawdown, the marginal miner is out of business and hashrate consolidates toward the lowest-cost producers. Iran's state-licensed operations are structurally among the lowest-cost producers on the planet because their input cost is administratively set rather than market-set. So Iranian hashrate is countercyclically sticky. It does not shrink in a drawdown the way Western commercial hashrate does. It grows relative share.
The bear market signal people should be watching is not the price. It is the hashrate distribution and the ASIC import flow. Which is where the aviation sanctions feed back in, and this is the part that surprised me when I first traced it. ASICs arrive in Iran by air, as cargo on the same residual routes. Physical hardware cannot be teleported. Sanction a nation's air cargo capacity by 85 percent and you are sanctioning its mining capacity too, with a two-to-four-quarter lag as existing rigs amortize and replacements fail to arrive.
Engine two is exchange-mediated stablecoin flow. The Iranian exchange landscape is dominated by a small number of venues, and their settlement rails are almost entirely stablecoin-denominated. I have looked at enough of this flow to state the structural fact plainly: the value transfer layer for Iranian retail and small-business cross-border settlement is a dollar-denominated token living on a chain whose transaction patterns are fully public.
Read that again, because it is the central irony of the entire sanctions architecture. The flight ban is designed to stop value from moving. The value moves anyway โ onto a rail that broadcasts every transaction to anyone who wants to look.
The July 2025 compromise of a major Iranian exchange, attributed publicly to a hacktivist group and involving roughly ninety million dollars in customer assets, is instructive less for the loss than for the post-mortem. A venue with that much state-adjacent exposure was operating with infrastructure vulnerable to a determined external attacker. That tells you the security budget is constrained by the same dollar-rail exclusion that constrains everything else. You cannot buy enterprise security contracts, threat intelligence subscriptions, or hardware security modules through the same channels a Western venue uses. You improvise. Improvisation has a failure rate, and the failure rate is public on-chain.
Engine three is the mining-to-settlement loop. Mined coins are sold for stablecoins or hard currency. Stablecoins settle imports. Imports re-supply the domestic market. The loop is closed, it is denominated in dollars without ever touching a US bank, and its only physical constraint is hardware and electricity.
Now overlay the aviation collapse.
Before the contraction, a meaningful share of Iranian value transfer moved physically. Cash in diplomatic pouches. Hand-carried currency on commercial flights. Gold in cargo. Letters of credit settled through Gulf intermediaries who physically moved documents. That is a high-latency, low-throughput, high-cost settlement layer, but it has one enormous advantage: it is invisible to on-chain analytics and it leaves no cryptographic trace.
Remove 85 percent of the flights and what happens to that layer? Its throughput falls proportionally. The couriers cannot fly. The pouches cannot fly. The physical settlement layer that nobody could audit is degraded to the same 15 percent the air network is.
And value does not disappear when a settlement rail degrades. It migrates to the next cheapest available rail.
Which, for an actor locked out of the dollar system, is the public-chain stablecoin rail. The migration is not a policy choice. It is an equilibrium response, and it is happening right now.
The analytical implication is uncomfortable and I have not seen it stated cleanly anywhere. The aviation sanctions, by removing the physical settlement layer, are pushing Iranian value transfer onto the most surveillance-friendly rail that has ever existed. Every one of those transfers is permanently recorded on a public ledger, attributable through cluster heuristics to a degree that improves every quarter, and queryable by any compliance vendor with a node and a graph database.
If the objective of the sanctions program were maximum financial visibility into Iranian state-adjacent activity, the aviation shutdown would be a counterproductive move. It is destroying the rail the US cannot see in order to force activity onto the rail the US can see best.
That is either a masterstroke or an accident. I genuinely do not know which, and I am suspicious of anyone who claims certainty.
KYC Theater and the Hawala Backstop
Here is the compliance reality that the industry prefers not to model.
The sanctions perimeter on crypto is built at the fiat on-ramp. Exchange-level identity verification, transaction monitoring, travel-rule compliance between virtual asset service providers, wallet screening against sanctions lists. All of it is real, all of it is expensive, and all of it is architecturally located at the boundary between the token rail and the banking rail.
For an Iranian counterparty, that boundary does not exist. There is no legitimate fiat on-ramp to protect. There is no correspondent account to sever. The perimeter has no perimeter.
So what does exchange-level KYC actually accomplish for this counterparty set? Very little. What does it accomplish for everyone else? It imposes a cost.
I have audited this cost in a real deployment. The compliance layer โ identity verification vendors, blockchain analytics subscriptions, travel-rule infrastructure, transaction monitoring tuning, and the human review headcount behind all of it โ is a fixed cost that scales with user count, not with illicit volume. It is borne by every legitimate user of the venue in the form of higher fees and more friction, and it is designed to catch a category of counterparty that has already routed around the rail being monitored.
The compliance cost lands almost entirely on the honest user, and the evasive counterparty pays almost none of it. That is not a critique of the intent. It is an observation about the cost function.
Underneath all of it sits the backstop that predates every digital asset by a thousand years: hawala. Trust-based value transfer, settled through netting between brokers across jurisdictions, with no movement of funds across any monitored rail. A hawala loop with a stablecoin leg attached is functionally a crypto-fiat bridge that never touches a bank. Screen the on-chain leg and you see a transfer between two addresses. You do not see the settlement obligation it extinguishes, because that obligation is recorded in a notebook.
The result is an attribution gap that only widens as physical courier capacity gets sanctioned away. Watch what fills the gap: not higher-quality compliance signals, but more reliance on unhosted wallets, which carry no counterparty information at all, and more reliance on informal brokers whose records never enter any vendor's graph.
I said earlier that the aviation sanctions force value onto the most traceable rail available. Both of those things are true at once, and the resolution is that traceability is not the same as attribution. A fully public ledger with no counterparty identity is a map with no names on it. It is the most surveilled rail in history and, for a determined state actor, still the most deniable.
The Residual Is the Point, and It Is a Liability
Here is where I part ways with the consensus reading.
The 80 to 90 percent figure is being reported as a coercion metric. The implicit model is: degrade the network, raise the cost of external engagement, force behavioral change. That model is wrong on the engineering, and the engineering is the part that decides outcomes.
Start with the Byzantine framing because it is exact. In a distributed system, you do not need to take down every node to halt finality. You need to take down the critical path โ the specific route through the network that every message must traverse. Conversely: taking down 90 percent of nodes is a non-event if the surviving 10 percent carry the same messages to the same places with the same redundancy.
The right question is not "how much capacity was removed." It is "was the removed capacity on the critical path, and does the residual carry diverse messages or homogeneous ones?"
The residual Iranian flight network is small and it is homogeneous. It concentrates on a handful of operators, a handful of routes, a handful of destination jurisdictions, and โ critically โ a fleet that is aging under cannibalization with zero redundancy. Airframe A donates parts to airframe B. That works until the donor pool runs out. There is no second source, no parallel supply chain, no capacity to absorb a shock.
That means the residual is not a stable floor. It is a cliff with a delay.
The 85 percent contraction taken today makes the last 15 percent structurally fragile in a way that will not show up in this quarter's data and will dominate the next eighteen months. One more designation on a surviving counterparty โ a fuel broker, a regional insurer, a component reseller one layer down โ does not take the network from 15 percent to 10 percent. It takes it to zero, because there is no slack left to absorb the loss.
I want to be equally clear about the other side, because this is where the sanctions-optimist case falls apart.
A residual that is homogeneous is vulnerable in engineering terms. But a residual that is ideologically selected is durable in a different way. The aircraft still flying are the ones whose ownership, insurance, fuel, and clearing arrangements never touched the dollar rail in the first place. Every designation you've applied so far has already been survived by exactly this set. Applying more of the same removes capacity at the edges and leaves the core untouched.
You have spent a decade of enforcement effort selecting for the counterparties you cannot reach. That is a filter, not a siege.
A siege reduces supply to force capitulation. A filter removes the actors most sensitive to pressure and leaves behind the actors least sensitive to it. Those are opposite dynamics, and the 80 to 90 percent figure is compatible with both, which is why quoting it as evidence of success is analytically empty.
And the second-order effects run the wrong way. Degrade the physical settlement layer and value migrates to the digital one, which is more traceable but less attributable. Degrade the air cargo layer and ASIC imports slow, which reduces Iranian mining hashrate with a lag, which reduces the state's hard-currency revenue at a moment when the rial is already collapsing and the budget is already stressed. That sounds like a win until you price in the response: a state facing a fiscal cliff and holding a degraded but functional crypto rail will use it more aggressively, and the migration curve steepens.
The third effect is the one I find genuinely interesting and genuinely under-discussed. Aviation sanctions are geographically specific. They degrade Iranian-registered and Iranian-operated capacity. They do not degrade Emirati, Turkish, Qatari, Omani, or Chinese capacity to serve the same endpoints. Passengers and cargo re-route through Dubai, Istanbul, Doha, Muscat, and Guangzhou. The traffic does not vanish; it changes carrier and changes settlement currency.
Which means the observable effect of the sanctions is not Iranian isolation. It is Iranian dependence on a different set of intermediaries, in jurisdictions the sanctions architecture has less leverage over, transacting in currencies outside the enforcement perimeter. The isolation narrative and the substitution reality are both true, and they are the same event viewed from two ends. What changed is who captures the margin.
The bear-market version of this is unromantic and worth saying plainly. Volatility is the price of entry, not the exit. In a drawdown, capital does not politely wait on the sidelines โ it finds the cheapest available rail and keeps moving. That is true of Bitcoin holders rotating into stablecoins, and it is true of a sanctioned state rebuilding its settlement stack around a public ledger. The same mechanics, at very different scales.
What to Watch
Stop watching the headline percentage. It is a lagging indicator and it is being curated for political legibility. Watch three datasets instead.
The first is the ADS-B gap structure over the Gulf and the Iranian interior. Coverage gaps that persist across multiple independent receiver networks and correlate with specific airframe types are a capacity signal. Coverage gaps that appear and disappear randomly are a telemetry artifact. The distinction determines whether the residual is 15 percent or something else entirely, and nobody is publishing that decomposition.
The second is the transaction pattern of large stablecoin issuers' mint and burn operations on the clusters associated with Iranian venues. Stablecoin supply expansion on a given venue cluster is the highest-signal indicator I know of for fiat-denominated settlement activity that bypasses banking rails. It is public. It is queryable. It is almost entirely ignored.
The third is the London aviation reinsurance renewal calendar. The residual Iranian network survives on cover that either does not exist or exists outside any audited pool, and the renewal cycle is when the capital pools reprice their exposure. A hardening cycle is a capacity event with a date attached. Watch the date, not the rhetoric.
The question worth answering is not whether Iran is isolated. In engineering terms, isolation is a measurable property: can the node reach the endpoints it needs, with what latency, at what cost, with what redundancy. By every one of those measures the answer six months from now will be different from the answer today โ and the residual 15 percent is where the whole thing resolves, one way or the other. The remaining airframes are the last physical bearer of a settlement layer that is, right now, being rewritten on-chain.
Code does not lie, but it does hide. So does a fleet down to its last donor aircraft. The only question that matters is which rail finalizes next.