Copyright (c) 2014-2019, The Monero Project
- Development resources
- Vulnerability response
- Introduction
- About this project
- Supporting the project
- License
- Translations
- Installing the Monero GUI from a package
- Compiling the Monero GUI from source
- Web: getmonero.org
- Mail: [email protected]
- Github: https://github.com/monero-project/monero-gui
- IRC: #monero-gui on Libera
- Translation platform (Weblate): translate.getmonero.org
- UI Design: Monero-GUI on Figma
- Our Vulnerability Response Process encourages responsible disclosure
- We are also available via HackerOne
Monero is a private, secure, untraceable, decentralised digital currency. You are your bank, you control your funds, and nobody can trace your transfers unless you allow them to do so.
Privacy: Monero uses a cryptographically sound system to allow you to send and receive funds without your transactions being easily revealed on the blockchain (the ledger of transactions that everyone has). This ensures that your purchases, receipts, and all transfers remain absolutely private by default.
Security: Using the power of a distributed peer-to-peer consensus network, every transaction on the network is cryptographically secured. Individual wallets have a 25 word mnemonic seed that is only displayed once, and can be written down to backup the wallet. Wallet files are encrypted with a passphrase to ensure they are useless if stolen.
Untraceability: By taking advantage of ring signatures, a special property of a certain type of cryptography, Monero is able to ensure that transactions are not only untraceable, but have an optional measure of ambiguity that ensures that transactions cannot easily be tied back to an individual user or computer.
This is the GUI for the core Monero implementation. It is open source and completely free to use without restrictions, except for those specified in the license agreement below. There are no restrictions on anyone creating an alternative implementation of Monero that uses the protocol and network in a compatible manner.
As with many development projects, the repository on Github is considered to be the "staging" area for the latest changes. Before changes are merged into that branch on the main repository, they are tested by individual developers in their own branches, submitted as a pull request, and then subsequently tested by contributors who focus on testing and code reviews. That having been said, the repository should be carefully considered before using it in a production environment, unless there is a patch in the repository for a particular show-stopping issue you are experiencing. It is generally a better idea to use a tagged release for stability.
Monero is a 100% community-sponsored endeavor. If you want to join our efforts, the easiest thing you can do is support the project financially. Both Monero and Bitcoin donations can be made to donate.getmonero.org if using a client that supports the OpenAlias standard.
The Monero donation address is: 888tNkZrPN6JsEgekjMnABU4TBzc2Dt29EPAvkRxbANsAnjyPbb3iQ1YBRk1UXcdRsiKc9dhwMVgN5S9cQUiyoogDavup3H
(viewkey: f359631075708155cc3d92a32b75a7d02a5dcf27756707b47a2b31b21c389501
)
The Bitcoin donation address is: 1KTexdemPdxSBcG55heUuTjDRYqbC5ZL8H
GUI development funding and/or some supporting services are also graciously provided by sponsors:
There are also several mining pools that kindly donate a portion of their fees, a list of them can be found on our Bitcointalk post.
See LICENSE.
Do you speak a second language and would like to help translate the Monero GUI? Check out Weblate, our localization platform, at translate.getmonero.org. Choose the language and suggest a translation for a string or review an existing one. The Localization Workgroup made a guide with step-by-step instructions for Weblate.
If you need help/support or any info you can contact the localization workgroup on the IRC channel #monero-translations (relayed on matrix/riot and MatterMost) or by email at translate[at]getmonero[dot]org. For more info about the Localization workgroup: github.com/monero-ecosystem/monero-translations
Packages are available for
- Arch Linux: monero-gui
- Debian: See the whonix/monero-gui repository
- Void Linux:
xbps-install -S monero-gui
- GuixSD:
guix package -i monero-gui
- macOS (homebrew):
brew install --cask monero-wallet
Packaging for your favorite distribution would be a welcome contribution!
Note: Qt 5.9.7 is the minimum version required to build the GUI.
-
Install Docker https://docs.docker.com/engine/install/
-
Clone the repository
git clone --branch master --recursive https://github.com/monero-project/monero-gui.git
*
master
- replace with the desired version tag (e.g.v0.17.1.9
) to build the release binaries. -
Prepare build environment
cd monero-gui docker build --tag monero:build-env-windows --build-arg THREADS=4 --file Dockerfile.windows .
*
4
- number of CPU threads to use -
Build
docker run --rm -it -v <MONERO_GUI_DIR_FULL_PATH>:/monero-gui -w /monero-gui monero:build-env-windows sh -c 'make depends root=/depends target=x86_64-w64-mingw32 tag=win-x64 -j4'
*
<MONERO_GUI_DIR_FULL_PATH>
- absolute path tomonero-gui
directory
*4
- number of CPU threads to use -
Monero GUI Windows static binaries will be placed in
monero-gui/build/x86_64-w64-mingw32/release/bin
directory
-
Install Docker https://docs.docker.com/engine/install/
-
Clone the repository
git clone --branch master --recursive https://github.com/monero-project/monero-gui.git
*
master
- replace with the desired version tag (e.g.v0.17.1.9
) to build the release binaries. -
Prepare build environment
cd monero-gui docker build --tag monero:build-env-linux --build-arg THREADS=4 --file Dockerfile.linux .
*
4
- number of CPU threads to use -
Build
docker run --rm -it -v <MONERO_GUI_DIR_FULL_PATH>:/monero-gui -w /monero-gui monero:build-env-linux sh -c 'make release-static -j4'
*
<MONERO_GUI_DIR_FULL_PATH>
- absolute path tomonero-gui
directory
*4
- number of CPU threads to use -
Monero GUI Linux static binaries will be placed in
monero-gui/build/release/bin
directory -
(Optional) Compare
monero-wallet-gui
SHA-256 hash to the one obtained from a trusted sourcedocker run --rm -it -v <MONERO_GUI_DIR_FULL_PATH>:/monero-gui -w /monero-gui monero:build-env-linux sh -c 'shasum -a 256 /monero-gui/build/release/bin/monero-wallet-gui'
*
<MONERO_GUI_DIR_FULL_PATH>
- absolute path tomonero-gui
directory
- Minimum Android 9 Pie (API 28)
- ARMv8-A 64-bit CPU
-
Install Docker https://docs.docker.com/engine/install/
-
Clone the repository
git clone --recursive https://github.com/monero-project/monero-gui.git
-
Prepare build environment
cd monero-gui docker build --tag monero:build-env-android --build-arg THREADS=4 --file Dockerfile.android .
*
4
- number of CPU threads to use -
Build
docker run --rm -it -v <MONERO_GUI_DIR_FULL_PATH>:/monero-gui -e THREADS=4 monero:build-env-android
*
<MONERO_GUI_DIR_FULL_PATH>
- absolute path tomonero-gui
directory
*4
- number of CPU threads to use -
Monero GUI APK will be placed in
monero-gui/build/Android/release/android-build
directory -
Deploy
- Using ADB (Android debugger bridge)
- Connect your device with USB and install Monero GUI APK with adb:
adb install build/Android/release/android-build/monero-gui.apk
- Troubleshooting:
adb devices -l adb logcat
- If using adb inside docker, make sure you did
docker run -v /dev/bus/usb:/dev/bus/usb --privileged
- Using a web server
Now it should be accessible through a web browser at
mkdir /usr/tmp cp build/Android/release/android-build/monero-gui.apk /usr/tmp docker run -d -v /usr/tmp:/usr/share/nginx/html:ro -p 8080:80 nginx
http://<your.local.ip>:8080/QtApp-debug.apk
- Using ADB (Android debugger bridge)
(Tested on Ubuntu 17.10 x64, Ubuntu 18.04 x64 and Gentoo x64)
- Install Monero dependencies
-
For Debian distributions (Debian, Ubuntu, Mint, Tails...)
sudo apt install build-essential cmake libboost-all-dev miniupnpc libunbound-dev graphviz doxygen libunwind8-dev pkg-config libssl-dev libzmq3-dev libsodium-dev libhidapi-dev libnorm-dev libusb-1.0-0-dev libpgm-dev libprotobuf-dev protobuf-compiler libgcrypt20-dev
-
For Gentoo
sudo emerge app-arch/xz-utils app-doc/doxygen dev-cpp/gtest dev-libs/boost dev-libs/expat dev-libs/openssl dev-util/cmake media-gfx/graphviz net-dns/unbound net-libs/ldns net-libs/miniupnpc net-libs/zeromq sys-libs/libunwind dev-libs/libsodium dev-libs/hidapi dev-libs/libgcrypt
-
For Fedora
sudo dnf install make automake cmake gcc-c++ boost-devel miniupnpc-devel graphviz doxygen unbound-devel libunwind-devel pkgconfig openssl-devel libcurl-devel hidapi-devel libusb-devel zeromq-devel libgcrypt-devel
- Install Qt:
Note: The Qt 5.9.7 or newer requirement makes some distributions (mostly based on debian, like Ubuntu 16.x or Linux Mint 18.x) obsolete due to their repositories containing an older Qt version.
The recommended way is to install 5.9.7 from the official Qt installer or compiling it yourself. This ensures you have the correct version. Higher versions can work but as it differs from our production build target, slight differences may occur.
The following instructions will fetch Qt from your distribution's repositories instead. Take note of what version it installs. Your mileage may vary.
-
For Ubuntu 17.10+
sudo apt install qtbase5-dev qt5-default qtdeclarative5-dev qml-module-qtqml-models2 qml-module-qtquick-controls qml-module-qtquick-controls2 qml-module-qtquick-dialogs qml-module-qtquick-xmllistmodel qml-module-qt-labs-settings qml-module-qt-labs-platform qml-module-qt-labs-folderlistmodel qttools5-dev-tools qml-module-qtquick-templates2 libqt5svg5-dev
-
For Gentoo
sudo emerge dev-qt/qtcore:5 dev-qt/qtdeclarative:5 dev-qt/qtquickcontrols:5 dev-qt/qtquickcontrols2:5 dev-qt/qtgraphicaleffects:5
-
Optional : To build the flag
WITH_SCANNER
-
For Ubuntu
sudo apt install qtmultimedia5-dev qml-module-qtmultimedia
-
For Gentoo
The qml USE flag must be enabled.
emerge dev-qt/qtmultimedia:5
-
-
Clone repository
git clone --recursive https://github.com/monero-project/monero-gui.git cd monero-gui
-
Build
make release -j4
*
4
- number of CPU threads to use
* AddCMAKE_PREFIX_PATH
enviroment variable to set a custom Qt install directory, e.g.CMAKE_PREFIX_PATH=$HOME/Qt/5.9.7/gcc_64 make release -j4
The executable can be found in the build/release/bin folder.
brew install boost hidapi zmq libpgm libsodium miniupnpc ldns expat libunwind-headers protobuf libgcrypt
- Install Qt:
brew install qt5
(or download QT 5.9.7+ from qt.io)
-
Grab an up-to-date copy of the monero-gui repository
git clone --recursive https://github.com/monero-project/monero-gui.git cd monero-gui
-
Start the build
make release -j4
*
4
- number of CPU threads to use
* AddCMAKE_PREFIX_PATH
enviroment variable to set a custom Qt install directory, e.g.CMAKE_PREFIX_PATH=$HOME/Qt/5.9.7/clang_64 make release -j4
The executable can be found in the build/release/bin
folder.
For building an application bundle see DEPLOY.md
.
The Monero GUI on Windows is 64 bits only; 32-bit Windows GUI builds are not officially supported anymore.
-
Install MSYS2, follow the instructions on that page on how to update system and packages to the latest versions
-
Open an 64-bit MSYS2 shell: Use the MSYS2 MinGW 64-bit shortcut, or use the
msys2_shell.cmd
batch file with a-mingw64
parameter -
Install MSYS2 packages for Monero dependencies; the needed 64-bit packages have
x86_64
in their namespacman -S mingw-w64-x86_64-toolchain make mingw-w64-x86_64-cmake mingw-w64-x86_64-boost mingw-w64-x86_64-openssl mingw-w64-x86_64-zeromq mingw-w64-x86_64-libsodium mingw-w64-x86_64-hidapi mingw-w64-x86_64-protobuf-c mingw-w64-x86_64-libusb mingw-w64-x86_64-libgcrypt
You find more details about those dependencies in the Monero documentation. Note that that there is no more need to compile Boost from source; like everything else, you can install it now with a MSYS2 package.
-
Install Qt5
pacman -S mingw-w64-x86_64-qt5
There is no more need to download some special installer from the Qt website, the standard MSYS2 package for Qt will do in almost all circumstances.
-
Install git
pacman -S git
-
Clone repository
git clone --recursive https://github.com/monero-project/monero-gui.git cd monero-gui
-
Build
make release-win64 -j4 cd build/release make deploy
*
4
- number of CPU threads to use
The executable can be found in the .\bin
directory.