Knowledge Base

FAQ - Frequently Asked Questions

FAQ - Frequently Asked Questions

Wallet crashes or has crashed and now won’t launch. Fails every time. What do I do?

An abnormal exit of the wallet could result in a blockchain inconsistency from that point onwards. This can happen due to a PC reboot without first closing the wallet gracefully or if the existing locally downloaded blockchain somehow got corrupt (due to environmental issues etc) and cause the wallet to crash.

 

If experiencing wallet launch failures with the latest wallet, it is suggested to first try using the -forcestart startup flag to see if it will recover from a failed start.
In Windows OS, you need to edit the shortcut properties and append it to the end of the "Target" field, so that the end reads:
pivx-qt.exe" -forcestart

 

If the wallet startup issue is not fixed by upgrading to v3.1.0.2 or higher and/or the -forcestart flag, the user should resync the blockchain as per steps below.

 

As you are not deleting the conf and wallet.dat file, this procedure will not affect your coins nor your masternodes.

 

Easy Method

GUI Wallet users: 

"Tools > Wallet Repair > Delete Local Blockchain Folders (-resync)" to initiate the full re-sync.

(unless you have a known good backup of the blockchain that you know how to restore)

 

Command line users:

You can initiate the full resync during daemon startup with the command switch `pivxd -resync`

 

Advanced Method

1) Navigate to your PIVX data directory and delete the files pointed in red arrow in the following image:

 

You must also delete the folders called: zerocoin & sporks if you are following this guide

 

2) Now re-launch the wallet and wait for it to Sync. This can take few hours on slower internet connection.

**Please note that during the sync your balance will show as 0 until near the end, this is normal and nothing is lost**

 

 

How do I make a backup of the blockchain so I can avoid a full resync if something goes wrong?

 

Now, if you face a corrupt blockchain again, just delete the 4 folders blocks, chainstate, sporks, & zerocoin only, copy over the good backup blocks, chainstate, sporks, & zerocoin folders, then restart the wallet and you will only have to sync transactions since the backup, not the beginning of PIVX.

 

FAQ - Frequently Asked Questions

When will my MN get the next payment, and is masternode list related?

(adapted from https://github.com/PIVX-Project/PIVX/issues/216#issuecomment-316534805 by Mrs-X)

The ranking from masternode list rank (or masternodelist for newer versions of PIVX), even when it might sound so, is NOT related to masternode payments, it's used to build consensus for SwiftTX and other things. Naming it rank was, umh, unlucky :-)

The decision to reward a masternode is (besides some other technical things) based on:

  • It must be enabled (have the 10000 PIV collateral, valid protocol version, and some other things)
  • The 10000 PIV collateral must be at least as many blocks (plus one) old as masternodes exist (e.g. would be 2172 right now)
  • It must be amongst the 10% oldest nodes (by last received payment)

If those prerequisites are all fulfilled the score for each of those 10% masternodes is computed.


The score is (basically) the hash (!) from some data from the blockchain and some properties of your masternode, so each node comes to the same result. The masternode with the highest score gets the payment.

But, and this is the important part: the hash is (more or less) a random number, so you never know which masternode will win beforehand.


And, if you have really bad luck, your masternode might stay in that 10% list for quite some time until it gets paid, I've had cases where I was paid after 8000 blocks instead of about 2000 blocks. But as long as you're masternode is enabled it stays in that 10% of nodes. In the long run, good and bad luck equals out and everyone gets the same number of rewards, so no need to worry.

FAQ - Frequently Asked Questions

My wallet seems to have become stuck syncing and says remains at X hours left. It’s been many hours and status hasn't changed. What do I do?

This may happen due to connecting to some bad peers or your chain has been corrupted somehow.

First, try simply restarting the wallet then after it's synced up, check if you are on the right chain via article below:
https://pivx.freshdesk.com/solution/articles/30000004667-my-staking-or-masternode-reward-is-much-higher-than-expected-and-or-my-recent-transactions-aren-t-sh

If you are on the right chain but isn't syncing the newer blocks, please follow solution steps outlined in below article to resync cleanly off the network with a new peers.dat.
https://pivx.freshdesk.com/solution/articles/30000004661-wallet-crashes-or-has-crashed-and-now-won-t-launch-fails-every-time-what-do-i-do-

Also, ensure that your pivx.conf doesn't have any connect= or addnodes= lines unless you know why they are there.
(pivx.conf is located in the folders listed in below KB article)
https://pivx.freshdesk.com/solution/articles/30000004664-where-is-my-wallet-dat-blockchain-and-conf-files-located-

FAQ - Frequently Asked Questions

Where are my wallet.dat, blockchain and configuration(.conf) files located?

Your PIVX data directory stores your blockchain, configuration, wallet, and masternode data. By default, they are located in the following locations for each OS type:

Windows

Go to Start > Run > %APPDATA%\PIVX
(or just enter the above path in explorer)
or C:\Users\%username%\AppData\Roaming\PIVX
(Hidden folder "AppData" - How to view hidden folders on Windows)

OSX (MacOS)

Open a finder window, then select the "Go" dropdown menu. In this menu please press the "Go to Folder..." option. In the window that opens type: ~/Library/Application Support/PIVX and press enter. If the folder cannot be found please repeat the steps and enter: ~/.pivx

~/Library/Application\ Support/PIVX
(/Users/YourUserName/Library/Application\ Support/PIVX)
(How to view the hidden folder on OSX)

MacOS High Sierra Only
~/.pivx
(/Users/YourUserName/.pivx)
(How to view the hidden folder on OSX)

Linux
~/.pivx
(Hidden folder ".pivx" - control+h to display in the GUI, ls -a to display in terminal)

Android
The Android wallet backs up your wallet file to the Download folder. Android does not use the typical data directory because it is an SPV wallet relying on a full node running PIVX Core. It does not host the blockchain or need a conf file for advanced functions like staking and masternode operation.

FAQ - Frequently Asked Questions

How do I make a backup of the blockchain so I can avoid a full resync if something goes wrong?

After a successful full resync, and if your wallet it working fine, you can make a backup of the good blockchain by following these steps below:

1) Close your wallet gracefully (File -> Exit or ./pivx-cli stop)

2) Go to your blockchain data directory. (default directories listed in this article)

3) Copy the 4 folders (blocks, chainstate, sporks, & zerocoin) elsewhere. (Some other directory or drive)

4) You can now start the wallet again.

Now, if you face a corrupt blockchain issue again (as in Question 1 above), you can close the wallet then delete the 2 folders (chainstate & blocks), copy over the good backup blocks & chainstate folders to it, then restart the wallet.

