Around a dozen banking apps began specifically permitting GrapheneOS
- ID
- 39081
- Status
- summarized
- Published
- 24 Oct 2026, 9:15 AM
- Fetched
- 24 Oct 2026, 11:34 PM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://grapheneos.social/@GrapheneOS/117492375462459244
- Source URL
- https://hnrss.org/best
Summary
- Score
- 5.0
- Created
- 24 Oct 2026, 11:35 PM
- Tags
- Audience
- developerssaas_startup_founders
What happened
A GrapheneOS project post claims that around a dozen banking apps have started specifically permitting GrapheneOS rather than blocking it outright. The excerpt itself is only the Mastodon page shell plus an unrelated reply about a Jolla/Sailfish phone, so it names no banks, no dates, and no technical mechanism. The Hacker News thread drew 390 points and 122 comments, which is the main evidence of builder interest here.
Why it matters
If the claim holds, it means some banks moved from blanket 'block non-Google-certified devices' logic to allowlisting specific OS builds — which changes what your own app's Play Integrity or hardware-attestation checks should return. Before copying that pattern, note the source gives zero detail on which banks, which verdicts (MEETS_DEVICE_INTEGRITY vs. strong integrity), or how allowlisting is maintained, so you cannot implement from this alone; treat it as a prompt to check whether your app fails closed on custom ROMs and whether that is a deliberate fraud decision or an accident.
Discussion angle
Ask the room: should a fintech app allowlist specific custom ROMs, or keep failing closed on attestation? Then walk through what a Malaysian banking or payments team would actually need — named banks, which integrity verdict changed, and who maintains the allowlist — none of which this post provides.