Breaking news

NYT Analysis Suggests Adam Back As Possible Bitcoin Creator

Introduction

A recent report by The New York Times revisits the identity of Satoshi Nakamoto, the pseudonymous creator of Bitcoin, and suggests that British cryptographer Adam Back may be a possible match. Back has consistently denied any connection to the identity. The investigation adds to ongoing efforts to identify the individual or group behind Bitcoin’s creation.

AI-Powered Forensic Analysis

John Carreyrou, journalist at The New York Times, analyzed email archives from three cryptography mailing lists spanning 1992 to 2008, a period linked to early Bitcoin development. Artificial intelligence tools were used to compare linguistic patterns, including punctuation choices and grammatical structures. Based on these indicators, the report identified Adam Back as a close stylistic match. Results are not presented as conclusive proof and remain part of a broader set of investigative approaches.

A Profile Consistent With A Cypherpunk Legacy

Adam Back is known for creating Hashcash, a proof-of-work system later referenced in Bitcoin’s design. He is also co-founder and CEO of Blockstream, a company focused on blockchain infrastructure. His background in cryptography and long-standing involvement in digital currency research align with characteristics often associated with Bitcoin’s creator. The report highlights these elements as part of its assessment.

Continuing The Debate

Back said similarities identified in the analysis may reflect common writing patterns among experienced cryptographers. He reiterated his denial of being Satoshi Nakamoto in comments shared on X. The debate over Bitcoin’s origin continues, with multiple theories and candidates discussed over time.

Google Sets New Android App Rules To Cut Memory Use

Google is introducing new quality requirements for Android apps as developers face tighter constraints on device memory and broader hardware supply pressures.

The company announced two new requirements this week. One focuses on reducing apps’ memory use and improving code efficiency, while the other requires apps to restore users’ sign-in status when they move to a new Android device.

Google Sets New Memory Performance Rules

Google said the mobile industry is facing “significant hardware supply constraints that are altering device memory availability,” which could affect app performance and the user experience.

Under the new rules, developers will need to meet thresholds covering areas including dynamic memory and bitmap usage. Additional code optimisation requirements are designed to reduce slowdowns and crashes linked to excessive resource use.

Google is also rolling out tools that alert developers when their apps exceed the new limits. More diagnostic features are planned later this year, including deeper analysis through Android’s Memory Limiter, which restricts excessive memory use.

Developers have until February 2027 to comply with the new standards, according to Google’s Android Developer documentation.

Zero-Tap Sign-In Requirement Starts In 2027

A separate requirement will apply to all apps distributed through Google Play. By April 2027, apps that use optional or mandatory sign-ins must automatically restore a user’s sign-in state when they move between Android devices.

The feature will rely on Android’s Restore Credentials API, which is designed to transfer sign-in credentials during device migration without requiring users to log in again.

Google said the new standards are intended to help developers maintain app performance and simplify device transitions as device specifications and memory availability change.

The Future Forbes Realty Global Properties
Aretilaw firm
Uol
eCredo

Become a Speaker

Become a Speaker

Become a Partner

Subscribe for our weekly newsletter