Rolling – Earlybirds Invest

Recall is shipping after nearly a year of announcement

Recall was originally announced in May 2024 as the flagship feature of Windows 11 and Snapdragon-powered “AI” PCs.

At that time, Microsoft touted Recall as one of the best use cases of AI on Windows 11, but security researchers noted that Recall is a privacy nightmare that captures your passwords and stores them in plain text.

Microsoft pulled back Recall AI and promised to address the privacy and security concerns by testing it with Windows Insiders.

The company also made Recall completely optional and upgraded the model to filter out passwords or other sensitive information.

After nearly one year of delay, Recall is now included in Windows 11 Build 26100 for PCs with Snapdragon Copilot+ PCs.

Recall will begin rolling out to everyone with the May 2025 Patch Tuesday Update.

What you need to know

Google is rolling out Loss of Pulse Detection to Pixel Watch 3 owners in the U.S. starting today.

The feature, which is opt-in, will automatically check if your pulse is detected and call emergency services if it can’t be found.

This life-saving tool will take a couple of weeks to become available for all Pixel Watch 3 users.

Google is now rolling out Loss of Pulse Detection, a new safety feature for the Pixel Watch 3, to U.S. users. The feature was originally marketed as a Pixel Watch 3 feature last year, and became available in other regions, but required FDA approval before it could work in the U.S.

Google earned that approval in February 2025, and Loss of Pulse Detection will become available in the country starting today, with a full rollout lasting a few weeks.

After earning FDA approval, the company announced Loss of Pulse Detection for U.S. users as part of the March Pixel Feature Drop. Originally, Google said it would “begin rolling it out in the U.S. at the end of March.” That deadline passed, but now the feature is shipping as of April 8, 2025.

Loss of Pulse Detection is a critical safety feature that Google explains can “detect when you’ve experienced a loss of pulse” and “automatically prompt a call to emergency services for potentially life-saving care if you’re unresponsive.” It adds a new element to Emergency SOS, which can be used to call emergency services quickly from your smartwatch.

Image 1 of 3

Google's Loss of Pulse will "check for pulse" if it cannot detect your heartbeat before calling emergency services. — (Image credit: Google)

Loss of Pulse Detection is opt-in, so you’ll need to manually enable it when the feature becomes available on your device. To do so, open the Google Pixel Watch app on your phone and tap Safety and Emergency. Then, press Loss of Pulse Detection, and follow the on-screen prompts to enable the safety tool. After that, the feature will monitor your heart rate and try to detect when and if your pulse can’t be found.

Prior to launching in the U.S., Loss of Pulse Detection has been available in 14 countries. The feature first arrived on Pixel Watch 3 for users in the EU last year.

It’s rolling out starting today, but may take “a couple” of weeks before it arrives on all U.S. Pixel Watch 3 devices. The announcement comes as Google releases the April 2025 update for all Pixel Watch models.

CORRECTION (Feb. 22, 19:16 UTC): Reworks the story throughout to clarify and include more context of the so-called “rollback” and the criticism around it. Also removed the percentage of ETH held by hackers in 2016).

Arthur Hayes, co-founder of BitMEX and major ether (ETH) holder, asked Ethereum co-founder Vitalik Buterin if he would be willing to entertain the idea of rolling back the network to assist hacked exchange Bybit, which lost nearly $1.4 billion in ether (ETH) on Friday.

“@VitalikButerin will you advocate to roll back the chain to help @Bybit_Official,” Hayes said in the social media post.

“My own view as a mega $ETH bag holder is $ETH stopped being money in 2016 after the DAO hack hardfork. If the community wanted to do it again, I would support it because we already voted no on immutability in 2016 [wh]y not do it again?” he added

Buterin was yet to reply as of time of publication.

While some, including Unchained’s Laura Shin, wondered if Hayes’s post was a joke, it did raise a serious question about whether rolling back is even feasible. CoinDesk reached out to Hayes about the post and hasn’t received a comment at the time of writing.

“I wish we could roll back for the Bybit hack, I’m not against the idea. But the DAO hack was 15% of ETH with a clean recovery path. Today, a rollback would break bridges, stablecoins, L2s, RWAs and so much more. ETH ecosystem is just too interconnected now for a clean solution like 2016,” said Gautham Santhosh, co-founder of Polynomial.fi.

The problem with “rollback”

Hayes’ suggestions of rolling back the blockchain as one of the potential ways to address hacking involves reverting the blockchain to a state before a specific event, in this case, the hack. That way, malicious transactions resulting from the hack can be erased, effectively restoring lost or stolen funds. Implementing a rollback requires consensus from the network participants.

For instance, in 2016, the Ethereum network saw a controversial revision of the network using a hard fork to reverse a theft of $60 million in ether from The DAO (the percentage the hackers took control of is still up for debate). The hard fork split the chain into two – Ethereum and Ethereum Classic.

However, the term “rollback” was never used during that revision; it was referred to as an “irregular state transition.” The move still triggered huge and important debates over so-called “immutability” in blockchains.

Immutability is a security feature that prevents data from being changed after it’s added to the blockchain, making it trustworthy and tamper-proof.

A similar controversy played out in the Bitcoin community in 2019 when Binance’s CEO Changpeng Zhao and his team considered pushing for a “rollback” approach (the term was later rephrased by CZ as “re-org” and decided not to pursue the approach) on the Bitcoin network following a $40 million hack. However, the Bitcoin mining community criticized the idea of going back against the principle of decentralization and immutability.

Similarly, the Ethereum community criticized the idea of “rollback” in this case, noting that the idea wouldn’t even have been considered by the community.

Theoretically, an actual “rollback” won’t be possible on Ethereum, as the network uses something called “accounts” to store the ether, which can be analogous to bank accounts. When the 2016 hack occurred, the nodes upgraded to new software, and the ETH held was moved to new addresses.

However, the idea of reversing a transaction in light of a hack isn’t a new one; at least one smaller blockchain network, Vericoin, actually executed such a procedure previously.

The Bybit hack came into light on Friday when on-chain sleuth ZachXBT noted suspicious outflows of over $1.4 billion from the exchange, with the attacker quickly swapping mETH and stETH for ether through a decentralized exchange.

The hackers were later identified by ZachXBT as the North Korean Lazarus Group.

The attacker then split 10,000 ETH to 39 different addresses and another 10,000 ETH to nine addresses, Polynomial.fi’s Santhosh said on X.

Bybit CEO Ben Zhou said that the hacker “took control of the specific ETH cold wallet and transferred all the ETH in the cold wallet to this unidentified address.” Zhou confirmed that the exchange “is solvent even if this hack loss is not recovered.”

Margaux Nijkerk contributed to the revised story.
Read more: Ether Price Spikes Further on Reports of Bybit Starting to Buy ETH