v1.3.2

1.3.2 Release notes

MANDATORY UPGRADE RELEASE

For anyone currently running v1.3.0 or v1.3.1 for either wallets or masternodes, is is very urgent to upgrade as soon as possible--we expect those versions will stop working as of block 433,160 which will occur around July 16th/17th depending on your timezone.

Most people are still running v1.2.2 (that shows up as v3.0.5-53 in About Phore Core), and they also need to upgrade, but have more time, since for them this change will not take effect until around August 11th (block 468,744).

Phore Core version 1.3.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 Wallets

Shut down the older version wallet, shut it down. Wait until it has completely
shut down (which might take a few minutes for older versions), then run the
installer (on Windows) or just copy over /Applications/Phore-Qt (on Mac) or
phored/phore-qt (on Linux).

How to Upgrade Masternodes

When upgrading masternodes, upgrade your controller wallet first. There are two ways people have installed masternodes, and to know how to upgrade, you first need to know which method yours was installed with. If you know you have more than one masternode running on a single VPS, then your masternodes were installed with the VPS installation script, and you can proceed to that section.

For those running a single masternode on a VPS, log in to your masternode VPS, and run the following command to see how the phored daemon is running:

ps -ef | grep phored

For server with an active masternode, that will print out the line you just ran (ps -ef etc.) and also one line that shows the running phored daemon command.

For masternodes installed with the VPS installation script, it will look like this:

mastern+ 20646 1 1 Jul12 ? 00:19:02 /usr/local/bin/phored -daemon -pid=/var/lib/masternodes/phore1/phore.pid -conf=/etc/masternodes/phore_n1.conf -datadir=/var/lib/masternodes/phore1

For masternodes installed with either the original type-in-all-the-commands way, or with liray-undelich's masternode automation script, it will look more like this:

root 20646 1 1 Jul12 ? 00:19:02 phored -daemon

There could be some variations, but the main difference that matters is the -conf=/etc/masternodes/phore_n1.conf part. That is a clear sign of the VPS installation script, and if nothing is there like that, it is one of the other methods. Proceed to either the VPS Installation Script or Other Installation Method section accordingly.

VPS Installation Script Method

For a single masternode installed with the VPS script method, upgrading the masternode can be done with the following commands after logging in to your VPS, with each command on a separate line, pressing Enter after each one:

rm -rf /root/vps
git clone https://github.com/phoreproject/vps
cd /root/vps
./install.sh -p phore -u

After that completes, then type:

systemctl restart phore_n1

To verify the status of the masternode after restarting with the upgraded version, type:

phore-cli --conf=/etc/masternodes/phore_n1.conf masternode status

If it says started successfully, that may be all you need to do. If it tells you that it is a hot node awaiting activation, go back to your controller wallet, open the debug console, and type the following, replacing "aliasname" with the name you used for your masternode:

startmasternode alias false "aliasname"

Other Installation Method

For anyone who used the phore-masternode-automation script, that also has upgrade instructions that can be found at the link below, which really is just logging in to your VPS and entering the following command all on one line:

curl -s https://raw.githubusercontent.com/liray-unendlich/phore-masternode-automation/master/masternode-setup.sh | bash -s -- -u -v 1.3.2

For those who installed masternodes with another method, you can download the linux binaries to your VPS, replace them in either /root or /usr/local/bin depending on where you have them installed, and restart your masternodes.

cd /root
wget https://github.com/phoreproject/Phore/releases/download/v1.3.2/phore-1.3.2-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.3.2-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.3.2/bin/phore* /usr/local/bin/
phore-cli stop
phored -daemon 

After either of these methods, check the status of the masternode on the VPS with:

phore-cli masternode status

If it tells you it is not a masternode, wait a minute and try again. If if says it is awaiting remote activation, go back to your wallet and start it with the following command in the debug console, replacing with the name you gave it in your wallet:

startmasternode alias false <aliasname>

After that, you can verify it is working with a couple of steps. First, on the VPS, type:

phore-cli masternode status

That should now say it is started successfully. Then after about 15 or 20 minutes from when you started the masternode, verify on your Phore wallet masternode tab, in the Active column, that the time has started counting up from zero. If it is, you're in good shape.

Reinstalling using a new VPS

You also have the option of starting over with a new VPS, and following one of the two mostly-automated VPS installation script guides available here:

https://github.com/phoreproject/vps
https://github.com/liray-unendlich/phore-masternode-automation

If you do that, you can set up the new VPS and then delete your old VPS once you have the new one ready to activate.

bootstrap.dat

It is more secure and recommended to sync the Phore blockchain over the network from other Phore nodes. However, if you have issues with your Phore wallet/masternode syncing the blockchain, for example if it gets stuck on a specific block and won't continue syncing, in some cases it may help to use a bootstrap.dat file that provides a local copy of all of the blocks up to a certain point. The team has provided a recent bootstrap.dat file to help with troubleshooting in these cases. Unless you have a very slow Internet connection, it is not significantly faster to load blocks from a bootstrap.dat file than it is to load it over the network--it is mostly useful in cases when a user is having issues with that completing successfully.

For last resort troubleshooting where even the bootstrap.dat is failing, we have also provided a snapshot of the key folders in the Phore data directory

Any time you are using either a bootstrap.dat file or a snapshot of the Phore data directory, you use this at your own risk. Do not use bootstrap.dat or snapshot files that are from any unofficial sources, as your node is trusting that the data is from the correct Phore blockchain.

To use the bootstrap.dat file, shut down your wallet or masternode if it was already running, download, uncompress and move the file to the Phore data directory, and start your wallet/masternode. It will load the blockchain up to the last block contained in the bootstrap.dat file and then switch to loading blocks over the network.

Phore Snapshot