FAQ - Frequently Asked Questions

My staking or masternode reward is much higher than expected. And/or my recent transactions aren't showing up in block explorer but my wallet is fully synced and seems up to date.

There is a possibility that your wallet may be not synced up with the network properly or that your wallet may have somehow forked and isn't connected to the main network. Just to make sure that you are on the right block and is on the right network, please perform the following check:
(demonstration)

  1. From your wallet's debug console (Tools -> Debug console or just use ./pivx-cli getinfo in linux), type:
    getinfo
  2. Note the block number. ("blocks":) That is the block number that your wallet is currently synced up to.
  3. Now type:
    getblockhash xxxxxx (where xxxxxx is the block number you got from getinfo output above)
  4. Compare the hash to the block explorer's block hash for that same block via the following URL:
    http://www.presstab.pw/phpexplorer/PIVX/block.php19 (search your block number that you used in step 2 & 3)
  5. If the hash is different, you are not on the right chain. Update to the latest wallet (if not already on it), restart the wallet, wait until wallet is synced, and follow steps 1 through 4 again.
  6. If you are still not matching block:hash of the presstab block explorer, then perform a reindex.
    Qt Wallet = Tools -> Wallet Repair -> Rebuild Index (this can take many minutes to complete)
    Linux = Close wallet. Start the wallet with `-reindex=1` (e.g. `./pivxd -reindex=1`)
  7. If that still fails, follow the steps outlined in this article to re-sync back fresh (but skip the -forcestart part): KB article
  8. If the hash matched up between your wallet and the block explorer, then your wallet is on the right network.
  9. If your recipient still hasn't received your coins, you need to ensure that the recipient is also on the right network and synced up to the latest block with no delays.

If you see lots of conflicted transactions, follow the steps below in this KB article to clear them. (conflicted transactions means they aren't/weren't valid transactions)

FAQ - Frequently Asked Questions

I'm seeing a lot of conflicted and/or orphan transactions as a result of staking but not winning those blocks. Is there a way to clean them up and not show them? I don't like seeing them.

Yes, there is a simple way and it doesn't (or shouldn't) affect your coin balance.

1) Backup your wallet if you haven't done so recently. (this is just a precaution and not mandatory)

2) In your Qt wallet, go to Tools -> Wallet Repair

3) Run the Recover Transactions 1 (zapwallettxes=1)

It will now go through your wallet and scrub out the orphan transaction. Should take few minutes.

FAQ - Frequently Asked Questions

How can I control which address my coins are sent from?

(video)
Open the PIVX wallet
Click the "Settings" option on the toolbar
Then select "Options"
Click the "Wallet" tab on the top
Check the "Coin Control" checkbox
Close the Options window
Click the "Send" tab and control which addresses to send from with the "Inputs..." button.

FAQ - Frequently Asked Questions

My PIVX wallet is missing some of my PIV or has no balance at all!, Easy steps to solve this

As a safety precaution always go to your PIVX data directory and backup your wallet.dat, Preferably on an offline location such as a secure flashdrive. Avoid online storage.

Now open your PIVX wallet, Select the TOOLS tab, select Wallet Repair in the drop down menu and lastly Select RESCAN BLOCKCHAIN FILES as seen in the image below

Your wallet should begin the rescan on the blockchain files for your missing transactions and your funds should show as normal. In some cases you may need to delete the old blockchain and completely resync everything. So if this tutorial doesn't work then please follow the blockchain deleting steps as mentioned in this one https://pivx.freshdesk.com/solution/articles/30000004661-wallet-crashes-or-has-crashed-and-now-won-t-launch-fails-every-time-what-do-i-do-

FAQ - Frequently Asked Questions

Terminology

  • Immature (PIV) - The maturity of coins refers to their staking eligibility, which is controlled by their amount of confirmations. PIV are considered mature once they have 101 confirmations, which takes about 101 minutes.
  • Immature (zPIV) - A new zPIV mint that has not yet been followed by 2 other mints of that denomination. (Reduced from 3 to 2 on v3.0.5) (source)
  • Unconfirmed (PIV) - A PIV transaction that has not yet been included in a block
  • Unconfirmed (zPIV) - A new zPIV mint that has not seen 20 confirmations
  • Orphan block - A block that is no longer part of the active chain. This can happen most often after fixing your chain or if you stake a block successfully, but someone else staked one slightly sooner.
  • Fork - In general terms, a fork is a divergence like a fork in a road. The most common use of this term in cryptocurrency is for code or chain forks. In both situations, the data leading up to the fork will match, but after the fork it will differ between the forks.
  • Chain fork - A divergence of a blockchain, usually due to expanding or constricting the rules about what kind of blocks are valid
  • Code fork - A copy of existing code to be developed toward different goals
  • Wrong chain - The incorrect blockchain, usually by not updating your software with a mandatory version in time
  • HD Wallet - Hierarchical Deterministic Wallet - A wallet that can use a seed mnemonic phrase to generate addresses and keys, rather than loading them from a wallet.dat file.
  • SPV wallet - Simplified Payment Verification - A wallet that relies on a full node elsewhere to send and receive blockchain data. The mobile PIVX wallets are examples of SPV wallets
  • GUI - Graphical User Interface
  • CLI - Command Line Interface
  • Zerocoin - A cryptographic blockchain privacy protocol that uses ZK Proofs to break linkage and hide balances. https://pivx.org/zpiv/
  • Zerocash - Zerocash is a different method of using ZK proofs for privacy, used in ZCash.
  • ZK Proofs - Zero Knowledge Proofs - Technology that allows you to prove you know a secret without disclosing the information. Used in the zerocoin and zerocash protocols as part of the privacy mechanism
  • zk-SNARKS - Technology used in the zerocash protocol used by ZCash and soon to be adopted by Ethereum
  • zk-STARKS - A theoretical improvement to zerocash with no trusted setup, smaller proofs, and lower resource requirements
  • Scaled - A scaled transaction or balance indicates that it is on an old wallet version and the wallet has not been upgraded yet
FAQ - Frequently Asked Questions

Nothing happens when I click Open Wallet Config File on my Mac

Symptoms:

Within PIVX Core, clicking Open Wallet Config File does not do anything


Cause:

MacOS has no default program association with the .conf file type. PIVX runs without admin rights for security reasons and so the wallet has to rely on the operating system to know which program to use.


Solution:

Users can make the association manually by opening up the file from the Finder the first time and ticking the checkbox that sets it to “always use this program…”. To find the .conf file in Finder, follow the OSX instructions here: Where is my PIVX data directory?

FAQ - Frequently Asked Questions

