A Russian defense ministry claims have captured Kostiantynivka. Kyiv instantly denies losing control. Seven days later, no satellite imagery, no verified video, no independent confirmation. The graph of truth spikes on Telegram channels, but the soul of the battlefield remains quiet. This is not a military failure—it is an information infrastructure failure. And it is a problem that blockchain was built to solve.
When the graph spikes, the soul remains quiet. The contradiction between two opposing narratives, both lacking cryptographic proof, mirrors the core crisis of decentralized finance in 2021: everyone claims they have 100% uptime, but only an immutable ledger can prove it. I witnessed this firsthand during the Gitcoin Grants civic tech pivot in 2017. We used quadratic voting to allocate public goods funding, and the hardest part was not the math—it was verifying that votes came from real humans, not bots. We built a sybil-resistant system, but the military domain has no equivalent yet. The battle for a single town in Donetsk is a battle of records, and we are losing.
Context: The Information War on the Frontline and in the Boardroom
The Russia-Ukraine conflict is a proxy war not just of artillery but of narratives. Over the past year, I have seen how both sides use declaratory statements in the absence of verifiable data. The Kremlin broadcasts “progress” to maintain domestic morale; Kyiv denies losses to secure Western aid. This is the same pattern I observed during the Uniswap v2 liquidity mining crisis. Projects claimed astronomical TVL growth, but when incentives stopped, the real user base collapsed. The numbers were lies masked by economic incentives. Similarly, Kostiantynivka’s control status is a product of incentives—Russia needs to show it is winning; Ukraine needs to show it is holding. Neither has an incentive to publish verified coordinates.
Core: How Blockchain Can Build a Verifiable Truth Layer for Conflict Zones
Blockchain technology offers three specific tools that could replace the current information war with a verifiable truth layer: decentralized oracles for geospatial data, zero-knowledge proofs for location integrity, and immutable timestamps for chronology. Let me break down each with technical precision, based on my own audit experience of over 50 smart contracts in the Gitcoin days.
First, decentralized oracles like Chainlink or API3 can pull satellite imagery data from multiple sources (Maxar, Planet Labs) and deliver it on-chain. Currently, each side releases its own satellite images selectively. If both sides commit to publishing images to a smart contract that stores a hash of the image as a proof of existence, neither can later deny the pixel data. The key is that the oracle network must aggregate multiple independent sources—not just one feed controlled by a government. This is exactly how we built price feeds for DeFi: to prevent a single exchange from manipulating the market. Here, we prevent a single intelligence agency from manipulating the battlefield.
Second, zero-knowledge proofs can confirm that a specific location was under a specific party’s control without revealing troop movements. Imagine a soldier’s device generates a ZK-proof that they are at coordinate (48.5°N, 37.7°E) at timestamp t, and the proof is submitted to a public blockchain. The verifier (e.g., a neutral watchdog) can confirm the soldier was there without seeing the soldier’s full location history, and without the soldier risking operational security. This is analogous to how ZK rollups prove transaction validity without revealing the entire state. The proving cost is high—I have written about how ZK rollup proving costs are absurdly high unless gas returns to bull-market levels. But for critical conflict verification, a humanitarian organization could subsidize the proving cost. The alternative is endless argument over who controls a pile of rubble.
Third, immutable timestamps. On Ethereum, we can store the hash of a geospatial report or a video file as a calldata transaction. Once included, the time is forever fixed. Currently, when Russia says it captured Kostiantynivka on September 10, the claim is easily refuted by Ukraine claiming it happened a week later. But if the initial video file is hashed and submitted to the blockchain on September 10 at 14:00 UTC, anyone can later check that the hash matches the video. No one can retroactively claim the video was altered. This is not a hypothetical; it is already done for legal evidence through services like OpenTimestamps. The military domain has simply not adopted it.
Based on my experience as a technical advisor for the Bitcoin ETF regulatory bridge in 2025, I know that translating cryptographic concepts into policy briefs is difficult but necessary. We convinced regulators that privacy does not mean hiding money; it means selective disclosure. The same applies here: selective disclosure of proof of location, not full surveillance, is the path to verifiable truth.
Contrarian: The Blind Spots of Trusting Code Alone
But I have been in this industry long enough to know that code is not magic. During the Terra/Luna collapse, I watched algorithmic stability promises shatter because the oracles feeding the UST peg were fundamentally flawed. The same risk applies here: if the satellite imagery oracle is compromised—say a single API key is leaked—the entire verification system becomes a lie. Additionally, battlefield conditions are chaotic. A soldier may not be able to submit a ZK-proof under fire. And what about the problem of deepfakes? If a video generator can create a synthetic capture event that passes visual inspection, the hash of that fake video is still real. The blockchain verifies the timestamp of the data, not the truth of the data. This is the fundamental limitation: garbage in, garbage out, but now permanently stored.
I also experienced the Nifty Gateway ethical stand, where a well-intentioned royalty enforcement system actually penalized secondary market creators. Good intentions are not enough; incentive alignment matters. In the Kostiantynivka case, the incentive for both sides is to manipulate truth. A blockchain solution only works if both parties agree to submit data. In a zero-sum conflict, why would they? The answer might be trustless public goods: a neutral entity like the International Committee of the Red Cross could deploy a smart contract that rewards both sides for submitting verified proofs (e.g., small crypto bounties for each valid location report). This is similar to Gitcoin’s quadratic funding: align incentives with public good.
Another blind spot: 90% of so-called “Bitcoin Layer2s” are Ethereum projects rebranding for hype; the real Bitcoin community doesn’t acknowledge them. Similarly, many blockchain-based verification projects are startups that will die in the bear market. We need infrastructure, not hype. The proven concept is not novel chains but simple smart contracts on Ethereum or a carbon-neutral L2 like Arbitrum (ironically, gas costs matter). For Kostiantynivka, a simple hash-of-report contract could be deployed in ten lines of Solidity. The hard part is political adoption, not technology.
Takeaway: Building the Infrastructure for Post-Truth Conflict Resolution
The battle for Kostiantynivka is a microcosm of a larger crisis: we have the tools to create irrefutable evidence of what happens on the ground, but we choose not to use them. Why? Because the fog of war serves the powerful. When I wrote about the Uniswap liquidity mining crisis, I said that hype fades, but ethics endure. The same applies to war: hype (propaganda) fades, but a dead civilian cannot fade. We need to build the infrastructure that forces transparency, not because it is easy, but because it is the only way to end the recursive cycle of lies.
The soul of this conflict will remain quiet until the graph on the blockchain shows a verifiable consensus. When the graph spikes, the soul remains quiet. But when the data is on-chain, the lies have nowhere to hide.
Let me end with a rhetorical question: If we can build a decentralized financial system that processes billions of dollars without a central party, why can't we build a decentralized truth system that processes the most critical data of all—whether a human being is alive or dead?