Once again, it is more secure and recommended to sync the Phore blockchain over the network from other Phore nodes. However, if you have issues with your Phore wallet/masternode syncing the blockchain, and in rare cases where even the bootstrap.dat is failing, we have provided a snapshot of the key folders in the Phore data directory. Using the snapshot will be faster than loading the blocks from the network, but is less secure because your wallet/masternode is assuming that all of the blocks are valid instead of validating each one as it is received from peers.

Any time you are using either a bootstrap.dat file or a snapshot of the Phore data directory, you use this at your own risk. Do not use bootstrap.dat or snapshot files that are from any unofficial sources, as your node is trusting that the data is from the correct Phore blockchain.

To use the Phore snapshot:

• If your wallet/masternode has never been run before, start your wallet/masternode to have it create the initial Phore data directory. If you have an existing wallet you can skip this step.
• Shut down the wallet/masternode.
• Delete the following folders: blocks, chainstate, sporks, and zerocoin.
• Download and uncompress the same folders into the Phore data directory.
• Start your wallet/masternode.

Your wallet/masternode should load the snapshot database and continue syncing the blockchain from that point forward.

Notes on the above process:

• The default locations of the Phore wallet data directory that contains the four folders above can be found in our wallet troubleshooting FAQ: https://forum.phore.io/t/phore-wallet-troubleshooting-frequently-asked-questions-faq/106
• For Phore masternodes, the default Phore data directory location for masternodes installed using the VPS script method would be /var/lib/masternodes/phore1, and if you are running more than one masternode on the VPS, you can use /var/lib/masternodes/phore2, and so on for each masternode.
• For Phore masternodes installed using other methods, in most cases the Phore data directory will be found in the /root/.phore directory.
• On Windows, 7zip is one option to uncompress .tar.gz files. Please note you have to run the file through 7zip twice--once to unzip the gzipped file into a tar file, and a second time opening the tar file to extract the individual folders and files it contains.
• For OSX or Linux, after deleting the four folders listed above, you can copy the snapshot file into the Phore data folder, navigate to that folder using Terminal, and uncompress it using ...

v1.3.0

1.3.0 Release notes

This is an optional update--there will be another release around July 7th/8th that will be a MANDATORY UPGRADE before the end of July

Phore Core version 1.3.0 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

Wallets: 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), then run the
installer (on Windows) or just copy over /Applications/Phore-Qt (on Mac) or
phored/phore-qt (on Linux).

When upgrading masternodes, upgrade your controller wallet first. For a single masternode installed with the VPS script method, upgrading the masternode can be done with the following commands after logging in to your VPS, with each command on a separate line, pressing Enter after each one:

rm -rf /root/vps
git clone https://github.com/phoreproject/vps
cd vps
./install.sh -p phore -u

After that completes, then type:

systemctl restart phore_n1

To verify the status of the masternode after restarting with the upgraded version, type:

phored --conf=/etc/masternodes/phore_n1.conf masternode status

If it says started successfully, that may be all you need to do. If it tells you that it is a hot node awaiting activation, go back to your controller wallet, open the debug console, and type the following, replacing "aliasname" with the name you used for your masternode:

startmasternode alias false "aliasname"

1.3.0 changelog

• Add Segregated Witness support
  • Add SPORK_17_SEGWIT
  • Update messaging system to current Bitcoin Core 0.16
  • Update GetTransactionSigOpCost to count witness transactions at 1/4 the normal cost
  • Add NODE_WITNESS version flag for nodes
  • Fix RPC tests and RegTest networks
    • Add tests for wallet
    • Add tests for segwit
  • Update wallet to find SegWit transactions
• Merge with PIVX upstream v3.1.0
  • Make Zerocoin deterministic
  • Fix wallet bugs causing corruption
  • Fix Zerocoin modulus bug
  • Fix bugs in RPC commands causing incorrect responses
• Update logos
• Add CHECKLOCKTIMEVERIFY support
• Add CHECKSEQUENCEVERIFY support
• Add bech32 addresses

Activation

SegWit will be activated after the majority of staking nodes and all major exchange wallets have been upgraded. Zerocoin changes will take effect around August 1st along with the next release that will be a required upgrade.

Credits

• BlankGT
• Julian Meyer
• barrystyle
• tohsnoom
• wqking

As well as the entire Bitcoin, Dash, and PIVX teams!

v1.2.2

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!

v1.2.1

1.2.1 Release notes

Phore Core version 1.2.1 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

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), then run the
installer (on Windows) or just copy over /Applications/Phore-Qt (on Mac) or
phored/phore-qt (on Linux).

1.2.1 changelog

Switched to PIVX Core version v3.0.6 - https://github.com/PIVX-Project/PIVX/releases/tag/v3.0.6

• Automated database corruption repair
• More accurate error messages
• Reduction of debug log spam
• Faster transaction searching algorithm
• Fix for possible fork regarding zPHR

Also:

• Disabled autominting in GUI (meyer9)
• Fixed compile time warnings and support C++17 (mostly) (meyer9)
• Added a Dockerfile (diógenes)
• Updated checkpoints (meyer9)
• Fixed tests (konez2k)

Versioning Note

Phore will now be switching to a more standard semantic versioning
system (https://semver.org/). This means that in the future, the version numbers
will take the form:

MAJOR.MINOR.PATCH

Credits

Thanks to who contributed to this release, at least:

meyer9
tohsnoom
diogenes
konez2k

As well as the entire PIVX team!

v1.2.0.0

Phore Core version 1.2.0.0 is now available from:

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

This is a new major-revision version release, including various bug fixes, features, and
performance improvements, as well as updated translations.

Please report bugs using the issue tracker at github:

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

How to Upgrade

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), then run the installer (on Windows) or just copy over /Applications/Phore-Qt (on Mac) or phored/phore-qt (on Linux).