Staking FAQ

  • Does staking require 24/7 uptime?
    No, but you will only be eligible for staking rewards while staking is active. If your computer is asleep, off, or offline you would not be eligible.
  • Does my amount of time staking or coin age affect my chances of winning rewards?
    No, PIVX proof of stake does not give more weight to older coins or clients with longer consecutive uptime. The only weight you have in staking is your (mature) PIV balance. Think of the block reward each minute like a lottery and each mature PIV is a ticket that increases your chances of winning
  • Can I optimize my inputs/UTXOs for better staking chances?
    This is debatable, but some people do swear by it. If you look at Stake Weight Spent on presstab's block explorer homepage, you will see that the network seems to choose UTXO of a certain size more often (2700 at time of writing). However, this could also be due to stakers optimizing their UTXOs to this size and creating a self-fulfilling prophecy situation.
  • Can I stake with zPIV?
    Yes, staking zPIV will reward a stake with 3 zPIV while staking with PIV will reward a stake with 2 PIV.
  • Why do I need to unlock my wallet for staking?
    An option to "unlock for staking only" has been included for security so normal transactions can't be sent during this type of unlock. An unlock is required because if you win the block reward, your PIVX client will send out the winning UTXO and it will come back with the reward included. So if your 2,010 PIV UTXO wins and the reward is currently 2.29, your client will send 2,010 PIV and get back 2,012.29 PIV. Here is an example on the block explorer (Output 2 is the masternode's reward). Please note, this is considered a transaction and the 3,004.25 PIV in that new input will be considered immature and ineligible for staking for 101 confirmations (about 101 minutes). After that time they will automatically be added back to your staking balance.
  • Can I stake on a Raspberry Pi?
    Yes, the Raspberry pi 3 can use the 32bit ARM build for Linux. The GUI usage matches other systems and there is a command line guide here. The Raspberry pi 2 Model B has been reported to work as well
    Its recommended to set a 1024Mb swap file at your Raspberry Pi, because the wallet requires more than 1GB of RAM at peaks (esp. when staking). Here are some instructions how to set the swap file. Stake without a swap file on a Raspberry Pi could corrupt your local copy of the Blockchain.

    Do I need to add "staking=1" to my configuration file?
    No, the only conditions for staking are listed here
FAQ - Frequently Asked Questions

Mandatory Upgrade and Hard Fork FAQ

What is a mandatory upgrade?

A mandatory upgrade is when you are required to upgrade your software to a minimum version in order to stay on the PIVX network and correct chain. This is usually due to a software upgrade that will cause a hard fork, but sometimes is due to other factors like a software security concern.

What is a hard fork?

A hard fork is an upgrade to PIVX that is not backwards compatible and would cause the blockchain to diverge. For example, PIVX Core v3.0 will allow usage of the zerocoin protocol, but clients on the old v2.3 software would not recognize these new blocks and reject them. More information can be found here.

What happens if I don't upgrade before the deadline?

If you are running an old version of PIVX during or after the fork, you will start recording blocks on the wrong chain. You will not be able to send PIV or otherwise interact with the PIVX network and correct blockchain.

How do I get back on the right chain?

Remediation for this problem involves upgrading your software, clearing your local cache, starting PIVX Core, and resyncing the chain. Follow these instructions starting at step 1 after the force start part.

What happens if I tried to send or receive PIV while I was on the wrong chain?

Don't worry, your PIV are not lost if you have your wallet.dat file. If you sent PIV while on the wrong chain, your address still has those PIV on the correct chain. If someone sent you PIV, your address on the correct chain has those PIV, your client just can't see them yet (assuming the sender is on the correct chain). To confirm PIV did or did not send on the correct chain, check the destination address on the block explorer.

What happens to the other chain?

The other chain is only populated by clients on the old software, so it does not have enough users or nodes to survive and quickly stops working. A second chain only survives if the upgrade is highly contentious and the old software has significant support from users, miners/stakers, nodes, exchanges, and merchants. Popular examples are bitcoin cash forking from bitcoin and ethereum forking from ethereum classic.

FAQ - Frequently Asked Questions

Why do some of my zPIV not appear?

Modified on: Mon, 16 Jul, 2018 at 1:29 PM

Backing up and Restoring V2 zPIV from a Deterministic Seed

Please note that zPiv take at least 20 confirmations to complete minting, so if the confirms are around/near there, please wait for more confirmations. Also, zPiv mintings require further mintings of the same denomination in the pool to complete, so you can find if these are still awaiting more mintings of the same denomination under Privacy -> zPiv control -> drop down arrows to the left, and check the rightmost column.

Please be aware zPiv v1 signatures are stored in the wallet.dat used at the time of minting, so if you have loaded an older/different backup since then, or used this wallet on more than one machine, you will want to check your other wallet.dat backups from around the time of minting. You may need to run the below steps on all relevant wallet.dats.

If you are missing zPiv, please try the following steps:

First, go to tools -> debug console and enter the following commands in this order:

getarchivedzerocoin
reconsiderzerocoins
resetspentzerocoin
resetmintzerocoin true

The last command may lock up the client briefly.

Then, go to the Privacy tab and use the Reset and then ReScan buttons (this last one will take some time)

After the rescan is complete, missing zPiv should appear within a few minutes.

If the above information does not assist, check out this video guide by presstab:
https://www.youtube.com/watch?v=qp7qHF7E_Dc

 

If you are missing v2 zPIV, please try the following steps:

First, fully unlock you wallet, then go to tools -> debug console and enter the following command:

searchdzpiv 0 1000 2

This command may take some time to complete.

FAQ - Frequently Asked Questions

How can I export / import zPIV?

