Pakistan's First cryptocurrency
C++ Python HTML C Roff Shell Other
Switch branches/tags
Nothing to show
Clone or download
Failed to load latest commit information.
contrib changed Jun 6, 2015
doc changed Jun 6, 2015
qa/rpc-tests changed Jun 6, 2015
share changed Jun 6, 2015
src Adjust for libboost 1.58 Feb 22, 2018
COPYING changed Jun 6, 2015
COPYING~ changed Jun 6, 2015
INSTALL changed Jun 6, 2015
INSTALL~ changed Jun 6, 2015 Update Feb 12, 2018 Updated to DGW Jun 8, 2016

Pakcoin integration/staging tree

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2015-2018 Pakcoin Developers

What is Pakcoin?

Pakcoin is a Digital Currency for Pakistan, using scrypt as a proof-of-work algorithm.

  • 1 minute block targets
  • subsidy halves in 3 years
  • 182 million total coins
  • 50 coins per block
  • 1 block to retarget difficulty using DGW.

For more information, as well as an immediately useable, binary version of the Pakcoin client sofware, see


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

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Pakcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion with the devs and community.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.txt) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Pakcoin.


Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, 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 for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test
make -f Makefile.test