Connect with us

Crypto World

How bombing Iran shifted oil and bitcoin prices

Published

on

How bombing Iran shifted oil and bitcoin prices

Since the world learned of massive US military deployments toward Iran on February 18, crude oil has rallied 36%, far surpassing bitcoin’s (BTC) 2.8%.

War-related headlines have definitely affected BTC which, with its 24-hour spot trading venues, has served as a trillion-dollar proxy for risk-on assets.

By charting the price of oil relative to BTC from the de facto start of the war, some of the conflict’s most critical moments become clear.

As a reference price for their pre-wartime starting points, at 12:15am New York time on February 18, BTC traded at $67,833. Oil, specifically contracts for difference (CFDs) on WTI crude, were trading at $62.39 per barrel.

Advertisement

At that time, open-source intelligence accounts began documenting “the largest US Air Force combat buildup in Europe and the Middle East since the Gulf War,” listing dozens of tankers, F-22s, and F-16s repositioning toward the Persian Gulf and Iran.

Chart 1: Price reaction to historic US naval movements toward Iran

BTC (orange) versus oil (blue), 12:15am Feb 18 to 12:15am Feb 20. Source: TradingView

The onset of war became obvious, and oil prices responded to the likelihood of supply restrictions. CFDs for the world’s most-traded and arguably most important commodity rallied without interruption for hours, and by two days later, oil had jumped 7% to $66.76 per barrel.

BTC, meanwhile, barely budged to $67,376, a near-flat 48-hour performance from its $67,833 start.

The divergence in those first 48 hours set the template for what followed. 

Oil immediately priced in an imminent kinetic war. BTC did not.

Advertisement

The sophistication of oil traders relative to BTC traders was obvious during those first two days.

Slowly, as anyone should expect from the class of risk-on investments as threats become too obvious to ignore, BTC slid deeper into the red after the initial military buildup reports, hitting a low of $62,525 a week later on February 24, a 7.8% decline from its 12:15am start on February 18. 

Oil, in contrast, had already begun a steady climb as more confirmation of military intent trickled into the mainstream news cycle. War was inevitable, and oil traders knew it.

Chart 2: Price reaction to official announcement of war

BTC (orange) versus oil (blue), 5pm February 27 to 6pm March 1. Source: TradingView

Finally, at 1:15am New York time on February 28, US and Israeli airstrikes on Iran formally commenced under the banner of “Operation Epic Fury.” Donald Trump announced the operation via Truth Social.

At this time, BTC was trading at $65,492. However, because the announcement fell on a weekend, oil CFDs weren’t open for trading, so there’s no way to know exactly how high oil would have traded.

Advertisement

Unfortunately, the most recent simultaneous price for both assets was February 27 at 5pm New York time: BTC at $65,524 and oil at $67.28 per barrel.

BTC panicked on the initial, formal announcement from Trump. Within 30 minutes, it dropped 3.8% to $63,037. It then recovered.

By Sunday, March 1 at 6pm New York time, when oil CFDs resumed trading, crude had gapped up 11.5% to $75 per barrel. 

BTC, at $65,245, remained essentially flat since Trump’s formal announcement. 

Advertisement

Oil was already repricing supply disruptions through the Strait of Hormuz, where Iran’s Islamic Revolutionary Guard Corps was threatening to block tanker traffic. BTC wasn’t. It had already sold off slightly from its pre-war, $67,833 start.

Oil surges 91% to $119 per barrel, while BTC recovers its mild loss

The war escalated quickly, sending the price of oil skyrocketing, but risk-on assets soon recovered entirely. 

Iran tried to close the Strait of Hormuz, briefly disrupting roughly 20% of global oil supply. Tanker traffic through the chokepoint dropped 81%. Airports and US bases throughout the Middle East took on drone and missile damage.

Oil producers declared force majeure on contracts. Drone strikes hit Saudi Arabia’s largest refinery and Qatari export facilities. Gulf oil production collectively fell by 6.7 million barrels per day by March 10.

Advertisement

