Monero

Post-Mortem of find_and_save_rings() bug

Tue, 26 Aug 2025 00:00:00 GMT

Quick Facts

Severity: HIGH if using untrusted remote daemon, MEDIUM otherwise
Affected versions: GUI/CLI wallet versions v0.12.0.0 to v0.18.4.1
Impact: Sends TXIDs of outgoing transactions to daemon after first time loading wallet from file, reducing sender anonymity
Fix: Update Monero CLI / GUI to v0.18.4.2
Workaround: TBD

Introduction

In 2018, a persistent "ring database" was added to wallet2 to solve a sender privacy problem with forks of Monero. If an enote was received before a fork occurs, and a wallet tries spending that enote after the fork occurs on both forks, the same key image will appear in the input to both of those transactions on the different forks. By necessity, one of the ring members must be the same between those two forks (the "true spend"). If no other ring members are shared between those two inputs, but both ring signatures verify correctly, then an external observer can pin which ring member is the "true spend". This destroys sender anonymity. To combat this, a ring database is populated in a user directory which maps spent key images to their ring signatures. Then, if a forked wallet tries to spend an enote already spent on another chain, it will lookup up ring signature data from the local ring database, and try to re-use as many decoys from that ring as possible. This reduces the sender anonymity risk for spending enotes across different forks.

There are basically three ways that the ring database can be populated: the ring indices from transactions can be added from 1) scanned outgoing transactions during a normal chain refresh 2) transactions submitted to the network from that wallet and 3) already-known outgoing transactions after explicitly fetching them from the daemon. The method tools::wallet2::find_and_save_rings() implemented the latter of the three schemes. Its purpose was to populate the ring database for already-existing wallets created before the v0.12.0.0 release after which rings were added during refresh, without having to rescan the whole blockchain. However, as it turns out, tools::wallet2::find_and_save_rings() was called more often than it should have given its niche purpose.

Reproducing

Here are steps to reproduce the privacy leak using the CLI wallet (assumes working daemon connection):

Create wallet (same-device keys, hardware wallet keys, multisig, etc), remember seed phrase if applicable
Receive an enote, spend said enote, wait 10 blocks
Delete (or move) wallet files, both keys and cache
Restore wallet and refresh before saving
Close wallet
(Optional) Open packet inspection software (e.g. Wireshark) and begin logging RPC traffic (using --daemon-ssl disabled helps here)
Re-open wallet
Daemon now has list of confirmed outgoing transactions ☹️
(Optional) If using packet inspection software, filter using the string gettransactions
To repeat, go to step 3

Technical explanation

tools::wallet2::find_and_save_rings() was called unconditionally when loading a wallet from file, inside wallet2::load(). However, it would return early if the member field m_ring_history_saved was equal to true. At the end of the call to tools::wallet2::find_and_save_rings(), m_ring_history_saved is set to true. However, initializing a wallet2 object sets m_ring_history_saved to false. This field, m_ring_history_saved, is also serialized into the wallet cache file. So, after a wallet's first load, if there are scanned outgoing transactions in the cache during the first save, m_ring_history_saved is set to false so tools::wallet2::find_and_save_rings() proceeds. It grabs all TXIDs from outgoing transactions (stored in field member m_confirmed_txs), and performs a /gettransactions RPC call with that list of TXIDs to the daemon, leaking its outgoing transaction history. The RPC call is made without discriminating whether the daemon is marked as trusted or not.

Let's say that you delete the cache file and keep keys file. Note that while tools::wallet2::find_and_save_rings() is still called on load, the /gettransactions RPC call is skipped since a missing cache file causes m_confirmed_txs to be empty. m_ring_history_saved is still set to true at the end of the call, and so the RPC call will never be made henceforth. So merely deleting the cache file won't trigger the vulnerability, the keys file also needs to not be present.

Vulnerability introduction commit (master branch): 5f146873
Vulnerability fix commit (master branch): dc350f35

Privacy implications with ring signatures

