Jump to content


  • entries
  • comment
  • views

Monero will undergo a network upgrade on 16th July, 2022




The next network upgrade will take place on 16th July, 2022 (block 2,668,888). Network upgrades are technically hard-forks and require all participants in the Monero network to update their software. The new software (v0.18 "Fluorine Fermi") will be released one month before the network upgrade, on the ~16th of June.

This network upgrade will introduce important new features like:

  • A ring-size increase from 11 to 16 – the largest ever absolute increase in the base anonymity set (read: plausible deniability, or base privacy) – of every transaction on the network
  • Upgraded Bulletproofs algorithm, "Bulletproofs+", which will reduce the typical transaction size by ~5-7% and improve typical verification performance by ~5-7%, making every transaction lighter and faster
  • View tags, a brilliant way to reduce wallet sync times by 30-40%
  • Fee changes, improving the security and resilience of the network to rapid changes in the fee market or attacks by malicious entities

The complete list of changes and improvements will be released along with the new binaries.

The logs of the meeting where the dates of the network upgrade were decided are available on Github.

To learn more about how Monero uses hard-forks to upgrade the network, you can read this article from LocalMonero: "How Monero Uses Hard-Forks to Upgrade the Network"

Common questions

Q: Hard-fork? Does this mean there will be a split and a new coin will be created?
A: No. Hard-forks in Monero are made to improve the base protocol, and are non-contentious. There will be no split and no new coin will be created.

Q: What do I have to do to be prepared for this upgrade?
A: A new release will be announced before the network upgrade (around the 16th of June). You will only have to be using the updated software by the time the network upgrade occurs (16th July). To the end user, it will be like a simple software update.

Q: How do I update my wallet/node?
A: Detailed instructions will be posted along with the software update, but basically users will need to simply replace their previous software (monerod, monero-wallet-cli, monero-wallet-gui) with the new version. That's it.

Q: If I have my coins on a paper wallet, do I have to do something?
A: No. You will simply have to use an updated version of the Monero software when you will decide to move your coins.

Q: If I have my coins on a hardware wallet, do I have to do something?
A: Yes, you will need to update the Monero app or device firmware from the manufacturer once the appropriate update is available. Always be sure you go straight to the official website of the manufacturer to get these updates!

Q: Will there be any changes to the PoW algorithm?
A: No. The PoW algorithm will not be affected. Mining will work as before and miners won't need to update their software.

If you have further questions about the hard-fork, please reach out in r/MoneroSupport or via #monero on IRC or Matrix.

View the full article


Recommended Comments

There are no comments to display.

Add a comment...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • HashVault Latest Blocks

  • HashVault Stats

    • Global Hashrate
      369.77 GH
    • Avg Hashrate
      155.36 MH
    • Total Miners
    • Miners Paid
    • Total Payments
    • Total Hashes
      9.23 EX
    • Blocks Found
  • Posts

    • Buenos dias, no se me abre pool monero,des de hace dias. Me comenta al abrir k puede haver cambiado de pagina.alguien sabe algo
    • How can I tell HiveOS how many cores or threads I want to use for mining? My Ryzen 3600 has been lowered to 55w. In order to avoid clogging GPUs, I only want to use 11 threads for mining, with 1 thread for system-specific purposes. fnf
    • ./xmrig --url pool.hashvault.pro:80 --user *** --pass x -a cn-heavy/xhv * ABOUT XMRig/6.17.0 gcc/9.3.0 * LIBS libuv/1.43.0 OpenSSL/1.1.1m hwloc/2.7.0 * HUGE PAGES supported * 1GB PAGES disabled * CPU AMD EPYC-Rome Processor (1) 64-bit AES VM L2:0.5 MB L3:16.0 MB 1C/1T NUMA:1 * MEMORY 0.6/1.9 GB (31%) DIMM 0: 2 GB RAM @ 0 MHz DIMM 0 * MOTHERBOARD Vultr - VHP * DONATE 1% * ASSEMBLY auto:ryzen * POOL #1 pool.hashvault.pro:80 algo cn-heavy/xhv * COMMANDS hashrate, pause, resume, results, connection [2022-05-22 12:49:13.205] net use pool pool.hashvault.pro:80 [2022-05-22 12:49:13.205] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (7 tx) [2022-05-22 12:49:13.205] cpu use argon2 implementation AVX2 [2022-05-22 12:49:13.207] msr cannot read MSR 0xc0011020 [2022-05-22 12:49:13.207] msr FAILED TO APPLY MSR MOD, HASHRATE WILL BE LOW [2022-05-22 12:49:13.207] randomx init dataset algo rx/0 (1 threads) seed 6ac097ea635e9d1d... [2022-05-22 12:49:13.207] randomx not enough memory for RandomX dataset [2022-05-22 12:49:13.235] randomx failed to allocate RandomX dataset, switching to slow mode (27 ms) [2022-05-22 12:49:13.517] randomx dataset ready (282 ms) [2022-05-22 12:49:13.517] cpu use profile rx (1 thread) scratchpad 2048 KB [2022-05-22 12:49:13.519] cpu READY threads 1/1 (1) huge pages 100% 1/1 memory 2048 KB (1 ms) [2022-05-22 12:49:17.487] net new job from pool.hashvault.pro:80 diff 36000 algo rx/0 height 2628998 (52 tx) [2022-05-22 12:49:20.337] signal Ctrl+C received, exiting [2022-05-22 12:49:20.345] cpu stopped (8 ms I run xmrig and set the algorithm `cn-heavy/xhv`, but it still response `rx/0`.How to solve this problem?
    • Yes, I like the content of this article.  LOL Beans
    • Yeah, it does, but apparently it's not so transparent. So if we > mention that we'd better indicate in the same paragraph that you > probably don't actually want to use it. How about the attached?  UNO Online
  • Create New...