In one line
Aephoron renders the web with its own Rust engine on desktop and Android, integrates Eoonia and the Ailoos assistant, and is not yet in any store.
Done
- Kinetoor, the engine (deep Servo fork), renders real sites.
- Desktop: egui interface with Material Design 3 toolbar, omnibox and tabs; 350+ roadmap tasks complete; clean compile.
- 19 crates: IPFS/IPNS gateway, on-chain DNS for
.emp, DNS-over-HTTPS, password manager (AES-256-GCM, breach check), encrypted sync over IPFS, bookmarks, downloads, prefetch, updater, wallet (Eoonia, SIWE,personal_sign), WalletConnect v2, payments (eth_call, ERC-20 encoding), AI (Ailoos), profiles with guest mode, PWA install, translation, PDF viewer, ads (SkoopoS), price ticker (DMS/DUSD). - Ads: native connection to the SkoopoS backend, verified end to end (30 July).
- Assistant: Ailoos model in the sidebar, Brave-Leo style, against
api.ailoos.com. - Android (8 September): a full news site rendered in a platform view on a POCO F8 PRO, redirects followed, URL returned to the bar. Four traps cleared: jemalloc silently empty on
aarch64, Scudo pointer tagging crashing SpiderMonkey, double engine init, R8 stripping 18 JNI callbacks in release. Release AAB 90.8 MB after size optimisation (engine 138 → 89 MB). - August audit (12 agents): a remote-code-execution path in the updater and a wallet store decryptable without a password, both fixed before any release.
Tooling that came out of it
verificar_motor.sh resolves the engine library's symbols against the NDK stubs (would have caught the jemalloc trap before the phone). verificar_puente.sh checks that every JNI callback Rust calls by name survives in the built dex. Both run on the artefact, not the source.
Not done
- A store listing for Android; hardening of the release build continues.
- Client diversity for the web: Kinetoor is one engine, young, and will render some sites imperfectly. It says so.
- macOS/iOS builds in the current environment.
Why an engine
Every other ecosystem browser is Chromium with an extension. Owning the engine is what lets Aephoron resolve .emp domains natively, block ads at the network layer while serving the ecosystem's own verifiable ads, and treat the wallet as a browser component rather than a plug-in. It is also why the work is slow. The August audit and the Android traps are the price; the checkpoint records both.
Based on the Aephoron roadmap (session 14), the Android Kinetoor notes (2026-09-08) and the August 2026 audit.