The Safex Mine v1.1.0 — Multilingual release + new project website
A fairly substantial update since the original v1.0.0 release. ![]()
The Safex Mine v1.1.0 is now available for Windows x64, with the main focus of this release being localisation and making the application much easier to use outside English-speaking Windows installations.
The application now supports English (Australia) plus 23 translated languages/locales across the main UI, status/accessibility text and the Mining Risk Acknowledgement.
- Bengali — বাংলা
- Chinese (Simplified) — 简体中文
- Dutch — Nederlands
- Filipino — Filipino
- French — Français
- German — Deutsch
- Greek — Ελληνικά
- Hindi — हिन्दी
- Hungarian — Magyar
- Indonesian — Bahasa Indonesia
- Italian — Italiano
- Japanese — 日本語
- Korean — 한국어
- Polish — Polski
- Portuguese (Brazil) — Português (Brasil)
- Portuguese (Portugal) — Português (Portugal)
- Russian — Русский
- Serbian (Latin script) — Srpski
- Slovenian — Slovenščina
- Spanish — Español
- Turkish — Türkçe
- Ukrainian — Українська
- Vietnamese — Tiếng Việt
Windows will automatically try to select the best supported language from the user’s preferred Windows languages, or the language can be changed manually and remembered by the app. The language can also be selected before accepting the first-run Mining Risk Acknowledgement.
The single Windows installer is multilingual as well, with 22 installer languages in total. Filipino and Bengali currently use the English installer UI, but both still receive the fully translated application and translated installation/first-use documentation.
We have also published 23 translated Windows installation guides, covering the important first-use information around SmartScreen, Microsoft Defender, checksum verification and the narrowly scoped antivirus exclusion process if one is required.
New multilingual project website
I’ve also put together a small public site for The Safex Mine:
The website supports the same 24 release-enabled application languages, automatically follows the visitor’s browser language where possible, and provides:
- the current Windows download and SHA-256 information;
- screenshots and an overview of the miner;
- the three CPU modes — Calm, Balanced and Full Bore;
- installation/security guidance;
- direct access to the appropriate translated Windows installation guide;
- links back to the public source repository and project documentation.
The site is deliberately simple and static — no analytics, advertising, tracking, external fonts or third-party JavaScript.
What hasn’t changed
v1.1.0 does not change the underlying mining model established in v1.0.0.
It is still a Windows desktop Safex Cash solo miner using the Safex-compatible XMRig backend, with the standard-user GUI / narrowly scoped elevated-helper model for XMRig and MSR optimisation.
The default public daemon remains:
rpc.safex.org:17402
Custom/LAN nodes are still supported.
Windows security reminder
The Safex Mine remains an unsigned Windows application.
Because it contains a CPU miner, elevated helper and WinRing driver, SmartScreen or antivirus products may warn about or quarantine the installer or mining components.
Please download it only from the official GitHub release and verify the supplied SHA-256 checksum before running the installer.
If Defender quarantines the installer immediately after download, the tested process is to restore/allow that specific installer, verify its SHA-256 against the published checksum, and only then run it. There is no need to disable Defender or create broad exclusions.
Download
The Safex Mine v1.1.0
Installer:
The-Safex-Mine_1.1.0_x64-setup.exe
SHA-256:
DB13AB3CF3D1A9B34AE291A5F3643C32C8421D4F9C6C7AEA47B0447EA453FF93
Translation feedback is still very welcome
The translated material is AI-assisted community-project localisation, with English (Australia) remaining the canonical reference.
A lot of work went into checking terminology consistency, layout behaviour and the various scripts used across the release, but native-speaker review is still extremely valuable.
So if you use one of the translated versions and spot wording that feels unnatural, technically incorrect or could simply be clearer, please post the language and suggested correction here or raise it on GitHub. Those corrections can be incorporated into later patch releases.
Thanks again to everyone who tested the original release, offered feedback, or was willing to have a look through the translations. ![]()