No description, website, or topics provided.
C++ Python HTML C Roff Shell Other
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.
contrib
doc
qa/rpc-tests
share
src
.gitattributes
.gitignore
COPYING
INSTALL
README.md
swiscoin-qt.pro

README.md

Important News

Swiscoin SCN will no longer available after March 15 2017 00:00:00 GMT. New Swiscoin will be available on https://github.com/SCNPay/Swiscoin-Master that is MSCN. Users can swap SCN to MSCN on www.swiswallet.com before 15 March 2017.

Swiscoin integration/staging tree

http://www.swisopensource.com

Copyright (c) 2009-2014 Bitcoin Developers Copyright (c) 2011-2014 Litecoin Developers Copyright (c) 2015-2017 Swiscoin Developers

What is Swiscoin?

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

  • 60 minutes block targets

  • subsidy halves in 840k blocks (~4 years)

  • ~3.1 billion total coins

  • 12 coins per block

  • 10 blocks to retarget difficulty

For more information, as well as an immediately useable, binary version of the Swiscoin client sofware, see http://www.swisopensource.com

License

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

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