When the aforementioned RPC call is triggered, the daemon receives a list of TXIDs of your wallets outgoing transactions. If a malicious operator of said daemon knows the receiver of the outputs in the outgoing transactions, then the operator can tie that wallet as sending funds to a certain receiver. Furthermore, because of the current ring size and size of the the blockchain, the probability of selecting your own owned outputs as a decoy in your own ring signatures is small. As such, a smart malicous operator, with a list of your outgoing TXIDs, can inspect the ring members of your going transactions and cross-reference if any of the members are outputs of transactions in the TXID list. If so, the operator can guess with high accuracy that a certain change output was spent in a certain ring in a later outgoing transaction. This allows the operator to construct a probabilistic transaction graph, without amount information, for a wallet's funds after entering possession.

FCMP++ Optimization Competition Results

Wed, 27 Aug 2025 00:00:00 GMT

We held a contest to optimize two libraries used in Monero's proposed upgrade to FCMP++: helioselene and ec-divisors. We have officially declared the winners of the contest!

EC Divisors (250 XMR prize)

Winner: @fabrizio-m

Fabrizio sped up the divisors library by over 95%. You can see the excellent submission here.

ec-divisors is a library implementing the calculation of divisors of elliptic curve points. These lead to efficient verification of scalar multiplications, as posited by Liam Eagen. FCMP++ uses EC Divisors to improve efficiency generally. This competition was focused on optimizing divisor construction, which affects transaction construction.

Managing slow divisors construction was a pain point for the FCMP++ integration. Fabrizio's 95%+ improvement effectively renders divisors construction negligible. Thanks to Fabrizio, we can now significantly simplify the final FCMP++ integration, and improve the user experience.

helioselene (100 XMR 1st place prize, 30 XMR 2nd place prize)

1st place: @lederstrumpf
2nd place: @rafael-xmr

Lederstrumpf's submission achieved a weighted speed-up of 22% on an AMD Ryzen 5600G, and improved the weighted WASM cycle count by 39%. The judges unanimously declared Lederstrumpf's submission the winner! Lederstrumpf's submission was the strongest foundation to build on. You can see the excellent submission here. As of this writing, @kayabaNerve has already improved on the submission here.

helioselene is a library implementing two curves, "Helios" and "Selene," which form a curve cycle towering Ed25519. Using a "tower cycle" over Ed25519 allows Monero to re-use the existing anonymity set while upgrading to FCMP++. This library is a critical component used in all aspects of FCMP++. Optimizing this library will therefore benefit all user-facing components of FCMP++ (daemon sync, wallet sync, and transaction construction).

Although not part of the official contest rules, we decided to award a 2nd place prize to Rafael, since we unanimously agreed Rafael's submission was 2nd best. Had we not received a submission from Lederstrumpf, we would have had an excellent submission to fall back on here. As such, we sought to reward Rafael's strong effort.

We received a number of quality submissions to this contest, and want to thank all contestants for participating! You can read more on our rationale for selecting the winner here.

What we learned

Form stricter bounds on exactly what code can be modified

Some code in a repo required for tests / benchmarks to run might not be in scope of the competition. Be as clear about which code is out of scope as possible. Explicitly tell contestants that modifiying certain code will be disqualifying.

Form stricter API requirements

Similar to the previous point, be crystal clear about the requirements the API of the code must take on and if it should even be allowed to be modified. Preferably provide downstream code that the API must compile and function correctly with.

Present concrete architectures and toolchains for which the code must run in constant-time

Code runs in constant-time or doesn't on specific architectures and toolchains. For example, LLVM to x86 generates variable-time code for u128 arithmetic in Rust, but constant-time code on x86_64. Give contestants examples of specific toolchains and architectures for which the code must compile to constant-time.

Allocate time for review and 2nd phase

No matter how well you think you define the competition rules, there may be scenarios which crop up where there was widespread confusion about the rules. There may be multiple submissions which have a lot of good work in them, but are in the gray area of validity. A review phase allows judges to clarify rules with contestants and refine submissions, and planning for this ahead of time helps to avoid misunderstandings.

Allocate time for deadline extensions

This one is pretty self-explanatory. Sometimes you need a deadline extension for unforseen circumstances, so allocate time for it.

Make a policy for non-1st place prizes

