$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.
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.
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.
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.
Go to your VPS and execute this:
wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pacmn.shchmod +x pacmn.sh./pacmn.sh
Follow the instructions and: Enter your external IP Enter your masternode genkey The script will setup the environment and run your masternode
Go to your VPS and execute the following commands on the command line:
wget https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.shchmod +x pac-update.sh./pac-update.sh
Or run this single line to execute the previous commands in one go:
wget -q -O- https://raw.githubusercontent.com/PACCommunity/PAC/master/pac-update.sh | bash
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
-
Open your command line and run the following command:
MacOS:
curl https://raw.githubusercontent.com/PACCommunity/PAC/master/contrib/masternodetools/PacNodesUpdater.tar.gz -o PacNodesUpdater.tar.gz && tar -xzf PacNodesUpdater.tar.gz && cd PacNodesUpdaterLinux:
wget https://raw.githubusercontent.com/PACCommunity/PAC/master/contrib/masternodetools/PacNodesUpdater.tar.gz && tar -xzf PacNodesUpdater.tar.gz && cd PacNodesUpdater -
Open and edit the nodes.csv file by adding the following data in order to login to the each node:
-
hostname: This is the user name used to login to the node (ssh user)
-
ip: Is the address of the node, be it an url or an IP address
-
password: It is the password used by the ssh user to authenticate in the node
Example in order to update 2 nodes the csv table will look like this:
hostname ip password john 192.168.1.1 12345 node2 198.39.0.1 12345
-
-
Go back to the command line and run the following command:
chmod +x updateMNs.sh && ./updateMNs.sh
Notes: Keep an eye on the execution as the script might ask you for confirmation or passwords to authorize certain actions.