No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
Latest commit 2ca4f67 Sep 18, 2016
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
contrib Add files via upload Aug 18, 2016
doc Add files via upload Aug 18, 2016
share Add files via upload Aug 18, 2016
src Update net.cpp Sep 18, 2016
.gitattributes Create .gitattributes Aug 18, 2016
.gitignore Create .gitignore Aug 18, 2016
COPYING Add files via upload Aug 18, 2016
INSTALL Add files via upload Aug 18, 2016
Makefile Add files via upload Aug 18, 2016
README.md Add files via upload Aug 18, 2016
dollarcoin-qt.pro Add files via upload Aug 18, 2016

README.md

dollarcoin integration/staging tree

http://www.dollarcoin.org

Copyright (c) 2009-2013 dollarcoin Developers

What is dollarcoin?

dollarcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. dollarcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. dollarcoin is also 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 dollarcoin client software, see http://www.dollarcoin.org.

License

dollarcoin 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 dollarcoin 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.md) 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 dollarcoin.

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 dollarcoin-qt.pro
make -f Makefile.test
./dollarcoin-qt_test

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by dollarcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.

See https://github.com/dollarcoin/QA/ for how to create a test plan.