Incredibly, oil prices wicked up to $119.48 per barrel at 10:32pm New York time on March 8, a 91.5% surge from its February 18 baseline. BTC peaked much earlier, at $74,075 on March 4 at 2:15pm New York time, for a comparatively modest 9.2% gain.

By 10:40pm New York time on March 10, oil had pulled back 29% from its peak to $84.86 per barrel, partly on comments from Trump suggesting the conflict would resolve “very soon.”

BTC sat at $69,725.

Read more: Bitcoin up, Dubai real estate down since Iran war began

Advertisement

Chart 3: From start to finish, two wildly different returns

BTC (orange) versus oil (blue), 12:15am February 18 to 10:40pm March 10. Source: TradingView

In the roughly three weeks since the start of the war, oil has gained approximately 35% while BTC as a risk-on asset has gained approximately 3%. The above chart illustrates that time period.

Oil’s entire trading range over that time period was $62.39 to $119.48 per barrel. BTC’s range, despite its far smaller size, was a far more conservative $62,525 to $74,075. 

One asset reacted to a worldwide a supply shock. The other absorbed headline volatility and largely shrugged it off.

As usual, there are many ways to trade headlines. At least across the opening weeks of this war, oil scarcity has been the bullish trade. BTC was the hold.

Got a tip? Send us an email securely via Protos Leaks. For more informed news, follow us on X, Bluesky, and Google News, or subscribe to our YouTube channel.

Advertisement

Source link

Advertisement
Continue Reading
Click to comment

Leave a Reply

Your email address will not be published. Required fields are marked *

Crypto World

Aave Oracle Glitch Causes $27M Liquidations: CAPO Misconfiguration Confirmed

Published

on

Aave Oracle Glitch Causes $27M Liquidations — CAPO Misconfiguration Confirmed

A misconfigured Oracle system in Aave triggered $27 million in forced liquidations on March 10, undervaluing wrapped staked Ether by 2.85% against its actual market rate.

According to the post-mortem by Chaos Labs, the CAPO oracle error caused Aave V3 Ethereum Core and Prime instances to apply an exchange rate of roughly 1.1939 wstETH-per-ETH when the live onchain rate was approximately 1.228, enough of a gap to push 34 high-leverage E-Mode positions below their liquidation thresholds automatically.

It resulted in the liquidation of 10,938 wstETH. The protocol says it incurred no bad debt and is moving to compensate all affected users.

The Damage: 34 Users, $27M in Liquidations, and 499 ETH in Bot Profits

Advertisement

The oracle glitch liquidated 34 users, with the total volume reaching $27 million in wstETH positions.

Liquidation bots moved quickly, capturing 499 ETH in bonuses, approximately $1.2 million, by executing against positions that should not have been eligible for liquidation at that moment.

Aave founder and CEO Stani Kulechov confirmed in a Wednesday post that the protocol generated no bad debt from the incident.

Of the 499 ETH that went to liquidators, Aave recaptured 141 ETH ($285,000) through BuilderNet refunds and an additional 13 ETH in liquidation fees.

Those recovered funds will flow directly to affected users as compensation, with DAO treasury funds covering any remaining shortfall up to the full 345 ETH identified as the excess liquidation windfall.

Lido contributors confirmed the event had no connection to wstETH or the Lido staking protocol itself; the issue originated entirely within Aave’s oracle configuration layer.

With Ethereum price defending the $2,000 support zone around the time of the incident, the liquidation values were amplified by the broader market context for ETH-denominated collateral.

Advertisement

Discover: The best pre-launch crypto sales

Chaos Labs Confirms Aave CAPO Oracle Misconfiguration: Here Is What They Found

Chaos Labs, Aave’s external risk management partner, confirmed the incident stemmed from what it described as an onchain configuration misalignment under differing onchain update constraints, not a design flaw in the CAPO system or in the core oracle infrastructure of Aave.

The team emphasized that Chaos Risk Oracles had processed over 1,200 payloads and more than 3,000 parameters across Aave markets without incident prior to March 10.

