ADAMANT Messenger v4.12.1: Harder Security, Eight Languages with Arabic RTL, and Faster Multi-Chain Wallets

Verifiable Builds and Zero-Compromise Browser Security
In a client-only crypto messenger where keys stay strictly on your device, the browser or WebView runtime itself is part of the threat model. ADAMANT v4.12.1 ships behind a unified strict Content Security Policy and security response header baseline—frame-ancestors 'none', X-Frame-Options: DENY, X-Content-Type-Options: nosniff, and Referrer-Policy: no-referrer—enforced continuously by automated production probes. Web3 validation was migrated to eval-free Zod 4 (jitless) and abitype, eliminating runtime eval and dynamic Function construction from the bundle, verified by a strict build gate before shipping.
The Build Identity indicator on Login and Settings lets you inspect the exact version, source branch, commit hash, author, and build timestamp, plus trigger a safe Force refresh of cached app assets without touching keys or encrypted local storage. Testnet mirrors carry clear TESTNET markers so test funds and mainnet sessions are never confused.

Eight Full Languages and Arabic RTL Support
ADAMANT doubles its full language coverage from four to eight complete localizations (418 matched interface keys per language). Arabic ships with full right-to-left layout support, mirrored directional icons, logical CSS spacing, dir="auto" composer alignment for natural mixed-direction typing, and clean Latin numerals (ar-u-nu-latn) for dates and balances. Spanish, French, and Japanese are newly added and matched across every dialog, wallet screen, and error message. English, German, Russian, and Simplified Chinese have been audited and aligned with corrected pluralization rules. Language preference is detected locally from browser settings without phoning home or leaking telemetry.


More Reliable Multi-Node Chats, Transfers, and Wallet History
Because ADAMANT connects directly to independent community nodes and indexers rather than a single corporate server, resilience comes down to how carefully the client handles partial failures and pagination. Updated ADAMANT Node REST/WebSocket subscriptions (includeDirectTransfers filters and [0, 8] socket events) ensure incoming direct ADM transfers refresh cleanly in chat lists and conversation bubbles.
Native Ethereum lookups now split into bounded indexed PostgREST queries merged client-side so indexers do not stall. BTC, DOGE, and ETH pagination keeps each scroll session pinned to a single active node instead of broadcasting your wallet address across multiple operators. Stale persisted pagination cursors in IndexedDB are automatically sanitized on save.
Outdated ADM nodes (< 0.10.0) and IPFS nodes (< 0.1.0) are clearly marked and filtered before requests fail silently, alongside refreshed fallback node endpoints from adamant-wallets. Even over plain HTTP .onion mirrors where Web Crypto is unavailable, attachment CID hashing works via a pure JS SHA-256 fallback.


Platform Updates and Apple Situation
v4.12.1 targets Android 16 (API 36) with a signed APK and App Bundle (versionCode 41201), updates desktop dependencies (Electron, Vite, Vue, Vuetify), and tightens production Electron bundling so development tools are excluded outside dev builds.
Apple blocked the ADAMANT developer account, so the iOS App Store build cannot currently be updated or installed via Apple’s store. Native macOS desktop apps (x64, Apple Silicon, and Universal .dmg) are still built, signed with Developer ID, and published on GitHub—just without Apple notarization. After opening the app once, go to System Settings → Privacy & Security → Open Anyway to run it normally.
Release notes and binaries are available on the v4.12.1 GitHub release page.