Prospercoin classic source tree
C++ Python HTML C Roff QMake Other
Switch branches/tags
Clone or download
Pull request Compare This branch is 4 commits ahead, 16055 commits behind litecoin-project:master.
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Failed to load latest commit information.
contrib ProsperX Initial Git Aug 14, 2017
doc
share
src Make leveldb compile working again May 14, 2018
.gitattributes ProsperX Initial Git Aug 14, 2017
.gitignore ProsperX Initial Git Aug 14, 2017
COPYING ProsperX Initial Git Aug 14, 2017
INSTALL ProsperX Initial Git Aug 14, 2017
README.md ProsperX Initial Git Aug 14, 2017
bitcoin-qt.pro ProsperX Initial Git Aug 14, 2017

README.md

PROSPER integration/staging tree

http://prosper.inmean.com

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2014 Litecoin Developers Copyright (c) 2014-2014 Propercoin Developers

What is Litecoin?

TBC

License

Prospercoin 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 Litecoin 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 Litecoin.

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