In a situation where anonymous submissions are allowed, 2nd place prizes can be gamed very easily. Also, game theory states that for a lot of competitions, the best incentive structure is winner-take-all. However, in the case where two submitters are certainly distinct competitors, and both submissions are close in quality, a 2nd place prize may be warranted. This is doubly true when parts of the code of the non-1st place are to be used in production code. Allocate funds for this scenario before the competition, but make sure to clarify that awarding such a prize is strictly up to the judgement of the judges.

Clarify rules for vendored dependencies

If you want to make rules about dependencies in the competition, make sure to specify rules about heavily modified and/or vendored dependencies before the start of the competition.

Spend more time marketing competition in specific circles where people do code competitions

There was a lot of good outreach for the FCMP++ competition, but some of the most fruitful outreach was to circles where there are already a lot of people doing coding/crypto competitions, who aren't necessarily involved in the Monero sphere.

Make sure that submitters always license their code under a permissive license

MIT, BSD, or even GPL, etc.

Setup an optional direct channel of communication for the contestants

Before the competiton starts, setup an offical, but optional, method of communication that lets judges push rule updates, feedback, announcements, etc to contestants. Otherwise, scrambling to find and message each contestant gets hectic very quickly.

Monero 0.18.4.2 'Fluorine Fermi' released

Tue, 26 Aug 2025 00:00:00 GMT

Overview

This is the v0.18.4.2 release of the Monero software. This is a recommended release that fixes a privacy leak when using a malicious remote node.

Some highlights of this release are:

