The numbers are stark. On a single night, July 12, 2025, US Central Command reported striking 140 Iranian targets. The range expanded from the Halmal Strait coastline deep into Iranian territory. The frequency accelerated: 80 targets on the 8th, 90 on the 9th, then this jump. Markets trembled. Oil futures spiked. Yet, sitting here in Prague, monitoring the news feed with my usual blend of cryptography and geopolitics, one question kept gnawing at me: Who actually verifies these numbers? Not that I doubt the military’s reports—I’ve no reason to. But in a world where trust in institutions is at an all-time low, and where I’ve spent the last decade teaching developers that code, not authority, should be the source of truth, the disconnect is glaring. We have a $3 trillion crypto market that runs on transparent ledgers, yet the most consequential events of our time—acts of war—still rely on press releases and satellite imagery that can be selectively cropped.
Build for humans, not just nodes. That phrase isn't just a slogan; it's a design principle. And right now, our systems for verifying conflict data are built for state actors, not for the global public. Let me break down why this matters and what blockchain technology could actually do to change it—if we have the courage to build differently.
Context: The Verification Gap
The issue is not with the US military's integrity. It's with the systemic opacity that all nations maintain during armed conflict. When I advised the EU regulatory task force on decentralized governance earlier this year, we spent weeks debating how to create transparent dispute resolution mechanisms for smart contracts. The goal was to ensure that when a DAO votes to rebalance a treasury, every step is auditable by anyone.
Now apply that same logic to conflict reporting. A nation-state announces it struck 140 targets. Independent journalists can't fly over the region. Satellite imagery is expensive and often classified. The public—and indeed other governments—must either trust the announcement or rely on adversary propaganda. This is a trust-based system in an age when trust in institutions is the scarcest resource. It is, ironically, the same problem that Bitcoin was invented to solve: how to have a single source of truth without a central authority.
Core: The Technical Case for On-Chain Conflict Verification
I want to propose a practical architecture, grounded in my experience running the Prague Decentralized workshops. Imagine a conflict zone where specific infrastructure—military radars, fuel depots, ammunition storage—is registered on a public, permissionless blockchain before any hostilities. Not as a static list, but as a cryptographic commitment.
Here's how it works:
- Pre-registration of assets: During peacetime, nations (or ideally a neutral third party like the UN) register the geolocation and type of critical military infrastructure using a zero-knowledge (ZK) proof. The proof is stored on-chain, but the exact coordinates remain encrypted until a predetermined triggering event—like a verified act of aggression.
- Drone or satellite validation: After a strike, independent verification entities (consortiums of universities, NGOs, or blockchain-based oracle networks) analyze public satellite imagery. They generate a cryptographic attestation of which registered coordinates now show strike damage. This attestation is aggregated with time-stamped sensor data from IoT devices (e.g., seismic sensors) deployed in the region.
- Resulting proof: A smart contract can then compute a mathematical proof that, say, 90% of the claimed targets were indeed destroyed at specific coordinates, without revealing the precise locations publicly (to protect operational security). Anyone can verify this proof without trusting any single actor.
This isn't science fiction. In 2021, during the NFT frenzy, I curated a digital gallery in Prague that used low-energy chains for provenance. We minted digital art with cryptographic signatures from the creators. Buyers could instantly verify authenticity without calling a gallery. The same principle applies to conflict verification.
Education is the ultimate yield. But right now, the infrastructure for education doesn't exist. The problem is not technical feasibility; it's political will. Nations benefit from ambiguity. They can claim success without independent verification, and they can claim caution when overstating losses. A transparent system would constrain that flexibility. That's precisely why we need it.
Contrarian: The Blind Spots of Decentralized Verification
Let me be contrarian here, because I've seen enough blockchain projects fail due to naive trust in technology. A fully on-chain verification system for military strikes has three critical blind spots:
- Data input integrity: The system is only as good as the initial registration. If a nation registers fake assets (empty warehouses), strikes them, and claims 140 hits, the proof will be mathematically correct but factually false. Garbage in, garbage out, even in a smart contract.
- Privacy versus transparency: Military operations require secrecy. ZK proofs can hide coordinates, but any leak during the encryption phase could reveal vulnerable positions. A breach would be devastating. The trade-off between transparency for the public and security for the troops is real.
- Adoption asymmetry: If only one side adopts this system, it becomes a unilateral vulnerability. The adversary could register nothing and still launch strikes, while the transparent side reveals its own infrastructure. A prisoner's dilemma emerges.
I experienced this trade-off firsthand during the bear market of 2022. I initiated a peer-support network called "Reclaim" for burned-out developers. We wanted to track contributions transparently, but many participants feared that on-chain visibility would expose their financial struggles. We settled on a hybrid model: private chat logs with a public audit trail of mental health resources used. It wasn't perfect, but it was better than nothing. The same compromise is needed here.
Takeaway: Build for Humans, Not Just Nodes
The US military's 140-target strike is a watershed moment, not because of its scale but because of the verification void it exposes. We have the tools to create a verifiable, transparent record of conflict that no single nation can control. But we must resist the temptation to treat blockchain as a silver bullet. It is a social technology that requires trust in the verifiers, the input providers, and the governance of the system itself.
Build for humans, not just nodes. That means designing verification systems that respect the legitimate need for operational security while empowering the global public to hold actors accountable. It means creating educational curricula—like the one I started in Prague—that teach both the technical and ethical dimensions of decentralized verification. It means acknowledging that the ultimate source of truth is not the code, but the community that maintains it.
The market is euphoric. Oil is up. Gold is up. But the real opportunity lies in rethinking how we verify power itself. Are we going to continue trusting press releases, or are we ready to trust a protocol? The answer will define not just the future of conflict, but the future of trust.
Alexander Harris, Decentralized Protocol PM, Prague