Status Legacy
im.status.ethereum
Zapstore _@zapstore.dev Republished from GitHub / F-Droid by the Zapstore main account.
a free (libre) open source, mobile OS for Ethereum
First release: Aug 11, 2025, 2 total releases.
Most recent release: Oct 28, 2025.
Appears in 0 app stacks.
0 sats / 0 zaps received in the past year.
Sats Received
Underlying data available via MCP: app_zaps, app_releases.
Zap Count
Underlying data available via MCP: app_zaps, app_releases.
Releases
- ### Release Notes Patch on top of [2.34.3](https://github.com/status-im/status-mobile/releases/tag/2.34.3) Read more about [Legacy Mobile App v2.34.4, Unified Mobile App, and What’s Next](https://status.app/blog/legacy-mobile-app-v2-34-4-unified-mobile-app-and-whats-next) The Status app team is now releasing the final feature release (v2.34.4) of this legacy Status Mobile App (Status Legacy), which includes: 1. Renaming the app to Status Legacy and changing its icon to blue, so users can easily distinguish it from the unified Status mobile app (Status).
More…
 2. Two new features to make user profile and data migration to the unified Status mobile app (Status) simple, secure, and private: - Optional message syncing across devices using end-to-end encrypted app pairing. Go to Settings → Syncing and Backup → Paired Devices → Tap + to start a new sync → Enable message syncing. <img width="393" height="873" alt="Screenshot_20251028_134318_Status_Legacy" src="https://github.com/user-attachments/assets/6a75b451-c5fc-4641-bcdf-add3a477a256" /> - On-device backup to manually back up your Status profile data (including optional backup of your direct, group, and community messages) directly on your device. Go to Settings → Syncing and Backup → Backup. <img width="393" height="533" alt="Screenshot_20251028_134238_Status_Legacy" src="https://github.com/user-attachments/assets/c72a8887-e025-4892-b095-f25cd29e9887" /> While the Clojure-based Status Legacy app (Status Legacy) will remain public and open for contributions, the core Status team won’t add new features beyond the current v2.34.4 release. The team will focus on developing the unified Status Mobile App (Status) going forward. We may issue critical fixes, if absolutely needed, during the 2–3-month user migration period. Read more about [Legacy Mobile App v2.34.4, Unified Mobile App, and What’s Next](https://status.app/blog/legacy-mobile-app-v2-34-4-unified-mobile-app-and-whats-next) - # Mobile release notes Patch on top of [2.34.2](https://github.com/status-im/status-mobile/releases/tag/2.34.2) ## 🔨 Bug Fixes - Fixed issue with choosing incorrect network for swap ([PR](https://github.com/status-im/status-go/pull/6785)) - Fixed issue with collision of tokens from different token lists ([PR](https://github.com/status-im/status-go/pull/6793)): - Fixed the delay when active networks switched ([PR](https://github.com/status-im/status-mobile/pull/22641))