Skip to content

PIVX Blockbook issue - returning wrong hash #985

@ianlapinskii

Description

@ianlapinskii

Context:

When we’re using /utxo method for DCYCfV1eRi71RH6Wwzhn7ZkvCyaKujZVsh address, it returns with dc79888b84087663a9c3b5f480d2a156a5827d3dbe65e36154bea4a1de79a1b2.

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, with DPjhZHMXPWDPLBkf5BoVNs1Msg4ovTwJVi address

What 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?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions