No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
build
contrib
doc
qa/rpc-tests
share
src
COPYING
INSTALL
Makefile
Phoenix-qt.pro
README.md
phoenix-qt
phoenix-qt.dmg
phoenix-qt.exe

README.md

Phoenix integration/staging tree

Copyright (c) 2018 Phoenix Developers

What is Phoenix?

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

For more information, as well as an immediately useable, binary version of the Phoenix client sofware, see http://www.phxcoin.org

License

Phoenix 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 Phoenix 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 regularly created to indicate new official, stable release versions of Phoenix

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
./phoenix-qt_test