Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
This branch is 9950 commits ahead, 12464 commits behind dashpay:master.

Latest commit

7547b30 [Build] Disable libsep256k1's openssl tests (Fuzzbawls)

Pull request description:

  Systems that have OpenSSL 3.x installed cause the lib's openssl based tests to fail. We don't use OpenSSL in PIVX anymore, so these tests are not of much interest.

  Ref: bitcoin#23314

ACKs for top commit:
    tACK 7547b30
    tACK 7547b30

Tree-SHA512: 7bc5fe16286946a851c81191ac07077f837515ff7055fe85cb77c48f92d7b1e73281f1034557184d5b07b7e61d218aa1ee55e48e5d6f6cc21f74033a85d85a5a


Failed to load latest commit information.
Latest commit message
Commit time

PIVX Core integration/staging repository

master Actions Status GitHub release (latest by date) GitHub Release Date

What is PIVX?

PIVX is an open source community-driven cryptocurrency, focused on five main aspects:

(1) User Data Protection: Through the use of SHIELD, a zk-SNARKs based privacy protocol.

(2) Low environmental footprint and network participation equality: Through the use of a highly developed Proof of Stake protocol.

(3) Decentralized Governance System: A DAO built on top of the tier two Masternodes network, enabling a monthly community treasury, proposals submission and decentralized voting.

(4) Fast Transactions: Through the use of fast block times and the tier two network, PIVX is committed to continue researching new and better instant transactions mechanisms.

(5) Ease of Use: PIVX is determined to offer the best possible graphical interface for a core node/wallet. A full featured graphical product for new and advanced users.

A lot more information and specs at Join the community at PIVX Discord.


PIVX Core is released under the terms of the MIT license. See COPYING for more information or see

Development Process

The master branch is regularly built (see doc/build-*.md for instructions) and tested, but it is not guaranteed to be completely stable. Tags are created regularly from release branches to indicate new official, stable release versions of PIVX Core.

The contribution workflow is described in and useful hints for developers can be found in doc/


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people a lot of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check. Further details on running and extending unit tests can be found in /src/test/

There are also regression and integration tests, written in Python. These tests can be run (if the test dependencies are installed) with: test/functional/`

The CI (Continuous Integration) systems make sure that every pull request is built for Windows, Linux, and macOS, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.


Changes to translations as well as new translations can be submitted to PIVX Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.


No packages published


  • C++ 50.9%
  • C 28.6%
  • Python 8.3%
  • Assembly 5.3%
  • M4 1.5%
  • CSS 1.2%
  • Other 4.2%