@meyer9 meyer9 released this Mar 3, 2018 · 416 commits to master since this release

Assets 14

1.2.2 Release notes

THIS IS A MANDATORY UPDATE. UPGRADE YOUR MASTERNODES AND CLIENTS BEFORE BLOCK 250,000.

Phore Core version 1.2.2 is now available from:

https://phore.io/

Please report bugs using the issue tracker at github:

https://github.com/phoreproject/phore/issues

How to Upgrade the Phore Wallet

If you are running an older version, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions). Unless you already have a recent backup, take this opportunity to back up your wallet.dat, ideally to a USB key or another hard drive so that you will have a copy in case something happened to your hard drive. For Windows, by default the wallet.dat is located in %APPDATA%\Phore. For Macs, the default location is in ~/Library/Application Support/Phore.

Then run the installer (on Windows) or just copy over /Applications/Phore-Qt (on Mac) or phored/phore-qt (on Linux). No changes to other files are needed.

After upgrading your wallet, if you choose About Phore Core from the menus, the version number will start with: Phore Core version v3.0.5

We realize this does not say v1.2.2, but if you see that, you have the correct version. On some platforms including the Mac, if you Control-click on the Phore-qt icon and select Get Info, it will display v1.2.2 as the version.

How to Upgrade Phore Masternodes

There are two upgrade methods, depending on the way the masternode was installed. This is because the original installation instructions and the new installation script put files in different locations and have different ways of starting and stopping the Phore masternode daemon.

The new simpler installation method uses the vps script that automates most of the VPS installation steps. It also supports IPv6 and running multiple masternodes on the same VPS, if it has enough memory and other resources (the $5/month VPS option at Vultr should be capable of running 2-3 masternodes this way).

You also have the option of doing a new installation on a new VPS, changing the IP address in your controlling wallet. If you wish to switch installation methods, start with a new VPS, or combine multiple masternodes onto a single VPS, the masternode installation guide is pinned to the #masternodes channel in the Phore Discord, or is available here:

https://cdn.discordapp.com/attachments/373490053403377666/406626124203032586/Phore_Masternode_Installation.pdf

The instructions below are for upgrading your masternodes on their current VPS, keeping the configuration the same as it was:

Upgrading a masternode installed the original/manual way

  1. Log in to your VPS using PuTTY (Windows) or Terminal (Mac or Linux).
  2. Shut down your masternode:
    ./phore-cli stop
  3. Enter this command on one line:
    curl https://raw.githubusercontent.com/liray-unendlich/phore-masternode-automation/master/masternode-setup.sh | sh -s -- -u -v 1.2.2
  4. If you are upgrading the masternode after block 250000, you will need to resync the blockchain to get rid of any bad blocks that have been downloaded.
    /usr/local/bin/phore-cli stop
    /usr/local/bin/phored -resync
  5. Unlock your wallet, and restart the masternode from the controller wallet using the debug console command, replacing your-alias-name with the alias you used in your masternode.conf file:
    startmasternode alias false your-alias-name

If your masternode was named phore-mn01, the command to type in the wallet debug console is:
startmasternode alias false phore-mn01

If you have more than one masternode, repeat this process for each one.

NOTE: The script used for this upgrade places your executables (phore-cli, phore-tx, phored) in /usr/local/bin. If that is in your path, you can use commands like this to check on your masternode:

phore-cli getinfo or phore-cli masternode status

If it is not in your path, it won't find phore-cli or phored with that method, so you will have to use the whole path:

/usr/local/bin/phore-cli getinfo or /usr/local/bin/phore-cli masternode status

Upgrading a masternode installed with the VPS script

  1. Log in to your VPS using PuTTY (Windows) or Terminal (Mac or Linux).
  2. Shut down your masternode. If you have more than one masternode running on the same VPS, run this multiple times, changing n1 to n2 for the 2nd masternode, etc.:
    /usr/local/bin/phore-cli -conf=/etc/masternodes/phore_n1.conf stop
  3. Remove the previous version of the VPS script:
    rm -rf vps
  4. Enter this command on one line:
    git clone https://github.com/phoreproject/vps && cd vps && sudo ./install.sh -p phore -u
  5. If you are upgrading the masternode after block 250000, you will need to resync the blockchain to get rid of any bad blocks that have been downloaded deleting the blocks and chainstate folders will cause this to happen on startup.
    rm -rf /var/lib/masternodes/phore1/blocks && rm -rf /var/lib/masternodes/phore1/chainstate
  6. Launch the Phore masternode daemon(s):
    /usr/local/bin/activate_masternodes_phore
  7. Check your masternode to see that it has caught up to the latest block, that you can see when you hover your mouse over the checkmark in the lower right corner of your wallet. To find out the block on your masternode, type:
    /usr/local/bin/phore-cli -conf=/etc/masternodes/phore_n1.conf getinfo | grep blocks
    When the masternode is on the latest block, continue.
  8. Unlock your controller wallet, and restart the masternode using the debug console command, replacing your-alias-name with the alias you used in your masternode.conf file:
    startmasternode alias false your-alias-name

1.2.2 changelog

  • Updated chain parameters in response to this governance proposal.
    • Updated development rewards to a constant 1 PHR per block.
    • Updated block reward schedule
  • Fixed bug with mempoolnotify important for marketplace launch
  • Updated dns seeding system to be more decentralized.

Credits

meyer9 for work on the code
tohsnoom for setting up a DNS seed

As well as the entire Phore team!