in

Updated information thread regarding the scheduled protocol upgrade of March 9

Updated information thread regarding the scheduled protocol upgrade of March 9

**First and foremost, you should upgrade to v0.14 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 v0.14.0.2 released, GUI v0.14.0.0 released

Alternatively, you can use the Github link:

**CLI:** https://github.com/monero-project/monero/releases/tag/v0.14.0.2 // Released

**GUI:** https://github.com/monero-project/monero-gui/releases/tag/v0.14.0.0 // Released

Note that the release threads can be found here:

– [CLI v0.14.0.2](https://www.reddit.com/r/Monero/comments/aygyfp/cli_v01402_boron_butterfly_released/)

– [GUI v0.14.0.0](https://www.reddit.com/r/Monero/comments/ayshug/gui_v01400_boron_butterfly_released/)

In case you’re using the GUI, please take notice of the following:

>**This version, *if using your own (local) node*, requires a database conversion, which may take 5-10 minutes and the GUI will show that it’s `Disconnected` (or unable to connect) from the daemon (monerod). I’d advise to simply let it run and after the database conversion has completed the GUI will connect back to the daemon (monerod).**

————–

**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 9th of March 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.14.0.0 or GUI v0.14.0.0. The scheduled network upgrade introduces four major changes. First, [some](https://www.reddit.com/r/Monero/comments/av0cn3/is_there_anyone_who_can_explain_the_new_block/ehc1ib3/) [changes](https://www.reddit.com/r/Monero/comments/av0cn3/is_there_anyone_who_can_explain_the_new_block/ehbp2vu/) to the dynamic block size algorithm to fix the [big bang attack](https://www.reddit.com/r/Monero/comments/aj21yt/big_bang_attack_on_xmr/). Note that, consequently, the daemon (monerod) has to perform a database conversion. Fortunately, however, this conversion should be relatively fast and only take 5-10 minutes. Second, a third PoW tweak (CryptoNight-R) to curb the ASICs currently present on the network and further preserve ASIC resistance. As a result, miners will have to update their miners (i.e. mining software) as well. Third, a dummy encrypted payment ID is now added to each transaction to improve transaction homogeneity. Fourth, the development team simplified amount commitments by shrinking the size of amount encodings and using deterministic masks. These changes were deemed safe to apply by the Monero Research Lab. Additionally, the changes essentially entail the transaction format being upgraded to a v2 format.

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

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

Note that all changes have been discussed extensively in the developer, community, and research meetings, which can be read here:

https://www.getmonero.org/blog/

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

https://github.com/monero-project/meta/ (logs are posted in research meeting tickets)

Due to variance the scheduled network upgrade will take place on or around the 9th of March. 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](https://github.com/monero-project/monero/blob/release-v0.13/src/cryptonote_core/blockchain.cpp#L120-L121). That is:

> // version 10 starts from block 1788000, which is on or around the 9th of March, 2019. Fork time finalised on 2019-02-10.

Note that there technically will be two hard forks (i.e. one on approximately the 9th of March and one on the approximately the 10th of March). This provides a grace period on the network where transactions in the transaction pool that still use the v1 transaction format are allowed to be included in a block by miners. Fortunately, running v0.14.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](https://src.getmonero.org/resources/user-guides/verification-windows-beginner.html) for Windows and [here](https://src.getmonero.org/resources/user-guides/verification-allos-advanced.html) for Linux and Mac OS X.

**CLI:**

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

1. Download the new binaries (the `.zip` file (Windows) or the `tar.bz2` file (Mac OS X and Linux)) from [the official website](https://getmonero.org/downloads/) or [Github](https://github.com/monero-project/monero/releases/tag/v0.14.0.2).

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

3. Copy over the wallet files from the old directory (i.e. the v0.13.x.x directory).

4. Start `monerod` (**warning:** a database conversion is required, although it should be relatively fast) 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.14.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 to the dynamic block size algorithm to fix the [big bang attack](https://www.reddit.com/r/Monero/comments/aj21yt/big_bang_attack_on_xmr/). The conversion should be relatively fast though.

**GUI:**

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

1. Download the new binaries (the `.zip` file (Windows) or the `tar.bz2` file (Mac OS X and Linux)) from [the official website](https://getmonero.org/downloads/) or [Github](https://github.com/monero-project/monero-gui/releases/tag/v0.14.0.0).

2. 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.

3. Open `monero-wallet-gui`^1. It should automatically load your “old” wallet and you should be set for the upcoming scheduled network upgrade.

4. If you’re running a local node, the integrated daemon (monerod) will first have to convert your database to a new version. This may a few minutes and the GUI will 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 `DocumentsMonero<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. However, to reiterate, a database conversion is required, which may take 5-10 minutes and the GUI will show that it’s `Disconnected` from the daemon (monerod).

**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 (i.e. v0.14).

**Webwallets (MyMonero & XMRwallet):**

You don’t have to do anything, as MyMonero will be properly upgraded in advance of the scheduled network upgrade. In addition, it is presumed XMRwallet will be properly upgraded as well.

**Mobile wallets: (Monerujo, Cake, Xwallet, MyMonero, Edge wallet, Zelcore, and Coinomi)**

Its presumed that the third-party mobile wallets will release a new version in advance of the scheduled network upgrade such that the user is sufficiently prepared.

**Desktop wallets: (MyMonero, Exodus Eden, Zelcore, Coinomi)**

Its presumed that the third-party desktop wallets will release a new version in advance of the scheduled network upgrade such that the user is sufficiently prepared.

**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 third PoW tweak (i.e. CryptoNightR)).

# 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.14.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.

What do you think?

0 points
Upvote Downvote

Blockchain in Energy: Recent SEC Guidance on Tokenization

/r/Monero Weekly Discussion – April 13, 2019 – Use this thread for general chatter, basic questions, and if you’re new to Monero