$PAC - People's Alternative Choice
Branch: master
Clone or download
Pull request Compare This branch is 80 commits ahead, 1686 commits behind dashpay:master.
theRealDijida and alejandromgk Update pac-update.sh with ending message
Changed the ending disclaimer/directions to reduce confusion for those upgrading from 12.5->12.5.1 and inadvertently start their MN.
Latest commit a88795c Oct 31, 2018


$PAC Core staging tree


What is $PAC?

$PAC is an experimental new digital currency that enables anonymous, instant payments to anyone, anywhere in the world. $PAC uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. $PAC is the name of the open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the $PAC software, see https://wallets.paccoin.net/.


$PAC is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of $PAC.

The contribution workflow is described in CONTRIBUTING.md.


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 lots 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

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

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.

Setting up a masternode on a VPS (only for Cold wallet setup)

Go to your VPS and execute this:

  1. wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pacmn.sh
  2. chmod +x pacmn.sh
  3. ./pacmn.sh

Follow the instructions and: Enter your external IP Enter your masternode genkey The script will setup the environment and run your masternode

Updating a masternode on a VPS to the latest verion (only for Cold wallet setup)

Go to your VPS and execute the following commands on the command line:

  1. wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh
  2. chmod +x pac-update.sh
  3. ./pac-update.sh

Or run this single line to execute the previous commands in one go:

wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh && chmod +x pac-update.sh && ./pac-update.sh

Follow the instructions: 1)Do you want to autobackup wallet.dat and continue with the process? [y/n]: Type yes to backup and continue or no to stop process