Preliminary information regarding the scheduled protocol upgrade of October 18

Note that this is a preliminary thread to inform community members about the upcoming scheduled protocol upgrade. This thread will be replaced once the binaries are released.

First and foremost, you should upgrade to v0.13 once the binaries are released or the tag has been created

The binaries, once they are released, can be found here:

https://getmonero.org/downloads/ // CLI released (ARMv7 & ARMv8 forthcoming), GUI released (new Mac OS X build forthcoming)

Alternatively, you can use the Github link:

CLI: https://github.com/monero-project/monero/releases/tag/v0.13.0.2 // Released (ARMv7 & ARMv8 forthcoming)

GUI: https://github.com/monero-project/monero-gui/releases/tag/v0.13.0.3 // Released (new Mac OS X build forthcoming)

Note that this is a scheduled and consensual network upgrade. Thus, unlike the BCH / BTC split, a new coin won't be created.

General information about the scheduled network upgrade

Approximately the 18th of October there will be a scheduled network upgrade on the Monero network. To be sufficiently prepared, a user, service, merchant, pool operator, or exchange should run CLI v0.13.0.2 or GUI v0.13.0.3. The scheduled network upgrade introduces four major changes. First and foremost, a new form of range proofs called Bulletproofs, which will replace the old Borromean range proofs and thereby significantly (i.e. by approximately 80%) reduce the transaction size (and thus fees). Second, a PoW tweak to curb any potential threat of ASICs and further preserve ASIC resistance. As a result, miners will have to update their miners (i.e. mining software) as well. Third, the minimum ring size is bumped to 11 (mixin 10) and will be static / fixed. Therefore, pool operators need to ensure that payouts use a ring size of 11 (mixin 10), otherwise they will get rejected by the network.

A blog about Monero compatible Bulletproofs can be found here:

https://getmonero.org/2017/12/07/Monero-Compatible-Bulletproofs.html

More information about the second PoW tweak can be found here:

https://github.com/monero-project/monero/pull/4218

The blog that set out a formal stance on ASIC resistance and the intention to maintain ASIC resistance can be found here:

https://getmonero.org/2018/02/11/PoW-change-and-key-reuse.html

In addition, more information about the ring size bump and the decision to make it a static parameter can be found here. Lastly, all changes have been discussed extensively in the last few dev meetings, which can be read here:

https://monerobase.com/wiki/Category:DevMeeting

Due to variance the scheduled network upgrade will take place on or around the 18th of October. There is, however, no specific date as the hard fork will be triggered by a specific blockheight. The specific blockheight for the hard fork can be found here. That is:

// version 8 starts from block 1685555, which is on or around the 18th of October, 2018. Fork time finalised on 2018-09-02.

Note that there technically will be two hard forks (i.e. one on approximately the 18th of October and one on the approximately the 19th of October). This provides a grace period on the network where transactions in the transaction pool that still use the old Borromean range proof are allowed to be included in a block by miners. Fortunately, running v0.13.0.0 ensures that one is sufficiently prepared for both hard forks.

How do I upgrade?

First and foremost, we encourage users to check the integrity of the binaries and verify that they were signed by Fluffypony's GPG key. A guide that walks you through this process can be found here for Windows and here for Linux and Mac OS X.

CLI: // ARMv7 and ARMv8 binaries are forthcoming

If you are using the CLI you ought to perform the following steps:

Download the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux)) from the official website or Github.

Extract the new binaries to a new directory of your liking.

Copy over the wallet files from the old directory (the one that contains the v0.12.0.0, v0.12.1.0, v0.12.2.0, or v0.12.3.0 binaries).

Start monerod and monero-wallet-cli (in case you have to use your wallet).

Note that a blockchain resync is not needed. Thus, if you open monerod-v.0.13.0.2, it will simply pick up where it left off. Note, however, that the daemon (monerod) will have to upgrade the database version to accommodate the changes required for the initial pruning implementation.

GUI: // new Mac OS X build forthcoming

If you are using the GUI you ought to perform the following steps:

Download the new binaries (the .zip file (Windows) or the tar.bz2 file (Mac OS X and Linux)) from the official website or Github.

Extract the new binaries to a new directory of your liking. This is the easiest and recommended way. Alternatively, however, you can overwrite the old binaries.

Open monero-wallet-gui1. It should automatically load your "old" wallet and you should be set for the upcoming scheduled network upgrade.

If you're running a local node, the integrated daemon (monerod) will first have to convert your database to a new version. This may take a few hours and the GUI may show that it's Disconnected. I'd advise to simply let it run and after the database conversion has completed the GUI will connect back to the daemon (monerod).

(1) On Linux you ought to start the GUI with the start-gui.sh script, i.e., ./start-gui.sh

(2) If, for some reason, the GUI doesn't automatically load your old wallet, you can open it as follows:

[1] On the second page of the wizard (first page is language selection) choose Open a wallet from file

[2] Now select your initial / original wallet. Note that, by default, the wallet files are located in Documents\Monero\<wallet-name> (Windows), Users/<username>/Monero/<wallet-name> (Mac OS X), or home/<username>/Monero/<wallet-name> (Linux).

Lastly, note that a blockchain resync is not needed, i.e., it will simply pick up where it left off. To reiterate, however, a database conversion is required, which may take a few hours and the GUI may show that it's Disconnected from the daemon (monerod).

Use the online HTML editor to maximize your web content composing efficiency.

Paper wallet:

You don't have to do anything. However, if you want to restore a wallet after the scheduled network upgrade, you need to use the new binaries.

MyMonero (web):

You don't have to do anything, as MyMonero will be properly upgraded in advance of the scheduled network upgrade.

MyMonero (desktop):

Its presumed that MyMonero will release a new version of the desktop wallet in advance of the scheduled network upgrade such that the user is sufficiently prepared. Basically, their new version has to use ring size 11 as minimum default, otherwise users will get their transactions rejected.

Mobile wallets:

Its presumed that the third-party mobile wallets (Monerujo, Cake, Xwallet, MyMonero, and Edge wallet) will release a new version in advance of the scheduled network upgrade such that the user is sufficiently prepared. Basically, their new version has to use ring size 11 as minimum default, otherwise users will get their transactions rejected.

Solo mining:

This process is similar to the CLI upgrade process. Thus, see aforementioned CLI steps.

Pool mining:

Your pool operator should upgrade to the new version. In addition, you should update your mining software to the latest version (the one that includes code to accommodate the second PoW tweak).

A call for community action

It's in our best interest that the upcoming scheduled network upgrade transits as smoothly as possible. Therefore, it is imperative that we, as community, contact economically sensitive nodes (exchanges and services) and inform them about the new version, the upcoming scheduled network upgrade, and that they should run v0.13.0.0 to be sufficiently prepared. A list of exchanges that have integrated Monero can be found here:

https://coinmarketcap.com/currencies/monero/#markets

In addition, services that have integrated Monero are, for example, XMR.to, Bisq, LocalMonero, and Morphtoken.

Lastly, if you have any questions or need any assistance with upgrading, please leave a comment in this thread and the community and I will help you out.