Skip to content
Branch: master
Clone or download
Pull request Compare This branch is 313 commits ahead, 245 commits behind zetacoin:master.
Latest commit 17ff4af Jun 25, 2018
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx tx: change slug to `bitcoin.qt-translation-013x` Jun 28, 2016
build-aux/m4
contrib Update gitian descriptors Mar 24, 2018
depends Fix wake from sleep issue with Boost 1.59.0 Oct 7, 2016
doc Release process doc Mar 24, 2018
qa
share Merge changes from Bitcoin 0.13.2 into Skeincoin Mar 18, 2018
src 0.13.2.2 Jun 25, 2018
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore Update gitignore Mar 18, 2018
.travis.yml
CONTRIBUTING.md [doc] Add basic git squash example May 10, 2016
COPYING Merge changes from Bitcoin 0.13.2 into Skeincoin Mar 18, 2018
INSTALL.md Update INSTALL landing redirection notice for build instructions. Dec 2, 2016
Makefile.am Merge changes from Bitcoin 0.13.2 into Skeincoin Mar 18, 2018
README.md
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh Oct 27, 2016
configure.ac
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015

README.md

Skeincoin Core integration/staging tree

https://www.skeincoin.co

What is Skeincoin?

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

License

Skeincoin Core 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 Skeincoin 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 developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

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

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, 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 can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

You can’t perform that action at this time.