WHAT ATTESTATION ACTUALLY DOES
Remote attestation lets a remote server verify what software is running on your device. A hardware key, burned into the phone at the factory, signs a statement: 'this is a Pixel running stock Android, bootloader locked.' The server trusts the chip, not the user.
THE ROOT-OF-TRUST PROBLEM
Attestation answers 'is this device unmodified?' — but the only authority that can answer is the manufacturer. Google signs Pixels, Apple signs iPhones, Samsung signs Galaxies. A user who compiles their own OS has no signing authority anyone trusts, regardless of whether the build is more secure than stock.
WHY GRAPHENEOS LOSES
GrapheneOS is widely regarded as the most hardened Android variant — verified boot, hardened memory allocator, network permission toggles. None of it matters for attestation. The Play Integrity API checks for one specific signing key (Google's), and a self-signed build fails by definition, even when measurably more secure.
THE CAPTCHA PIVOT
reCAPTCHA started in 2007 as image puzzles, pivoted to behavioral analysis (mouse movements, browser fingerprints) around 2014, and is now moving to device attestation. Each generation traded user friction for deeper system access. The endpoint is a web that asks not 'are you human' but 'is your device approved.'
THE PRECEDENT
Web Environment Integrity — Google's 2023 proposal to bring Play Integrity-style attestation to all browsers — was withdrawn after public backlash. Apple shipped Private Access Tokens, a similar mechanism, in iOS 16 with almost no objection. The reCAPTCHA change implements the same idea on Android without a standards process at all.
THE BANKING TRAP
Once a bank, government portal, or healthcare site adopts attestation-gated login, users on unattested devices have no recourse — the failure is silent and looks like a network error. The user cannot 'try harder' or solve a puzzle. The lockout is structural, and the alternative is buying a different phone.