Wallet: fix privacy leak with malicious remote node (#10015). For a detailed report, read Post mortem of find_and_save_rings() bug
Daemon: more accurate connection count (#10047)
Minor bug fixes and improvements

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 7 people who worked to put out 12 commits containing 39 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
cho-m
vtnerd
woodser
jeffro256
selsta
j-berman

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-win-x64-v0.18.4.2.zip, 14dd5aa11308f106183dd7834aa200e74ce6f3497103973696b556e893a4fef2
monero-win-x86-v0.18.4.2.zip, 934d9dbeb06ff5610d2c96ebe34fa480e74f78eaeb3fa3e47d89b7961c9bc5e0
monero-mac-x64-v0.18.4.2.tar.bz2, b1b1b580320118d3b6eaa5575fdbd73cf4db90fcc025b7abf875c5e5b4e335c1
monero-mac-armv8-v0.18.4.2.tar.bz2, 9b98da6911b4769abef229c20e21f29d919b11db156965d6f139d2e1ad6625c2
monero-linux-x64-v0.18.4.2.tar.bz2, 41d023f2357244ea43ee0a74796f5705ce75ce7373a5865d4959fefa13ecab06
monero-linux-x86-v0.18.4.2.tar.bz2, 03e77a4836861a47430664fa703dd149a355b3b214bc400b04ed38eb064a3ef0
monero-linux-armv8-v0.18.4.2.tar.bz2, a39530054dac348b219f1048a24ca629da26990f72cf9c1f6b6853e3d8c39a79
monero-linux-armv7-v0.18.4.2.tar.bz2, ecb2577499a3b0901d731e11d462d3fadcd70095f3ab0def0c27ee64dc56b061
monero-linux-riscv64-v0.18.4.2.tar.bz2 18492ace80bf8ef2f44aa9a99b4f20adf00fd59c675a6a496211a720088d5d1a
monero-android-armv8-v0.18.4.2.tar.bz2, 3b248c3201f028205915403b4b2f173df0dd8bf47eeb268fd67a4661251469d3
monero-android-armv7-v0.18.4.2.tar.bz2, 6122f0bcaca12d5badd92002338847d16032f6d52d86155c203bcb67d4fe1518
monero-freebsd-x64-v0.18.4.2.tar.bz2, b4e2b7de80107a1b4613b878d8e2114244b3fb16397821d69baa72d9b0f8c8d5

A GPG-signed list of the hashes is at https://www.getmonero.org/downloads/hashes.txt and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero GUI 0.18.4.2 'Fluorine Fermi' released

Tue, 26 Aug 2025 00:00:00 GMT

Overview

This is the v0.18.4.2 release of the Monero GUI software. This is a recommended release that fixes a privacy leak when using a malicious remote node.

The latest CLI release notes can be found on the precedent blog post

Some highlights of this release are:

Fix privacy leak with malicious remote node. For a detailed report, read Post mortem of find_and_save_rings() bug
Add background sync when locked functionality (#4050)
Update P2Pool to v4.9.1, fix Linux permission bug (#4490)
Add P2Pool nano sidechain (#4482)
Minor bug fixes

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 7 people who worked, to put out 12 commits containing 290 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

luigi1111
tobtoht
nahuhh
j-berman
SChernykh
selsta
xihuwenhua

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

A complete guide for the GUI wallet is included in the archives, but an online version is available.

Download Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-gui-win-x64-v0.18.4.2.zip, 4daff8850280173d46464ba9a9de7f712228ad1ef76a1c4954531e4fd2b86d86
monero-gui-install-win-x64-v0.18.4.2.exe, 9d6e87add7e3ac006ee34c13c4f629252595395f54421db768f72dc233e94ea8
monero-gui-mac-x64-v0.18.4.2.dmg, 16abadcbd608d4f7ba20d17a297f2aa2c9066d33f6f22bf3fcdca679ab603990
monero-gui-mac-armv8-v0.18.4.2.dmg, 3dfee5c5d8e000c72eb3755bf0eb03ca7c5928b69c3a241e147ad22d144e00a7
monero-gui-linux-x64-v0.18.4.2.tar.bz2, e4fcdea3f0ff27c3616a8a75545f42a4e4866ea374fa2eeaa9c87027573358ea

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero GUI 0.18.4.3 'Fluorine Fermi' released

Wed, 08 Oct 2025 00:00:00 GMT

Overview

This is the v0.18.4.3 release of the Monero GUI software. This is a highly recommended release that enhances protection against spy nodes when using a local node.

The latest CLI release notes can be found on the precedent blog post

Some highlights of this release are:

Add support for Ledger Flex (#4494)
Update Qt to 5.15.17 (#4498)
Update P2Pool to v4.11 (#4505)
Minor bug fixes

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 4 people who worked, to put out 18 commits containing 61 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

luigi1111
tobtoht
SChernykh
selsta

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

A complete guide for the GUI wallet is included in the archives, but an online version is available.

Download Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-gui-win-x64-v0.18.4.3.zip, dc9531cb4319b37b2c2dea4126e44a0fe6e7b6f34d278ccf5dd9ba693e3031e0
monero-gui-install-win-x64-v0.18.4.3.exe, 7b9255c696a462a00a810d9c8f94e60400a9e7d6438e8d6a8b693e9c13dca9ab
monero-gui-mac-x64-v0.18.4.3.dmg, 27243b01f030fdae68c59cae1daf21f530bbadeaf10579d2908db9a834191cee
monero-gui-mac-armv8-v0.18.4.3.dmg, 68ea30db32efb4a0671ec723297b6629d932fa188edf76edb38a37adaa3528e6
monero-gui-linux-x64-v0.18.4.3.tar.bz2, 0bd84de0a7c18b2a3ea8e8eff2194ae000cf1060045badfd4ab48674bc1b9325

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero 0.18.4.3 'Fluorine Fermi' released

Wed, 08 Oct 2025 00:00:00 GMT

Overview

This is the v0.18.4.3 release of the Monero software. This is a highly recommended release that enhances protection against spy nodes.

Some highlights of this release are:

Wallet: increase batch subaddress creation limit to match RPC (#10098)
Wallet: warn instead of throw when RingDB doesn't include spend (#10150)
Daemon: improved peer selection with /24 subnet deduplication to disadvantage 'spy nodes' (#10113)
Daemon: add max_block_count field to getblocks.bin RPC request (#9901)
Daemon: send ZMQ miner notifications after txpool additions (#10104)
Daemon: seed node maintenance (#10105, #10112, #10115)
Daemon: fix on_getblockhash error return on too high height (#10125)
RPC: allow creating more than 64 addresses at once (#10096)
Fix logging deadlock (#10066)
Minor bug fixes and improvements

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 13 people who worked to put out 36 commits containing 253 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
vtnerd
0xFFFC0000
nahuhh
moneromooo
WeebDataHoarder
jeffro256
Gingeropolous
lalanza808
rbrunner7
hinto-janai
selsta
j-berman

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-win-x64-v0.18.4.3.zip, bd9f615657c35d2d7dd9a5168ad54f1547dbf9a335dee7f12fab115f6f394e36
monero-win-x86-v0.18.4.3.zip, e642ed7bbfa34c30b185387fa553aa9c3ea608db1f3fc0e9332afa9b522c9c1a
monero-mac-x64-v0.18.4.3.tar.bz2, a8d8273b14f31569f5b7aa3063fbd322e3caec3d63f9f51e287dfc539c7f7d61
monero-mac-armv8-v0.18.4.3.tar.bz2, bab9a6d3c2ca519386cff5ff0b5601642a495ed1a209736acaf354468cba1145
monero-linux-x64-v0.18.4.3.tar.bz2, 3a7b36ae4da831a4e9913e0a891728f4c43cd320f9b136cdb6686b1d0a33fafa
monero-linux-x86-v0.18.4.3.tar.bz2, e0b51ca71934c33cb83cfa8535ffffebf431a2fc9efe3acf2baad96fb6ce21ec
monero-linux-armv8-v0.18.4.3.tar.bz2, b1cc5f135de3ba8512d56deb4b536b38c41addde922b2a53bf443aeaf2a5a800
monero-linux-armv7-v0.18.4.3.tar.bz2, 3ac83049bc565fb5238501f0fa629cdd473bbe94d5fb815088af8e6ff1d761cd
monero-linux-riscv64-v0.18.4.3.tar.bz2 95baaa6e8957b92caeaed7fb19b5c2659373df8dd5f4de2601ed3dae7b17ce2f
monero-android-armv8-v0.18.4.3.tar.bz2, 1aebd24aaaec3d1e87a64163f2e30ab2cd45f3902a7a859413f6870944775c21
monero-android-armv7-v0.18.4.3.tar.bz2, 4e1481835824b9233f204553d4a19645274824f3f6185d8a4b50198470752f54
monero-freebsd-x64-v0.18.4.3.tar.bz2, ff7b9c5cf2cb3d602c3dff1902ac0bc3394768cefc260b6003a9ad4bcfb7c6a4

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero 0.18.4.4 'Fluorine Fermi' released

Fri, 14 Nov 2025 00:00:00 GMT

Overview

This is the v0.18.4.4 release of the Monero software. This is a recommended release that fixes a bug with Ledger hardware wallet when rejecting secret view key export.

Some highlights of this release are:

Ledger: make secret view key export mandatory (#10195)
Wallet: identify spends in pool when scanning (#10153)
Daemon: relay empty fluffy block on found block (#10206)
Daemon: correct txpool weight miscalculation in edge case (#10204)
Daemon: refine sync height selection logic (#10202)
Additional logging deadlock fixes (#10194)
Minor bug fixes and improvements

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 4 people who worked to put out 14 commits containing 286 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
0xFFFC0000
selsta
j-berman

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-win-x64-v0.18.4.4.zip, 7eb3b87a105b3711361dd2b3e492ad14219d21ed8fd3dd726573a6cbd96e83a6
monero-win-x86-v0.18.4.4.zip, a148a2bd2b14183fb36e2cf917fce6f33fb687564db2ed53193b8432097ab398
monero-mac-x64-v0.18.4.4.tar.bz2, af3d98f09da94632db3e2f53c62cc612e70bf94aa5942d2a5200b4393cd9c842
monero-mac-armv8-v0.18.4.4.tar.bz2, 645e9bbae0275f555b2d72a9aa30d5f382df787ca9528d531521750ce2da9768
monero-linux-x64-v0.18.4.4.tar.bz2, 7fe45ee9aade429ccdcfcad93b905ba45da5d3b46d2dc8c6d5afc48bd9e7f108
monero-linux-x86-v0.18.4.4.tar.bz2, 8c174b756e104534f3d3a69fe68af66d6dc4d66afa97dfe31735f8d069d20570
monero-linux-armv8-v0.18.4.4.tar.bz2, b9daede195a24bdd05bba68cb5cb21e42c2e18b82d4d134850408078a44231c5
monero-linux-armv7-v0.18.4.4.tar.bz2, 2040dc22748ef39ed8a755324d2515261b65315c67b91f449fa1617c5978910b
monero-linux-riscv64-v0.18.4.4.tar.bz2 c939ea6e8002798f24a56ac03cbfc4ff586f70d7d9c3321b7794b3bcd1fa4c45
monero-android-armv8-v0.18.4.4.tar.bz2, eb81b71f029884ab5fec76597be583982c95fd7dc3fc5f5083a422669cee311e
monero-android-armv7-v0.18.4.4.tar.bz2, 7c2ad18ca3a1ad5bc603630ca935a753537a38a803e98d645edd6a3b94a5f036
monero-freebsd-x64-v0.18.4.4.tar.bz2, bc539178df23d1ae8b69569d9c328b5438ae585c0aacbebe12d8e7d387a745b0

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero GUI 0.18.4.5 'Fluorine Fermi' released

Wed, 07 Jan 2026 00:00:00 GMT

Overview

This is the v0.18.4.5 release of the Monero GUI software. This release fixes a bug with Ledger hardware wallet.

The latest CLI release notes can be found on the precedent blog post

Some highlights of this release are:

Fix Ledger Monero app crash (#4534)
Add support for Ledger Nano Gen5 (#4539)
Update P2Pool to v4.13 (#4543)
Improve macOS dark mode support (#4537)
Minor bug fixes

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 5 people who worked, to put out 12 commits containing 25 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
SChernykh
plowsof
selsta
nabijaczleweli

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

A complete guide for the GUI wallet is included in the archives, but an online version is available.

Download Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-gui-win-x64-v0.18.4.5.zip, 9f3cf22fdb12cec1df6b1cb4cbe78d48457d68cbccdc46a82920a167885a988c
monero-gui-install-win-x64-v0.18.4.5.exe, 4d0cefe9d639bf2a31c02470c53d2f01c09d31165cedcc6eba184f1ccc7ed196
monero-gui-mac-x64-v0.18.4.5.dmg, aa1b818b7dea2a6315b7a25216e8661b5d4378d1823aa8747c8b39aac59232a0
monero-gui-mac-armv8-v0.18.4.5.dmg, 6b10e9336d9eb804f518a3815152e236ff5615fac3578a445500d92c572949c9
monero-gui-linux-x64-v0.18.4.5.tar.bz2, 6200d97615f23a3701c2cc51da3e9472ccd71561c259ca62f60030ef40ce785c

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero GUI 0.18.4.4 'Fluorine Fermi' released

Fri, 14 Nov 2025 00:00:00 GMT

Overview

This is the v0.18.4.4 release of the Monero GUI software. This is a recommended release that fixes a bug with Ledger hardware wallet when rejecting secret view key export.

The latest CLI release notes can be found on the precedent blog post

Some highlights of this release are:

Fix Ledger hardware wallet bug when rejecting secret view key export
Update P2Pool to v4.12 (#4519)
Minor bug fixes

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 3 people who worked, to put out 6 commits containing 23 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
SChernykh
selsta

Download

The new binaries can be downloaded from the Downloads page or from the direct links below.

A complete guide for the GUI wallet is included in the archives, but an online version is available.

Download Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-gui-win-x64-v0.18.4.4.zip, b96faa56aa77cabed1f31f3fc9496e756a8da8c1124da2b9cb0b3730a8b6fbd9
monero-gui-install-win-x64-v0.18.4.4.exe, 4c81c8e97bd542daa453776d888557db1ceb2a718d43f6135ad68b12c8119948
monero-gui-mac-x64-v0.18.4.4.dmg, 811df70811a25f31289f24ebc0edc8f7648670384698d4c768bac5c2acbf2026
monero-gui-mac-armv8-v0.18.4.4.dmg, a6f071719c401df339dba2d43ec6fffe103fda3e1df46f354b2496f34bb61cc4
monero-gui-linux-x64-v0.18.4.4.tar.bz2, e45cb3fa9d972d67628cfed6463fb7604ae1414a11ba449f5e2f901c769ac788

Two guides are available to guide you through the verification process: Verify binaries on Windows (beginner) and Verify binaries on Linux, Mac, or Windows command line (advanced).

Monero 0.18.4.5 'Fluorine Fermi' released

Wed, 07 Jan 2026 00:00:00 GMT

Overview

This is the v0.18.4.5 release of the Monero software. This release fixes a bug with Ledger hardware wallet.

Some highlights of this release are:

Ledger: fix Ledger Monero app crash (#10234)
Ledger: add support for Ledger Nano Gen5 (#10243)
Daemon: fix race condition causing dropped connections during sync (#10257)
Wallet: fix edge case where key images remain marked unspent (#10255)
Improve terminal color detection (#10268)
Minor bug fixes and improvements

The complete list of changes is available on GitHub, along with the source code.

Contributors for this Release

This release was the direct result of 7 people who worked to put out 16 commits containing 76 new lines of code. We'd like to thank them very much for their time and effort. In no particular order, they are:

tobtoht
plowsof
nahuhh
selsta
laanwj
iamamyth
j-berman

Download

The new binaries can be downloaded from the [Downloads page]({{ site.baseurl }}/downloads/#cli) or from the direct links below.

Hashes

If you would like to verify that you have downloaded the correct file, please use the following SHA256 hashes:

monero-win-x64-v0.18.4.5.zip, a58132eefdecf6bd5443ae52fc15c0c371499de17223667173e5c81d12bfc2c5
monero-win-x86-v0.18.4.5.zip, 6a0eff6b06fe9b1372a64744900bfe19b47a532b6678d6f7055c2de9999b58d1
monero-mac-x64-v0.18.4.5.tar.bz2, b92a2cebde86bf87ebcdfa9cab8e20ae4b3697798058c3de71945267f361a984
monero-mac-armv8-v0.18.4.5.tar.bz2, f6b91dd7cb06483941945e6a1dc455ed80360092c138a1d1af53dc31985bd8d8
monero-linux-x64-v0.18.4.5.tar.bz2, 423b49f3658e29f70a1d971667dec924c7ee7a107cfc93440456e28500b471a6
monero-linux-x86-v0.18.4.5.tar.bz2, 9960aba30ab2ffc3450a4865e707a60615661ae5c32f3b90da74f1c0a38e4bc0
monero-linux-armv8-v0.18.4.5.tar.bz2, a1667e15307f0dfce2f25f882238c432aee14884219ff0d0be07d7bee959a903
monero-linux-armv7-v0.18.4.5.tar.bz2, 42fbcbcf678794d6b104134bb7218093d6aa2764cc9cfa6fad404a4648a7c38a
monero-linux-riscv64-v0.18.4.5.tar.bz2 ed06d510dc53412362fa22a2149d709eb3b60f973583ebf33bbfbc9edc58f2ab
monero-android-armv8-v0.18.4.5.tar.bz2, 4d48830d0d6494b27bf1144b9546e5e7bccc7eef0f6991a16ae2bf6ac71a69d9
monero-android-armv7-v0.18.4.5.tar.bz2, 3cd6611c5c33ae4c10e52698826560bbb17e00cf2f8a2d7f61e79d28f0f36ef6
monero-freebsd-x64-v0.18.4.5.tar.bz2, a2e924a2293e1d0c192f6e50748dcbcbb58dd9d5ad2b6733ffccefad37c556cf

A GPG-signed list of the hashes is at [https://www.getmonero.org/downloads/hashes.txt]({{ site.baseurl_root }}/downloads/hashes.txt) and should be treated as canonical, with the signature checked against the appropriate GPG key in the source code (in /utils/gpg_keys). To ensure that the files you download are those originally posted by the maintainers, you should both check that the hashes of your files match those on the signed list, and that the signature on the list is valid.

Two guides are available to guide you through the verification process: [Verify binaries on Windows (beginner)]({{ site.baseurl }}/resources/user-guides/verification-windows-beginner.html) and [Verify binaries on Linux, Mac, or Windows command line (advanced)]({{ site.baseurl }}/resources/user-guides/verification-allos-advanced.html).