Skip to content

v1.6.3 Release Notes

v1.6.3 is an optional release for all wallets and masternodes.

This is a minor, optional bug fix release that fixes a display issue related to proposal amounts.

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.6.3
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.6.1/phore-1.6.3-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.6.3-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.6.3/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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Mike T.
Wang

Assets 14
Pre-release

@tohsnoom tohsnoom released this Apr 9, 2019 · 2 commits to master since this release

v1.6.2 Release Notes

v1.6.2 is an optional release for all wallets and masternodes.

This release includes contains a new feature that allows the creation of budget proposals from within the GUI, and some bug fixes including one for sporks that is needed for SegWit activation.

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.6.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.6.1/phore-1.6.2-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.6.2-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.6.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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael T. (Moonshot)
Wang
dustineagle

Assets 14
Feb 22, 2019
Merge pull request PIVX-Project#170 from j00v/master
Min. stake age validation fix
Verified by @masterhash-us

@tohsnoom tohsnoom released this Jan 31, 2019 · 11 commits to master since this release

v1.6.1 Release Notes

v1.6.1 is an MANDATORY release for all wallets and masternodes, and all nodes need to be upgraded by February 9th for them to continue functioning on the latest blockchain. Any v1.6.0 wallets or masternodes should upgrade to this version immediately.

This release includes contains bugfixes for the previous solution addressing a potential block spam vulnerability, which among other things prevents issues with reorganizing the blockchain when there are forks longer than 2 blocks.

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.6.1
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.6.1/phore-1.6.1-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.6.1-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.6.1/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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael (Moonshot)
Julian Meyer
Pinkcoin
@Astrych

Assets 15

@tohsnoom tohsnoom released this Jan 19, 2019 · 16 commits to master since this release

v1.6.0 Release Notes

v1.6.0 is an MANDATORY release for all wallets and masternodes, and all nodes need to be upgraded by February 9th for them to continue functioning on the latest blockchain.

This release includes the community approved development budget increase, a Japanese translation for the masternode setup GUI features, logging improvements, and a fix for a potential block spam vulnerability, and some other bugfixes and code refactoring.

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

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.6.0
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.6.0/phore-1.6.0-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.6.0-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.6.0/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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael (Moonshot)
Julian Meyer
Fuzzbawls
Mrs-X
liray-unendlich

Assets 14
Jan 9, 2019
Merge pull request PIVX-Project#162 from bulwark-crypto/dev
v2.1.1.0
Jan 3, 2019
Merge pull request #132 from heartofgold42/patch-2
Update URL for seeds

@tohsnoom tohsnoom released this Dec 14, 2018 · 45 commits to master since this release

v1.5.1 Release Notes

v1.5.1 is an optional release, but v1.5.0 is an mandatory release for all wallets and masternodes, which also includes a new Masternode Setup GUI for the steps performed in the wallet. See the v1.5.0 release notes for more details on those new features.

This release includes changes to make the minimum width of the wallet more narrow, to accommodate lower screen resolutions.

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.5.1
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.5.1/phore-1.5.1-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.5.1-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.5.1/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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael (Moonshot)

Assets 12

@tohsnoom tohsnoom released this Dec 12, 2018 · 94 commits to master since this release

v1.5.0 Release Notes

This is an mandatory release for all wallets and masternodes, and includes a new Masternode Setup GUI for the steps performed in the wallet.

Previously, several steps when you set up, modify, or remove a Phore masternode required you to manually run commands in the debug console and then use that information to edit the masternode.conf file, as well as requiring you to restart the wallet to load the new masternode configuration before you can start it. No more!

The new Phore masternode setup features allow you to add a new masternode to your wallet right in the masternode tab. Instead of running a command to generate a new masternode private key, now you can add one for your new masternode with the click of a button. Instead of running a command to find the masternode output information, the wallet can find the unused masternode outputs entry and autofill that information also with the click of a button.

Now to do these steps, simply send the 10,000 PHR collateral transaction to your wallet, click Configure Masternode on the Masternode tab, give the masternode an alias name, enter the IP address of the VPS where you are hosting the masternode, click the Autofill buttons for the private key and masternode outputs, and click OK. You do not need to restart the wallet--if the masternode is ready on the VPS, select the masternode and click Start Alias and you're up and running!

This release also includes a change to SegWit that is needed before we can activate it, and it is a required change for nodes to continue to work once we reach that point. We will monitor how quickly everyone upgrades their nodes, but at a minimum we will allow six weeks for the upgrade period, so we are tentatively targeting the end of January to activate SegWit. Wallet and masternode upgrade instructions are included below.

Several other bugs have also been squashed as part of this release. If you need further details feel free to ask in Discord or Telegram!

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

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

If you see this, use the [VPS upgrade method](### VPS Installation Script Method)

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

If you see this, use the [other upgrade method](### Other Installation Method)

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.

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.5.0
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.5.0/phore-1.5.0-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.5.0-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.5.0/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
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.

Syncing the blockchain with 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

It is more secure and recommended to sync the blockchain online from the Phore network. However, if you have issues with your Phore wallet/masternode syncing the blockchain, or when even the bootstrap.dat does not work, we have provided a snapshot of the key folders in the Phore data directory. Syncing the blockchain with the snapshot will be faster, but is less secure because your wallet/masternode is trusting that all of the previous blocks in the snapshot are valid and accurate.

Using a bootstrap.dat file or a snapshot of the Phore data directory are done at your own risk. Never use bootstrap.dat or snapshot files from any unofficial sources.

Syncing the blockchain with 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael (Moonshot)
Kolby (Mrmetech)
Wang (wqking)
Fuzzbawls
Mrs-X
SHTDJ
Warrows

Assets 12

@tohsnoom tohsnoom released this Nov 10, 2018 · 137 commits to master since this release

1.4.5 Release notes

This is an optional release, and squashes a couple of bugs that were reported by Phore users:

  • Some users have been reporting a problem sending more than a certain amount of Phore, with error messages related to SwiftX. We had removed the SwiftX checkbox in the last release, so to address this bug we have restored it. There is no reason to use SwiftX for most normal Phore transactions, and as long as that checkbox is not checked, you should no longer encounter these issues.
  • A long standing issue has been reported periodically about the timestamp of transactions not being shown accurately in the Transactions tab. Liray-undelich found a way to fix this, so the times for your staking and masternode rewards should be more accurate going forward.

This is an optional release for both wallets and masternodes. Version 1.3.3.1 and version 1.4.4 nodes are both compatible with this version. Please note however, if you upgrade your masternodes, you will need to also upgrade your wallet that controls the masternodes before you can start them.

Phore Core version 1.4.5 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.4.5
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.4.4/phore-1.4.4-x86_64-linux-gnu.tar.gz
tar zxvf phore-1.4.5-x86_64-linux-gnu.tar.gz
mkdir phore-old
mv /usr/local/bin/phore* phore-old/
cp /root/phore-1.4.5/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
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, or for rare cases where even the bootstrap.dat does not work, 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 the command tar zxvf PhoreSnapshot.tar.gz

Credits

Michael (Moonshot)
liray-unendlich

Assets 12
You can’t perform that action at this time.