No description or website provided.
C++ Python HTML C Groff Shell Other
Latest commit b033d65 Jan 3, 2017 @SCNPay committed on GitHub New Updates
Failed to load latest commit information.
contrib initial commit1 Apr 11, 2016
doc Update Info Dec 29, 2016
qa/rpc-tests initial commit1 Apr 11, 2016
share initial commit1 Apr 11, 2016
src Node Added Jan 3, 2017
.gitattributes Added files via upload Apr 11, 2016
.gitignore Added files via upload Apr 11, 2016
COPYING Update Info Dec 29, 2016
INSTALL Added files via upload Apr 11, 2016 New Updates Jan 3, 2017 Added files via upload Apr 11, 2016

Swiscoin integration/staging tree

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

Important News

We have fixed BlockChain fork Issue and Updated Protocol Version from 70002 to 71003. Difficulty algorithm changed to DGW.. Changes take effect on Jan 25, 00:00:00 GMT.

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


Swiscoin is released under the terms of the MIT license. See COPYING for more information or see

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 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
make -f Makefile.test