Advertisement
Aave Oracle Glitch Causes $27M Liquidations — CAPO Misconfiguration Confirmed
24-hour liquidations on Aave. Source: Chaos Labs

Chaos Labs quickly contained the situation: borrow caps on wstETH were reduced immediately, and snapshot parameters were manually realigned to restore oracle accuracy. Kulechov noted in his public statement that the configuration issue had already been remediated by the time the post-mortem was published, and praised the team’s response speed in limiting broader DeFi risk contagion.

The Aave governance post-mortem marks this as the first operational failure in CAPO’s deployment history on Aave V3, despite more than a year of live operation across multiple markets.

What Traders and Aave Users Are Watching Next

The immediate focus is on the full reimbursement timeline. Aave DAO service providers are finalizing compensation for all 34 affected users following the initial 141 ETH refund via BuilderNet, with a formal governance announcement expected shortly.

Beyond compensation, governance teams are conducting a broader review of CAPO parameters across all Aave markets, updating stale snapshots and building out enhanced monitoring to flag rate divergences before they reach liquidation-threshold proximity.

Advertisement

Whether that review produces binding parameter update standards or remains advisory is the governance question to watch.

If the DAO formalizes automated CAPO sync requirements and publishes updated risk oracle documentation, the incident may ultimately strengthen Aave’s operational credibility. If the review stalls at the discussion stage, the reputational cost will compound the financial one.

Discover: The best new cryptocurrencies

The post Aave Oracle Glitch Causes $27M Liquidations: CAPO Misconfiguration Confirmed appeared first on Cryptonews.

Advertisement

Source link

Continue Reading

Crypto World

CBI Arrests Darwin Labs CTO in GainBitcoin Cryptocurrency Case

Published

on

CBI Arrests Darwin Labs CTO in GainBitcoin Cryptocurrency Case

India’s Central Bureau of Investigation (CBI) has arrested Ayush Varshney, co-founder and chief technology officer of Darwin Labs Private Limited, in connection with the long-running GainBitcoin cryptocurrency fraud investigation.

According to a Wednesday press release shared via the CBIs official X account, Varshney was detained at Mumbai airport on Monday while attempting to leave India after a Look Out Circular had been issued against him. He was formally arrested and handed over to the CBI on Tuesday.

The CBI said Darwin Labs played a central role in building the technological infrastructure used by the alleged scheme, including the GainBitcoin investor platform and associated tools used to manage payments and wallets.

The arrest is the latest development in India’s investigation into the multi-million-dollar GainBitcoin scheme, one of the country’s largest alleged cryptocurrency investment frauds.

Advertisement
Source: CBI India

Investigators link developer to infrastructure behind alleged scheme

According to the CBI, the GainBitcoin scheme was promoted through Variabletech Pte. Ltd. and allegedly promised investors monthly returns of about 10% in Bitcoin (BTC) for up to 18 months. “The funds collected from investors were subsequently misappropriated,” the CBI said.

Related: India’s central bank proposes linking BRICS digital currencies for trade: Reuters

The agency said Darwin Labs and its co-founders, including Varshney, Sahil Baghla and Nikunj Jain, were involved in designing and deploying a cryptocurrency token known as MCAP along with its associated ERC-20 smart contract.

CBI added that the company also helped develop key components of the platform’s technical infrastructure, including the GBMiners.com mining pool, a Bitcoin payment gateway, the Coin Bank Bitcoin wallet, and the GainBitcoin investor website used to interact with participants.

Decade-old case involved 8,000 investors and $790 million

GainBitcoin emerged in the mid-2010s as a cloud-mining investment platform that encouraged users to purchase Bitcoin and deposit it with the service in exchange for promised fixed returns.

Advertisement

The CBI alleged that the scheme eventually relied on a multi-level marketing structure in which payouts were tied to recruiting new investors. As new deposits slowed, the platform reportedly shifted payouts from Bitcoin to its in-house MCAP token, which had a significantly lower value.