Skip to content

HTTPS clone URL

Subversion checkout URL

You can clone with
or
.
Download ZIP
TypeScript C++ C Python IDL Shell Other
Branch: master

Fetching latest commit…

Cannot retrieve the latest commit at this time

Failed to load latest commit information.
contrib Phicoin Genesis
doc
share
src
COPYING
INSTALL
README.md Update README.md
bitcoin-qt.pro

README.md

Phicoin integration/staging tree

http://phicoin.cc

What is Phicoin?

Phicoin is a scrypt version of Bitcoin using scrypt as a proof-of-work algorithm.

  • 2.5 minute block targets
  • 25 block difficulty retargets
  • 1.6 Coins per block
  • Subsidy halves in 70K Blocks
  • ~569 thousand total coins
  • Default RPC Port: 1741
  • Default P2P Port: 1744
  • Addresses Begin with P

The rest is the same as Bitcoin.

For more information, as well as an immediately useable, binary version of the Phicoin client sofware, see http://phicoin.cc

License

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

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 Phicoin 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 (if they haven't already) on the mailing list.

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 Phicoin.

Testing

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 bitcoin-qt.pro
make -f Makefile.test
./phicoin-qt_test
Something went wrong with that request. Please try again.