You are mistaken if you believe Bitcoin is state-resistant. No state has ever needed to attack Bitcoin itself. A state only needs to attack the three dependencies Bitcoin cannot negotiate away: the grid that powers its miners, the cables that connect its nodes, and the banks that convert its coins into rent money. Over the past seven days, while security analysts parsed an unusually detailed war doctrine out of Tehran, the Bitcoin mempool processed roughly 687,000 transactions and did not pause once. That is the headline number, and it is almost entirely meaningless.
On Tuesday, the Islamic Republic's semi-official Tasnim news agency published what it called a strategic response plan codifying the country's retaliation posture toward the United States and Israel. As reported by Crypto Briefing, the plan explicitly designates civilian and economic infrastructure — including energy export terminals, power grids, data transmission infrastructure, and financial systems — as target classes. This is not a strike timetable; it is a policy declaration about what kinds of systems will be treated as military objects in the next phase of the conflict.
For Western analysts, the document is a familiar inflection point in a war that already includes direct missile exchanges, strikes on nuclear research facilities, and cyber operations against critical systems. For anyone who earns a living assessing the resilience of blockchain networks, the Tasnim text is a formal declaration that the physical substrate of the crypto industry is a military target. The physical substrate was always the part the industry refused to audit.
This will get worse before markets price it correctly.
Context: A state that already runs on crypto
To understand why an Iranian military doctrine matters to a crypto reader, the history must be stated without narrative polish. Iran legalized commercial Bitcoin mining in 2019 — not because Tehran believes in digital sovereignty, but because the country produces more natural gas than it can consume, the electricity is heavily subsidized, and the global banking system is closed to Iranian counterparties. Mining converts stranded energy into an exportable, dollar-denominated asset that requires no correspondent bank. At its peak in 2021, the Cambridge Centre for Alternative Finance estimated that Iran accounted for roughly 4.5 per cent of global hashrate. The US Treasury's Office of Foreign Assets Control designated Iranian mining operations in April 2024, describing the sector as a channel for sanctioned revenue. By 2025, after electricity shortages, a winter crackdown by the state utility Tavanir, and successive sanctions rounds, Iran's share had fallen to the low single digits. The sector never died. It could not die. It is state infrastructure.
The conflict timeline matters because it frames the doctrine. In April 2024, Iran launched its first direct drones-and-missiles attack on Israel. In October 2024, Iran fired roughly 180 ballistic missiles at Israeli military and intelligence sites; Israel responded with calibrated strikes on Iranian air defenses. In June 2025, Israel executed "Rising Lion," a multi-day campaign against Iran's nuclear research infrastructure in Natanz and Isfahan. Each round escalated the target lists. The Tasnim response plan is the first time the doctrine has been published as a whole — and it explicitly moves beyond military installations to the civilian and economic systems that underpin a modern state's financial sector.
Crypto Briefing's report frames the response plan as a new source of complexity for regional conflict, one that widens the battlefield to civilian and economic systems. That framing deserves a hard look. The reason infrastructure targeting is a complexity amplifier rather than a simple escalation is that it converts every energy consumer, every cable operator, and every data center landlord into a participant in the conflict. When the response plan names data transmission infrastructure, it is naming data centers in Manama, undersea landing stations in Marseille, and cloud regions in Virginia. The doctrine's boundaries are not national; they are functional. Functionally, crypto runs on the same wires as everything else.
Why does this belong in a crypto publication? Because the industry's founding narrative — that blocks are sovereign and code is law — has never accounted for the physical reality of the networks it runs on. Every chain is a tenant. The lease is written in electricity prices, cable routes, and the tolerance of a cloud provider. Tasnim has placed that lease under explicit threat.
Core: A systematic teardown of crypto's physical dependencies
1. The physical layer was always the attack surface
Let me state the dependency chain with the precision it deserves. Bitcoin's consensus requires two continuous inputs: electricity and internet connectivity. No property of the blockchain supplies either. Both are delivered by physical infrastructure — power plants, transformers, submarine cables, landing stations — built decades before the first block and operated by nation-states, municipalities, and utilities that owe no loyalty to a decentralized network.
The Tasnim categories track that dependency chain with uncomfortable accuracy. Energy export terminals are target class because they generate foreign currency. Power grids are target class because they generate everything else. Data transmission infrastructure is target class because the modern economy and the modern military run on the same fiber. The authors of the Iranian doctrine do not need to understand Merkle trees to understand what keeps Western finance alive. They need to read a cable map.
The industry has been shown this map before and chose not to look. In February 2024, when Houthi actions in the Red Sea damaged submarine cables serving the Europe-India Gateway and TGN Gulf routes, Middle Eastern exchanges reported elevated latency and adjusted routing. The event barely registered in a market obsessed with spot ETF flows. Later that year, Iran's state utility Tavanir cut power to licensed mining facilities during summer peak demand — not war, just seasonal load. The network absorbed the loss. But observe what kind of resilience that was: Bitcoin was resilient to the loss of Iranian miners because Iranian miners could be replaced by American, Kazakh, and Ethiopian hashrate. That is geographic redundancy. It is not invulnerability.
Look at the cable map as a security professional would. The Red Sea corridor carries a substantial share of Europe-Asia traffic across the SEA-ME-WE series and the Asia-Africa-Europe 1 route. Those cables pass within range of multiple states and non-state actors, and the Houthi campaign of 2023-2024 proved that a networked adversary can degrade them with relatively low-tech methods. The February 2024 cable cuts near Bab el-Mandeb were, by most accounts, inadvertent — anchors dragging under pressure from rerouted traffic. Now consider deliberate targeting by a state with a published doctrine. A state actor does not need to chart the cables; landing stations are on every map. Sever two landing stations serving the Gulf and every financial exchange in the region reroutes through high-latency paths. The blockchain will not stop. The arbitrage desks will feel it. The difference between a network being functional and being efficient is measured in milliseconds; milliseconds are priced in basis points; and basis points are the difference between survival and capitulation for leveraged infrastructure in a bear market.
Now invert the geography. More than half of global hashrate sits in the United States. American electricity infrastructure is aging, fragmented, and — per the Tasnim document — officially designated as target class. A state-level adversary does not need to take down the entire US grid to create a genuine consensus crisis. A prolonged regional outage affecting fifteen per cent of the network is enough to stress pool concentration, distort the difficulty adjustment cycle, and tip marginal operators into capitulation. The network survives. The operators do not. Survival was never the relevant question. Cost has always been the relevant question, and cost is set by the grid.
Based on my audit experience, I can predict the industry's response to this realization with confidence. It will tokenize the risk and rebrand it as resilience. There will be "war-resistant infrastructure" projects, on-chain insurance pools, and a thousand blog posts asserting that decentralization saved the network. None of that will repair a severed cable. Code is not law, it is merely preference — and the preference written in the Tasnim doctrine is to attack the grid, not the gossip protocol.
2. Iran's miners are a state asset, not a freedom tool
The role of Iranian mining in this conflict deserves colder analysis than the industry has provided. Western coverage treated Iranian mining for years as a curiosity: cheap power, shadowy ASIC farms, miners in the desert. The actual model is more corporate and more cynical. Iran's licensed mining sector operates inside state-controlled free-trade zones, frequently under entities connected to the Islamic Revolutionary Guard Corps, buying electricity at subsidized rates that amount to an export subsidy. The mined output is sold for dollars on OTC desks in Dubai, Istanbul, and Moscow, and the proceeds flow back into Iran's import financing channels. The IMF and the US Treasury have both described this pipeline in public documents.
That changes the moral geometry of the "blockchain is freedom" myth. When Tasnim names American and Israeli infrastructure as legitimate targets, it speaks for a state whose own mining sector is wired into the same grid the doctrine is designed to protect. Individual liberty narratives are real for the Iranian citizen holding USDT to escape the collapse of the rial. They are irrelevant to a mining fleet whose revenue keeps the state's sanctioned trade machinery liquid.
Here is the data point the industry will not integrate: Iranian hashrate barely moved during the June 2025 "Rising Lion" strikes. Israeli aircraft were striking nuclear research facilities hours away, and the mining pools connected to Iranian territory kept hashing. The public explanation is that the strikes did not target power infrastructure serving mining zones. The structural explanation is more uncomfortable: the mining output is too strategically valuable to the state to leave unprotected. The continuity of Iranian mining during the conflict is not evidence of a neutral permissionless protocol. It is evidence of state protection for a state-owned export asset. The ledger remembers what the mempool forgets — and what the mempool forgot in June 2025 is that the most "censorship-resistant" mining jurisdiction in the Middle East is an explicit instrument of the state that just published a doctrine targeting foreign grids.
3. The bifurcated state: Bitcoin on the export side, a digital rial on the inside
Iran's relationship with crypto is a study in state-level preference, not ideology. On the export side, the state protects licensed Bitcoin mining because it earns hard currency without touching the SWIFT system. On the domestic side, the Central Bank of Iran has spent years piloting a digital rial — a permissioned CBDC — with trials in the Kish Island free-trade zone and other regulated spaces. The digital rial is not a response to Western innovation; it is a response to the failure of the banking system and the need for a monitorable domestic payment rail.
The state's position is precise: permissionless assets for earning dollars abroad, a permissioned rail for monitoring transactions at home. The crypto industry loves to cite the impossibility of stopping a peer-to-peer network. The state's answer is to not try. It converts the permissionless network into an export business and builds its own permissioned layer for the population. This bifurcation is the real doctrine that the Tasnim infrastructure plan serves. The response plan is not an attack on decentralized networks; it is a strategy to defend the state's own dual use of them. A reader who imagines Iran as an enemy of crypto is reading the wrong map. Iran is a competitor in the same export markets, with a clearer understanding of where the physical boundaries of digital money actually lie.
4. Stablecoins are the sanctions chokepoint
The layer that actually affects most portfolio allocations in a bear market is not Bitcoin mining; it is the dollar-pegged stablecoin complex. Capital rotates into USDT and USDC in downturns the way it historically rotated into Treasury bills. The flows are defensive, prudent, and structurally blind to their own dependencies.
Walk the chain forensically. Stablecoin issuance is collateralized by dollar reserves held in US banks, money markets, and Treasury instruments. That collateral gives the stablecoin its price, but the price is real only to the extent the holder can exit through a licensed exchange into a bank account. The licensed exchange sits on global banking rails — correspondent networks, settlement systems — which run on the exact infrastructure classes the response plan designates. Then there is the compliance layer. Tether has frozen hundreds of wallets at the request of Israeli authorities; Tether and Circle both maintain blacklist capabilities that shadow OFAC designations. For an Iranian user fleeing the rial, a USDT balance is not an escape from the state system. It is a dollar IOU issued by a private company whose sovereign is a New York compliance department.
That is the structural trap. A user who moves value out of a sanctioned currency and into a stablecoin has not left the infrastructure war. She has traded exposure to one state's payment system for exposure to another state's settlement layer, with a private issuer acting as the border guard. Code is not law, it is merely preference — and the controlling preference is written in a legal department's sanctions policy, not in a smart contract.
The enforcement pattern is already visible. The Treasury has made clear that it views stablecoin issuers as extensions of its sanctions apparatus; issuer freezing behavior around Israeli and Ukrainian requests is a matter of public record. Regulators in multiple jurisdictions are preparing market-structure bills that would formally bind stablecoin issuance to licensed, state-supervised custody. The interesting detail is not the freezing itself; it is the timing. The Tasnim doctrine names "financial systems" as a target class at the exact moment stablecoins are becoming the settlement layer of choice for sanctions-circumventing trade. The dollar peg is not a refuge from the conflict. It is the conflict's preferred ammunition. Both sides are loading the same weapon.
This is the third time in my career I have watched the industry mistake a permissions system for a freedom machine. In 2022, I modeled the UST seigniorage equation and concluded that the peg required infinite external liquidity; the collapse followed three weeks later. In 2026, I spent six months reverse-engineering an "AI-powered" proof-of-work oracle and demonstrated that 90 per cent of the computations were cached responses; the project had raised nine figures on the premise that the blockchain layer was doing verifiable work. The common thread is always the same: the industry monetizes the narrative of technological independence and leaves the dependencies undebuggable. Stablecoins are the largest undebugged dependency in the market today. The market treats them as cash. They are, in fact, a highly leveraged position on the continued functioning of the US financial infrastructure and the continued compliance cooperation of two private issuers.
5. The bear market reads geopolitical risk as volatility — that is the mistake
Over the past seven days, while security analysts parsed the Tasnim document for escalation timetables, crypto markets did what they do in a bear market: they shrugged. Order books thinned. Derivative funding hovered near zero. On-chain volume stayed muted. The measured response can be quantified. Bitcoin's 30-day realized volatility actually declined in the days following publication; options skew across Deribit flattened; basis on the major exchanges remained in the low single digits. The market's message is unambiguous: this document is priced as event risk — near-zero probability of immediate execution — rather than structural risk. That is exactly how the market priced the April 2024 drone attack until the missiles were already in the air.
The learned pattern is real. In April 2024, when Iran attacked Israel directly for the first time, Bitcoin fell roughly seven per cent within hours and recovered over the following week. In October 2024, Iran's ballistic missile barrage produced a sharp downside wick, a V-shaped recovery, and a collective sigh of relief. The market now treats state-on-state kinetic events as buy-the-dip liquidity events. The pattern is correct for the historical sample. It is catastrophically wrong for the current one. The prior events were kinetic but bounded — strikes on military installations and a small set of high-value military targets. The Tasnim response plan is not a strike list; it is a doctrine of portfolio construction at the national level. It converts civilian economic infrastructure — power grids, data transmission, financial systems — into standing target classes. The empirical sample contains no instances of that scenario executing. The market has learned to be calm in exactly the type of environment this doctrine is designed to break.
The bear market context changes the stakes. In a bull market, an infrastructure shock is absorbed by capital inflows; in a bear market, there is no inflow cushion. Projects with weak treasuries, concentrated operations teams, and single-region cloud dependencies will fail precisely in the scenario the doctrine describes. A chain whose validator set is concentrated in a region that loses power for a week will see finality stalled, bridge operators scrambling, and community blame aimed at protocol design rather than geographic concentration. The incident will be reported as a "network event." It will actually be a logistics event. The difference matters because the first framing invites a protocol fix; the second demands infrastructure relocation.
I have debugged the narrative instead of the contract enough times to recognize the coming pattern. In 2017, I delivered a reentrancy audit of a Sydney ICO's token distribution contract, documenting fourteen edge cases that could drain funds; the founders rejected the report because the market window mattered more than security. In 2019, I calculated that gas inefficiencies in Uniswap v1 liquidity pools were inflating swap costs by roughly forty per cent for small holders; the analysis was ignored because the community had moved to the liquidity incentive narrative. In 2022, I published the death-spiral math for UST three weeks early on a blog that generated almost no traffic. The pattern never changes. The measurable risk faces a narrative that refuses to incorporate it, and the narrative holds until the liquidity dries.
The illusion persists until the liquidity dries. An infrastructure war dries the liquidity of the physical systems first. The mempool will keep moving because the mempool is a gossip protocol and gossip is cheap. The liquidity that matters — converting a position into dollars, paying a validator bill, repatriating mining revenue — runs on grids, cables, and bank servers that are now explicitly target-classed. The market will treat the first grid outage as an anomaly. It will treat the second as a pattern. By the third, the survival of marginal protocols will already be decided.
6. A survival checklist for the infrastructure war
Instead of ending the core analysis with another prediction, here is a checklist for readers concerned with asset safety in a bear market with a physical attack surface. These are the questions I would ask before holding any position, based on a decade of audits and investigations.
First, map the grid. Where does the chain's security physically sit? If sixty per cent of a network's hashrate or staked value is concentrated in one country, a regional power outage is a consensus event, not a market event. Do the node geography analysis yourself from public data; ignore the "decentralized by design" marketing layer.
Second, map the validator stack. A large share of Ethereum validator infrastructure sits on three public cloud providers, with a single US-Eastern region carrying an outsized concentration. Cloud providers are not the risk; geographic concentration is the risk. A doctrine targeting data transmission infrastructure has a short list of preferred targets in the United States, and that Virginia corridor is near the top.
Third, map the exit ramp. Trace where your stablecoin redeems. If the issuer's compliance team can freeze your wallet at a regulator's request, the instrument is a permissions system wearing a monetary costume. Treat it accordingly.
Fourth, map the energy price. If a position depends on cheap Middle Eastern power for its economic viability — mining hashrate, certain DePIN networks, high-throughput chains — model what a prolonged conflict does to the cost base. Missiles do not need to hit a mining farm to kill its margin; they only need to hit the regional energy price.
Fifth, map the verification theater. Any protocol that claims to verify physical work — AI computation, energy production, sensor data — is only as trustworthy as the oracle layer that feeds it. I have spent six months proving that an "AI-verified" network was caching outputs; the same failure mode will appear in conflict zones where data feeds disappear. The oracle is the attack surface the industry keeps building over.
Sixth, read the adversary's doctrine. The Tasnim plan is public in translation and names system classes with a clarity that most crypto whitepapers lack. Treat it as documentation of the business environment, not as noise. The teams that relocate infrastructure, diversify fiat rails, and plan for grid segmentation will survive the next two years. The teams that continue to classify state infrastructure doctrine as "volatility" will not.
Contrarian: What the bulls got right
The infrastructure-war thesis has a genuine counterweight, and it deserves a fair statement. Bitcoin has now survived multiple direct exchanges between states with real kinetic capability. It survived April 14, 2024, October 1, 2024, and June 13, 2025, without a single block delay attributable to the conflict. Settlement continued because the power stayed on and the cables stayed up. That is a real property, not a fantasy. The honest bull case is not that blockchain cannot be stopped. It is that blockchain has a very high tolerance for geopolitical disruption, provided the grid endures. That tolerance has measurable value, and the market is correct to price some of it.
The second point the bulls own is the individual scale. When the Iranian rial collapsed into the hundred-thousands to the dollar, the non-bank market for USDT inside Iran kept functioning because it required only mobile phones and private trade networks. For the individual inside a sanctioned currency regime, crypto did exactly what its proponents claimed: it provided an exit without a border crossing. That functionality did not depend on Iranian state mining or on any doctrine. It depended on cheap gossip and a widely held dollar IOU. Narrow, but real.
The third point is structural. Difficulty adjustment is a shock absorber with no equivalent in traditional finance. When miners disconnect, the network reprices security downward until marginal operators return. When regions become hostile, capital relocates — the shift out of Kazakhstan after the 2022 state network disruptions and the current migration toward Ethiopia, Oman, and Latin America are evidence that the physical layer is diversifying. The migration is slow, capital-intensive, and geographically predictable. But it functions. The network is not static; it is a load-balancing system with a decade of data proving its transfer function.
And to be fair to the market, the current pricing is not irrational under one assumption: that the doctrine is coercive signaling rather than an operational plan. If Tasnim's text is designed to raise the costs of Israeli and American escalation without triggering a full economic-war response, then market indifference is correct. The problem is that a doctrine does not need to be executed to shape behavior. It shapes the behavior of insurance underwriters, cloud providers, and compliance officers first. Those actors are already repricing infrastructure risk in the physical world. The crypto market has not yet noticed.
The synthesis is uncomfortable. The bull case is true at the individual scale and true at the settlement scale, and almost irrelevant at the infrastructure-war scale. A state does not need to crack consensus to win a conflict. It needs to crack the plumbing around consensus: energy markets, dollar access, cable routes, and the compliance behavior of private issuers. None of that plumbing was built by the crypto industry, and none of it will be redesigned by the crypto industry within the horizon of this conflict. Truth is a derivative of transparent data — and the transparent data shows that the industry's physical dependencies remain nation-state-shaped. The blocks may be sovereign. The infrastructure is not.
Takeaway: Map the dependency, because the market won't
The Tasnim response plan is not a prediction of an imminent launch. It is a statement of policy priorities from a state that already uses crypto mining as an export tool and does not share the industry's belief in neutrality. The industry can respond in one of two ways: classify the doctrine as a volatility event and revert to the buy-the-dip reflex, or classify it as a structural forecast and audit the physical layer of every position held.
I know which one the market will choose. I have watched the industry refuse this lesson for a decade, through reentrancy exploits that were documented and ignored, through oracle frauds that were documented and ignored, through algorithmic stablecoin collapses that were documented and ignored. The ledger remembers what the mempool forgets — but the grid, once struck, remembers nothing. It simply goes dark. The question for 2026 is not whether Bitcoin survives an infrastructure war. It is whether your chain, your wallet, your stablecoin issuer, and your cloud provider survive the loss of their preferred region. Map the dependency. The market will not do it for you.