If you have zPIV on separate wallet.dat files and want to combine them, you can use the following steps:

  1. Open the wallet with the wallet.dat you want to export zPiv from and go to tools -> debug console and enter the command
    exportzerocoins true
  2. Copy the resulting output of this command, everything from [ to ]
    Please note: NEVER share the full output of this command with others as it contains the signatures needed to load and use your zPIV!
  3. Close the wallet and replace the wallet.dat with the one you want to use (do not delete the wallet.dat, simply move or rename it)
  4. Open the wallet with the preferred wallet.dat and go to tools -> debug console and enter the command
    importzerocoins '
    (Note the opening ') and then paste the output from the export command, followed by a final '

Again, the input following importzerocoins should be wrapped in apostrophes (') so it should look like:
importzerocoins '[ multiple lines of data ]'

FAQ - Frequently Asked Questions

My wallet is still autominting even though I added the line to disable it in my config file

Symptoms

The wallet continues to automint even after adding "enablezeromint=0" to the config file

Cause

The most common cause is that the config file line was added while the wallet was running and it has not yet been restarted. Failing that, the same wallet may be running somewhere else where automint is not disabled

Resolution

Restart the wallet and confirm that there are no other clients running your wallet. Please also note that running the same wallet on two computers at the same time can lead to file corruption and is not recommended

 

FAQ - Frequently Asked Questions

A transaction does not appear in the destination wallet

This can happen if either the sender or receiver is forked, not synced, or otherwise not aware of the transaction, but either way there is no need to worry. If the sender had a problem with their wallet, they will still have that money when the problem is resolved. If the recipient has a problem with their wallet, they have the money and they just can't see it until the problem is resolved.

To determine where the problem is, check if your transaction appears on the block explorer by looking up the transaction ID or the destination address. If the transaction appears, the problem is with the recipient wallet. If it doesn't, the sender has a problem they need to fix.

The wallet with the issue can find out if they are forked or unsynced and fix it by following this article: https://pivx.freshdesk.com/support/solutions/articles/30000004667-my-staking-or-masternode-reward-is-much-higher-than-expected-and-or-my-recent-transactions-aren-t-sh

FAQ - Frequently Asked Questions

How can I setup alerts or other actions when I win a staking or masternode reward?

We get many questions about getting an email or text when a reward is won. This process may become easier when blockchain monitoring web services pop up, but for now there is a parameter that will help us accomplish this from the Core client. This command can be used as a startup switch or in your config file

HTML
-walletnotify=<cmd>
Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)

 

For example, you could run a script:

Windows
HTML
-walletnotify=%userprofile%\scripts\email.ps1 %s


Linux
HTML
-walletnotify=/home/turtleflax/scripts/email.sh %s


These examples would launch a script and passes the transaction ID as a parameter to the script. The script could then do whatever you like, including logging to a file or sending an email. For email, you would need to set that up on your system independently. The following links may be useful for that:
https://gallery.technet.microsoft.com/scriptcenter/Simple-Powershell-function-8e826d7c

https://stackoverflow.com/questions/4658283/shell-script-to-send-email

If you would like to get a text message, you'll have to set up email and follow this guide: http://www.popularmechanics.com/culture/web/how-to/a3096/email-to-text-guide/

FAQ - Frequently Asked Questions

Automatic zPIV minting and zPIV backup requirements

What is the automint?

As of PIVX Core v3.0 your wallet will automatically mint about 10% of your balance to zPIV. If your wallet is encrypted, this will happen once you send a transaction or unlock the wallet (even for staking and anonymization only). You can configure the automint to any percentage 0 to 100% or disable it using the link at the bottom of this article.


Why does PIVX Core Wallet automint zPIV?

PIVX’s Zerocoin Protocol works by automatically “mixing” zPIV of the same denomination together, making zPIV transactions virtually impossible to trace. The PIVX Core Wallet automatically mints 10% of users’ unlocked PIVX balances into zPIV, which ensures there are enough zPIV denominations available to mix and make Zerocoin Protocol effective regardless of manual zPIV minting volume.


What are the backup requirements for zPIV?


Beginning with PIVX Core v3.1, PIVX uses an innovative system called dzPIV, which provides a one-time seed backup for your zPIV. Please follow this guide to backup your zPIV seed.

This means that you don't need to make a new backup after every zPIV mint, but periodic wallet.dat backups are still a good idea. It is still important to keep all of your wallet.dat files because your normal piv are still stored in there and the seed does not cover them.

Never delete any wallet.dat files.

How do I disable the automint?

FAQ - Frequently Asked Questions

Which wallet download do I need?

This page is here to help you choose your correct wallet download from the PIVX wallet download page.

 

Windows

32bit or 64bit
You will need the version that matches your operating system, although 64bit windows is generally backwards compatible with 32 bit apps. How to check your version of Windows.

exe or zip
The exe is the recommended download as this will install everything to standard locations and updating is easier. The zip download allows you to download the binaries in a more portable format, but please note that your data directory will still be saved to the C: drive unless you specify otherwise. If you use the zip version, please remember to update your shortcuts when you update the software.


Mac

dmg or tgz
This is similar to the exe or zip section above. The dmg will install PIVX Core in standard locations and update easily. The tgz is a portable set of binaries. If you use the tgz version, please remember to update your shortcuts when you update the software.

High Sierra
Changes in the High Sierra version of OSX require a special build of PIVX Core. If you have High Sierra you must use this download.


Linux

32bit or 64bit
You will need the version that matches your operating system. How to check your OS type on Linux.

tgz or arm
The ARM option is for low power processors like a raspberry pi. All others should use the standard tgz install. Please note the tgz is a portable set of binaries, so you when you need to run or update your PIVX Core software you'll need to know where you downloaded and unzipped it.


Mobile

PIVX Mobile Wallet for Android
This is the official PIVX Android app. It is an HD and SPV wallet.

Coinomi
Coinomi is a 3rd party multicoin HD and SPV wallet that works based on a seed phrase and supports PIVX. It can also sweep wallets, which is useful for recovery or redemption of paper wallet balances.


Single Board Computers (SBCs)


The Raspberry Pi runs Linux and runs Raspbian, a 32bit operating system (even though the CPU is 64bit ARM). For this you will need the 32bit ARM download.

Other SBCs like the Odroid or banana pi are likely to use the linux ARM build but may be full 64bit

FAQ - Frequently Asked Questions

How Do I Open my Wallet Configuration file on a Mac?

MacOS has no default program association with the .conf file type; this prevent the PIVX Wallet application from opening the Wallet Configuration file (or pivx.conf) from the Tools dropdown menu.


To Navigate to the configuration file from the Desktop:

  1. Open a finder window,
  2. Select the "Go" dropdown menu.
  3. In this menu please press the "Go to Folder..." option.
  4. In the window that opens type: ~/Library/Application Support/PIVX and press enter

If the folder cannot be found please repeat the steps and enter: ~/.pivx
If the folder still cannot be found:

  1. Open the wallet and select the tools drop down menu
  2. Select the Wallet Repair option.
  3. Make note of the folder which contains the wallet in use.
  4. Use the specified folder in the "Go to Folder..." option.
  5. Double click on pivx.conf
  6. A popup window will state that "There is no application set to open the document “pivx.conf”. Press the Choose Application... button
  7. Now in the window that opens scroll down to select the TextEdit application and select open.
  8. Enter your configuration updates.
  9. Click the file dropdown menu and select save.
  10. Click the file dropdown menu and select close.
  11. Restart the wallet for the configuration to take effect.

To Navigate to the configuration file from within the Application:

  1. Open the PIVX Wallet
  2. Click the Tools dropdown menu and select "Show Automatic Backups." This will open a finder window with a bunch of wallet.dat files in it.
  3. Click this finder window and press the cmd key along with the up arrow at the same time. This will cause your finder window to move up one directory into the PIVX data directory.
  4. Double click on pivx.conf
  5. A popup window will state that "There is no application set to open the document “pivx.conf”. Press the Choose Application... button
  6. Now in the window that opens scroll down to select the TextEdit application and select open.
  7. Enter your configuration updates.
  8. Click the file dropdown menu and select save.
  9. Click the file dropdown menu and select close.
  10. Restart the wallet for the configuration to take effect.

To navigate to the configuration file from the Terminal:

  1. Open the terminal by using Spotlight search in OS X, searching for “terminal”
  2. Determine your user name by entering:
            id -un
  3. Enter the following where <username> is replaced with the output from line 2:

High Sierra:

            open -a TextEdit /Users/<username>/.pivx/pivx.conf

Other:

open -a TextEdit /Users/<username>/Library/Application\ Support/PIVX.pivx.conf

4. Enter your configuration updates.
5. Click the file dropdown menu and select save.
6. Click the file dropdown menu and select close.
7. Restart the wallet for the configuration to take effect.

 

 

Getting Started

Getting Started

What does PIVX stand for?

PIVX is an acronym for Private Instant Verified Transaction(X).

Getting Started

What is PIVX?

PIVX is a transactional security and privacy driven decentralized open source cryptocurrency.

PIVX was launched on February 1st, 2016 under the name of 'Darknet' (DNET).

PIVX features Pos 3.0, masternodes and no premine.

Getting Started

Where can I view the PIVX white paper?

You can view the white paper here.

Getting Started

Where can I find the roadmap?

You can find the roadmap here.

Getting Started

PIVX Best Practices

Cryptocurrency is brand new technology that has new concepts, procedures, terminology, and security risks to learn about. Even if you are familiar with other cryptocurrency, there are some unique parts of PIVX that you may need to know.

  1. Always encrypt your wallet file with a 16+ character passphrase. This will protect your PIV in case someone steals your wallet.dat file physically or digitally
  2. Always back up your wallet.dat file. Minting zPIV requires a new backup. The software automatically does this for you, but for extra caution you can also do it manually. Replicate all new backups to all backup locations (only add to them, do not overwrite old backups)
  3. Never ever delete or overwrite a wallet.dat file or your backups folder. Instead, rename the existing file and add it to your backups.
  4. Do not forget your encrypted wallet's passphrase. If you do, your funds are lost. If you need to record the passphrase somewhere, make sure you use an offline, secure method that you will not lose access to and nobody else can access.
  5. Do not run the same wallet in multiple locations at the same time. This can corrupt your wallet files and cause your minted zPIV to be difficult to find.
  6. Do not back up your wallet.dat file to a cloud provider or shared storage without a second layer of encryption like 7zip or veracrypt container.
  7. When designing your backup scheme, consider what level of protection you want for your balance. Do you have an offsite backup? Could your active wallet.dat and cold storage backups be lost to theft? Floods, tornados, hardware failure, fires, or hackers may also be things to consider.
  8. Do not ever send your wallet.dat file to anyone for any reason. At best this would violate your privacy and at worst put your coins at risk. There is no support reason to request your wallet file, so if anyone asks you for this report them to the PIVX team immediately.
  9. Do not ever share the information from dumpprivkey, exportzerocoins, or masternodeprivkey with anyone. This would give them access to your money. If anyone asks you for this information, contact the PIVX team immediately.
  10. Do not accept or solicit support over Private Messages, this is where scammers prefer to work
Getting Started

Getting Started with PIVX Core

Welcome to PIVX! This is a quick guide on the first steps you should take when starting the software:

  1. Download the latest PIVX Core wallet for desktop from https://pivx.org/wallet/
  2. Start the software and after the intro splash screen it will begin to sync the blockchain. While this is happening you can proceed to the next steps
  3. Encrypt your wallet
  4. Backup your wallet.dat and your zPIV seed
  5. Read about the automint and decide if you want to adjust or disable it: https://pivx.freshdesk.com/support/solutions/articles/30000026923-automatic-zpiv-minting-and-zpiv-backup-requirements
  6. Wait for your wallet to complete the sync and then you are ready to start using PIVX

 

You may now be interested in some of the following articles:

Tutorials

Tutorials

How to use the command line to install or upgrade PIVX and start staking on Linux.

The first few commands will help you backup your files for an upgrade, but brand new installs can skip down to the highlighted location. This guide should be updated as new versions are released, but make sure you use the latest version in the download step.

Change Directory to the home directory (/home/pi in this case)

pivx2.PNG

Stop the currently running PIVX daemon. Your PIVX binaries may be in a different location like Downloads

pivx3.PNG

Make a backup of the current wallet (to a network share in this case but you can copy to a USB too). Backing up your wallet to a safe location is always a good idea

pi@barry:~ $ cp .pivx/wallet.dat /media/Crypto/walletBackups/wallet.dat.pivx.20171130.bak

New installs being here
Download the new binaries from the official github repository. Make sure you get the right build for your device. For a Raspberry Pi, you want the 32-bit ARM release (pivx-3.1.1-arm-linux-gnueabihf.tar.gz)

pi@barry:~ $ wget https://github.com/PIVX-Project/PIVX/releases/download/v3.1.1/pivx-3.1.1-x86_64-linux-gnu.tar.gz
--2017-11-30 20:32:22-- https://github.com/PIVX-Project/PIVX/releases/download/v3.1.1/pivx-3.1.1-x86_64-linux-gnu.tar.gz

...

Saving to: ‘pivx-3.1.1-x86_64-linux-gnu.tar.gz’

pivx-3.1.1-x86_64-l 100%[===================>] 35.79M 7.89MB/s in 5.9s

2018-07-13 09:30:58 (6.11 MB/s) - ‘pivx-3.1.1-x86_64-linux-gnu.tar.gz’ saved [37533970/37533970]

Extract the tar.gz file to the pivx-3.0.6 folder, still in the home directory

pivx1.PNG

New installs only: Create the .pivx folder and pivx configuration with the RPC lines required for pivx-cli to talk to pivxd

pi@barry:~ $ mkdir ~/.pivx
pi@barry:~ $ nano ~/.pivx/pivx.conf

#Add the following lines to the file. For the X's, press 16+ random keys on the keyboard. You don't need to record or remember these random values:

rpcuser=XXXXXXXXXXXXXXXX
rpcpassword=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Start the PIVX daemon

pivx5.PNG

Be impatient and spam getinfo to see if it's ready yet so you can get staking. "Blockchain information not yet available" just means it's still starting, which takes a few minutes and quite a bit longer on a single board computer.pivx6.PNG

The daemon is ready and the version number indicates the newest version in the "version" line. However we are not staking yet, as indicated in the "staking status" line.pivx7.PNG

Remember to be safe and always encrypt your wallet before holding any PIVX!
You can give your wallet a password by using the commands:

vWvpivx7.PNG

The wallet will turn off once it has completed encrypting. All you need to do is run to get it started! 

pivx8.PNG

Unlock the wallet for staking only. The syntax is
walletpassphrase <passphrase> <unlock time> <for staking/anonymization only true/false>
Introduced in v2.3 is the ability to unlock indefinitely by using an unlock time of 0. It is recommended that you start the command with a space so it is not saved in bash history with your passhrase. If you've already done this, you can use nano to remove the entry from ~./bash_history

pi@barry:~ $ ~/pivx-3.1.1/bin/pivx-cli walletpassphrase 9jF5rujKLo96t$4erfdy76tf 0 true

Staking active!

pivx9.PNG

If you have unlocked your wallet but staking is still not active, please refer to the troubleshooting guide here: https://pivx.freshdesk.com/support/solutions/articles/30000023125-how-to-troubleshoot-staking-activation

 

 

 

Tutorials

How to hash a file to confirm its integrity

Windows
On Windows, you can open up a command prompt and use the certUtil command.
Usage: certUtil -hashfile <filepath> SHA256

C:\Users\turtleflax>certUtil -hashfile "C:\Users\turtleflax\Downloads\pivx-3.0.6-win64-setup-unsigned.exe" SHA256

SHA256 hash of C:\Users\turtleflax\Downloads\pivx-3.0.6-win64-setup-unsigned.exe:

2ae1e5f9e6b7ca6119891fd09713b3fca53d52f4c36bb84b4528a4b9440b88ec

CertUtil: -hashfile command completed successfully.

Mac
On Mac, you can open a terminal window and use the openssl command.
Usage: openssl sha -sha256 <filepath>

pivx10.PNG

Linux
On Linux, you can open a terminal window and use the sha256sum command.
Usage: sha256sum <filepath>

pi@barry:~$ sha256sum ~/Downloads/pivx-3.0.6-x86_64-linux-gnu.tar.gz
1b987933112560641ac3d8f9b56509ae5dcfc2df2179a1a07b6c9535744d8e58 pivx-3.0.6-x86_64-linux-gnu.tar.gz

Why would I want to do this process?

PIVX Core releases are posted to github with their SHA256 checksum values in a file called SHA256SUMS.asc. You can open this file in notepad or any other text editor to view the contents. You will see that it is a PGP signed message with a SHA256 value for each associated binary file with that PIVX Core version. The purpose of the SHA256 value is to confirm that the file you downloaded matches the official github release file exactly. If it does not, it could indicate a download problem or MITM (Man in the Middle) attack.

Here is an example SHA256SUMS.asc file from the v3.0.6 release:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

141be1f2305dc133cb96f6fe7122f53be99f1bb6ed88a8f36199ab3e436d1f2e pivx-3.0.6-aarch64-linux-gnu.tar.gz
46e157d13a3718868732e6c86110d699c6fc8b9087b08774611240700a5718bb pivx-3.0.6-arm-linux-gnueabihf.tar.gz
f49d4f3140b7231539a40b2704487940f2520654b48684eaef50cc52d56fda68 pivx-3.0.6-i686-pc-linux-gnu.tar.gz
80677ac9c9c6b0656fd9c6c8958d5e00518ab2f3fb4baddf024d7ea11b16df5b pivx-3.0.6-osx64.tar.gz
5eedaa29157f586ea28f0b558ff526bae6d164a5cafacb4f65f871625d8249d5 pivx-3.0.6-osx-unsigned.dmg
87fafd709e602537c4e9d4f02b397181c82e260d967fa4d50fb0813d30117bc0 pivx-3.0.6.tar.gz
a1e58750b217ab8a1ca12e2f157c92de652c664221f79731453540c3a9a175b1 pivx-3.0.6-win32-setup-unsigned.exe
970e08bf934daf00612b3bb53c71b063bbc952a9b9f26f7f813307f00fcb4e71 pivx-3.0.6-win32.zip
2ae1e5f9e6b7ca6119891fd09713b3fca53d52f4c36bb84b4528a4b9440b88ec pivx-3.0.6-win64-setup-unsigned.exe
f113435a0e514bf3d8ac7a0186d9013a5dbfe95fe2000111b8a03abb508f8870 pivx-3.0.6-win64.zip
1b987933112560641ac3d8f9b56509ae5dcfc2df2179a1a07b6c9535744d8e58 pivx-3.0.6-x86_64-linux-gnu.tar.gz
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCAAGBQJaH52hAAoJEDvc2i2HqIHZfU0P/jHiqzOoZra2hDaqW/jnLTH9
/BNmeDxd4B1/zpYo/uHS/xML+IKuscp/VPWxJ9AYVX19FP7SZo4HLfjHfmEBggGO
weqNxHmK7Etik3kOqx6d+cTXG/7OLz2EPMEuJgrR1byfgg51j1eGTQ5jGnOSI/VU
NuG1CXr5CfUBJm8fxFqoQ+yb9nmkhqmNA0mbJyczg5q8bZcabUj1eviI9GVJB9Ck
5nncL74bK0Qthj15nfPhcRT8Du79m7QZ5vmR1uZDBWlxad36HGQ+wbd2w4A3U8gp
TM7tIiHpYKYSD1SmE0rz6OYkZJGYbV2dj0CEIBNJudYlSB72BFwgDFsW0b9LGuKn
VzqHUFSXgSykTjIQH12F57oe8sdLvtnIoX5CFSrHwNF5Q/8gJimGKyumg3u1TPYx
owq5WSeBxZOmSXasX1kR6zelBMulF5fKpzQU1jBPLhiRzp9Q+JWsyBET+69fj74f
IwOqEVKfAGSzTmcZvqA+Sf4yJAf7ijmxBrqYqgBbW+0av20sbheqUI7wCavRTa4y
Gyie85fvc6gVA58LaNbNdD2ZJoGSjf9lJdIKgMCnOFJXuocX6xsA4bY1rtjwKXRC
9xr4m9+mI8IM5vHvj1MSEPCWK3bDaoFRH8vFMbThNr7/e5EJ1LGo5cKQ5UQqR/cn
skuiUEGo+W6OBYP1RgRw
=3YAP
-----END PGP SIGNATURE-----

Please note, checksums do not rule out a Github level breach because the attacker could have replaced both the binaries and SHA256 file. That is where the PGP signature comes in. You can use the developers public keys to confirm that the SHA256 file was signed with their private key.

Tutorials

How to resync your blockchain cache

If your PIVX Core blockchain cache has become corrupt or forked, you may wish to resync it using one of the methods below. **Please note that during the sync your balance will show as 0 until near the end, this is normal and nothing is lost**

Preparation - Before trying any of the methods below, please consider these steps

  1. It is always a good idea to make new wallet.dat and zPIV seed backups
  2. Make sure you are running the latest version of PIVX Core. Running old software can be a reason that your wallet forked in the first place and it will likely fork again if you have not updated.

Method 1 - Resync the blockchain from scratch
(Takes the longest, but it is the easiest. This method will sync you from block 1 and your computer will download and validate every block. CPU and bandwidth heavy)
Graphic User Interface (GUI) users:
"Tools > Wallet Repair > Delete Local Blockchain Folders (-resync)" to initiate the full re-sync.
Command line users:
You can initiate the full resync during daemon startup with the command switch `pivxd -resync`

Method 2 - Use a bootstrap
(Medium Difficulty: Takes a medium amount of time to resync. This will provide a zip that your computer can import and validate blocks from that will save on bandwidth. CPU heavy)
https://pivx.freshdesk.com/support/solutions/articles/30000021125-using-the-bootstrap

Method 3 - Restore a snapshot
(Medium Difficulty: Takes almost no time to sync because it is not downloading or validating any blocks. Instead you are trusting the data in the snapshot is correct)
https://pivx.freshdesk.com/support/solutions/articles/30000026470-how-can-i-use-a-snapshot-

Method 4 - Manual Resync
(Medium Difficulty: Only use this option if all others have failed. Your computer will download and validate all new blocks. CPU and bandwidth heavy)

  1. Gracefully shut down your PIVX wallet
  2. Navigate to your PIVX data directory and delete ONLY the files noted in the follow image:
    (Do NOT delete backups, masternode.conf, pivx.conf, or wallet.dat)

pivx11.PNG

3. Now re-launch the wallet and wait for it to sync. This can take few hours on slower computers or internet connections.


After you have finished syncing your PIVX blockchain, you can create a snapshot to save yourself some time in the future if you need to resync: https://pivx.freshdesk.com/support/solutions/articles/30000004666-how-do-i-make-a-backup-of-the-blockchain-so-i-can-avoid-a-full-resync-if-something-goes-wrong-


 

 

Tutorials

How to backup or restore your zPIV seed

 


What is a zPIV seed?
PIVX's dzPIV (deterministic zPIV) technology greatly simplifies your backup scheme. Instead of a new backup after every mint, you can back up the seed once and you'll have a failsafe copy for all activity based on that seed in case it's ever needed.
For more information about dzPIV, see the guide here


How to backup your seed
GUI (Graphic User Interface)

  1. If your wallet is encrypted, unlock the wallet with Settings-> Unlock Wallet. Make sure that you uncheck for staking an anonymization only
  2. Go Tools -> Debug Console -> Console
  3. Type getzpivseed
  4. Your zPIV seed will be output to the console. The seed is a 64 character hexadecimal string (256bit). It is not a mnemonic phrase. Backup this seed in a safe location, preferably offline.

CLI (Command Line Interface)

1. Make sure your wallet is fully unlocked (not just for staking) by using the command. On Linux, use a space at the beginning so your passphrase isn't saved in your shell history

pivx12.PNG

2. Use getzpivseed to output your seed string. Store this securely and never share it because it provides access to all your current and future zPIV

pivx13.PNG


How to restore your seed

Using the zPIV Seed to restore the information about your zPIV is computationally expensive, it can take several hours to restore all of the coins. Although it requires a lot of computation, it does provide a good fail safe in the case of wallet corruptions, machine failure, or other situations.

Importing a seed
Important Warning: It is extremely important that if you are importing a seed, you should be aware that you are setting the wallet's current seed to 'inactive'. Right now the wallet is only coded to handle one seed at a time. If the wallet you import to has zPIV generated by a different seed, then these zPIV will not be spendable until you switch the seed back.
Using the RPC command setzpivseed to replace the wallets existing seed with the seed you are importing. Please read the warning above before doing this!
As seen above, a dzPIV is comprised of your master zPIV seed and the count the coin is in the sequence. If you know that you have only generated a few zPIV, the wallet will likely automatically detect those for you because it will pregenerate the public value of the zPIV (called PublicCoin within the codebase) and will search the blockchain for any knowledge of that zPIV.

Extended Search
If the automatic import does not work, there are likely gaps in your generation sequence. For example when staking zPIV, you may have had 20 orphans in a row, thus bumping the count up by 20 without any of those Public Coins making it onto the blockchain. In this situation, you are able to tell your wallet to search a certain count range on the blockchain.
In this example, I think my wallet generated up to count 100. I import my zPIV seed to a fresh wallet.dat using RPC command setzpivseed

pivx14.PNG

The wallet automatically generates mints 1-20 and checks the chain for those values. If it finds that count 15 was used and on the blockchain, it will then generate up to 35 (keeping a buffer of 20) and check if any of those were added to the chain. The wallet loops through that process until no coins are found in the buffer of 20.
After the wallet stops syncing dzPIV, I type in command dzpivstate which will return something like this:

pivx15.PNG

My wallet stopped generating at 35, but I suspect my mints could be all the way up to count 100. I tell the wallet to generate up to count 100. I want the wallet to start at count 35 because I have already generated up to count 35. I want my wallet to generate an additional 65 zPIV so that it will check up to count 100. Searching for zPIV takes computation, so I am going to run it on two threads. I type the following command searchdzpiv

pivx16.PNG

When the process is finished it will return the message done. I can now use dzpivstate to see what the current count is (the last found zPIV added to the blockchain + 1). I can also go to the Privacy Dialog and check that my zPIV have been added.

Tutorials

Troubleshooting PIVX Core Wallet startup issues

Symptoms
Your PIVX wallet software does not start. When you try to run it nothing happens, an error is displayed, the window disappears, the loading window never completes, or another startup issue is encountered.

Cause

An abnormal exit of the wallet could result in corruption of your local blockchain cache. This can happen due to a power loss, unexpected reboot, OS updates, or if the local blockchain cache becomes corrupt by other means.

Resolution

Method 1

  1. Make a backup of your wallet.dat file and zPIV seed (Best practices)
  2. Make sure you are running the latest PIVX Core software
  3. Try using the -forcestart startup flag to see if it will recover from a failed start.
    In the Windows GUI, you will need to make a shortcut to the pivx-qt.exe file

pivx17.PNG

Then, edit the shortcut properties and append it to the end of the "Target" field, so that the end reads:pivx-qt.exe" -forcestart

pivx18.PNG

From the command line on all operating systems you can call the pivxd daemon with the switch -forcestart

Method 2
If Method 1 does not resolve the startup issue, try to resync the blockchain using the steps in this link

 

Tutorials

How to open and use the debug console

What is the debug console?

The debug console is a way to use advanced features of the wallet while in the pivx-qt GUI. It is similar to how a command-line user would issue RPC commands using pivx-cli.

How do I open the debug console?

To open the debug console, you'll use 'Tools > Debug Console' as shown below:

  1. In your wallet's menu (usually in the top left of the window or screen depending on your OS), select Tools. It should be listed among File, Settings, Tools, and Help.

pivx19.PNG

2. Once you click tools, select Debug console and you should see a window appear similar to the one below:

pivx20.PNG

3. Once here, go ahead and enter commands at the bottom where noted in the image.

To use the debug menu, type "help" for a list of commands or reference this article: https://pivx.freshdesk.com/support/solutions/articles/30000020865-debug-console-command-line

Common Errors

Common Errors

Assertion and block failures

Symptoms
Any of the following error messages:

Assertion failed!

Expression: !setBlockIndexCandidates.empty()

Expression: hashPrevBlock == view.GetBestBlock()

pivx-qt: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.

pivxd: main.cpp:2300: bool ConnectBlock(const CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool): Assertion `hashPrevBlock == view.GetBestBlock()' failed.

Failed reading from database. PcoinsTip best block is not correct. The block database is in an inconsistent state and may cause issues in the future. To force start use -forcestart

(OSX) A fatal error occurred. PIVX can no longer continue safely and will quit
Exception: St13runtime_error TopupKeyPool() : writing generated key failed
pivx in Runaway exception

Cause
An abnormal exit of the wallet could result in a blockchain inconsistency from that point forward. This can happen due to a PC reboot without first closing the wallet gracefully or if the local copy of the blockchain became corrupted (due to environmental issues etc) and caused the wallet to crash.


Solution
To fix the problem with your local copy of the blockchain, follow these instructions
https://pivx.freshdesk.com/support/solutions/articles/30000004661-wallet-crashes-or-has-crashed-and-now-won-t-launch-fails-every-time-what-do-i-do-

 

Common Errors

My passphrase is not working / Forgotten passphrase

The simple fix for you never to forget your password!

Make sure it is written down and is correct. There is no fix for a typo'd password as something like this would be an obvious security flaw.

If you believe you have been inputting the right password, please try common typos you could commit. This includes hitting the wrong letters next to the one you pressed.

Common Errors

The wallet was unlocked only to anonymize coins

Symptom

When trying to send coins or optimize for staking the following error appears:

pivx21.PNG

Cause

The wallet was unlocked, but only for staking. This is a security measure that allows you to stake safely without opening up your coins to easy theft.

Solution

To continue, you will need to lock your wallet (which stops staking) and then fully unlock it.

For the GUI or qt wallet, you can follow these steps:

1. Select Settings > Lock Wallet
2. Select Settings > Unlock Wallet
3. Provide your passphrase as requested and do not check 'For anonymization and staking only'
4. You should be able to proceed without the error

For the command line wallet, you can follow these steps (more info here):

1. Enter pivx-cli walletlock
2. Enter pivx-cli walletpassphrase <your passphrase> <timeout in seconds, 0 for indefinite> <true/false unlock for staking/anon only>

In other words: pivx-cli CorrectHorseBatteryStaple 0 false

Now you should be able to proceed without the error

Common Errors

PIVX client or daemon crashes on startup or randomly

Symptoms

The PIVX software crashes out with no error message or log file entries on startup or at random intervals


Cause

This is often caused by a memory shortage


Solution

As of v3.0.0, zerocoin does have slightly higher memory requirements. Minimum specs have not been published, but 2GB RAM on linux and 4GB on Windows and Mac seem to run ok. As more data comes in this article can be updated

Common Errors

Command line error: code 32601 message: Method not found

Symptoms

Attempts to start the daemon and check the status with getinfo on command line return:
error: code 32601 message: Method not found


Cause

The PIVX daemon is not running properly


Solution

Use the -daemon switch when starting pivxd:

Example:

pivx22.PNG

Common Errors

Known Error: st13runtime_error

Symptoms:

A similar error appears on startup or in a debug log:

pivx23.PNG

Cause:

A bug in the code for invalidating fraudulent zPIV spends


Resolution:

Update to v3.0.5.1 or newer. If you have problems syncing, follow the instructions in the link

https://github.com/PIVX-Project/PIVX/releases/tag/v3.0.5.1

Common Errors

coinspend: accumulator witness does not verify

Symptoms:

When trying to spend zPIV, the following error appears: coinspend: accumulator witness does not verify

Cause:

A bug in v3.0.5 and v3.0.5.1 affecting some users

Solution:

This issue is resolved beginning with the v3.0.6 release and the binaries are available here

In the Privacy tab, set the security to 100 and rescan/reset the the wallet. If not solved, re-open the wallet and ensure the wallet is completely synced.

Open a ticket if issue isn't fully solved

Common Errors

I've banned all my peers and now I can't sync

Symptoms

The PIVX Core wallet will not sync and you are not getting any peers or find all new peers are added to your banlist.


Cause

This can be caused by running a forked chain or old wallet. Your wallet would not accept any of the blocks the real network provides it and bans everyone.

There is currently a bug going around where an improper shutdown can cause bad data in the zerocoin cache, resulting in rejection of all blocks and banning peers as outlined above. Luckily the devs have identified the issue, created the fix, and pulled it into the master branch on github so it will be included in the next update.


Resolution
Make sure you are running the latest wallet software from: https://pivx.org/wallet/

Make sure you are not forked off onto the incorrect chain: https://pivx.bitcoiner.me/am-i-forked/
If you are forked, please follow the steps on this page: https://pivx.freshdesk.com/support/solutions/articles/30000029354-how-to-resync-your-blockchain-cache

pivx-qt (GUI): Use the debug dialog to enter the command 'clearbanned'
pivx-cli (CLI): Use the command "pivx-cli clearbanned"

See if your wallet starts syncing within a few minutes, otherwise proceed to step 4

Follow the steps in this link and use Method 4: https://pivx.freshdesk.com/support/solutions/articles/30000029354-how-to-resync-your-blockchain-cache

Your wallet will sync from scratch and you should be all set. If not, please contact support