-
-
Notifications
You must be signed in to change notification settings - Fork 650
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PIVX Blockbook issue - returning wrong hash #985
Comments
@martinboehm hi |
Hi @ianlapinskii
Any idea how to run PIVX backend? |
You need to run install-params.sh from the directory where install-params.sh is. ... In script is |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context:
When we’re using /utxo method for
DCYCfV1eRi71RH6Wwzhn7ZkvCyaKujZVsh
address, it returns withdc79888b84087663a9c3b5f480d2a156a5827d3dbe65e36154bea4a1de79a1b2.
The problem is that this transaction doesn’t exist, the node should return
c0acc395cd15d61d2e69755a31be7b4a93581071aaeb5eeadd71d7475f2572a6
We also tried /tx request, it returns with
"Transaction 'dc79888b84087663a9c3b5f480d2a156a5827d3dbe65e36154bea4a1de79a1b2' not found"
. Which is logical, as this transaction doesn’t exist. However, the node keeps returning with it for this address. Another anomaly is that /utxo method works properly, for example, withDPjhZHMXPWDPLBkf5BoVNs1Msg4ovTwJVi
addressWhat we tried:
We resynced our PIVX blockbook - nothing changed. Contacted PIVX development team - no luck to find assistance.
Question:
Could you please take a look and let us know when the fix will be available?
The text was updated successfully, but these errors were encountered: