Kore Core integration/staging tree
Branch: momentum
Clone or download
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx qt: translation update prior to opening 0.12 translations Nov 1, 2015
build-aux/m4 Initialize Kore Oct 14, 2017
contrib Initialize Kore Oct 14, 2017
depends v0.12.4.0 Jan 13, 2018
doc updated README.md Apr 12, 2018
qa Initialize Kore Oct 14, 2017
share Initialize Kore Oct 14, 2017
src removed IP reference in masternode.conf generation Aug 9, 2018
.gitignore Initialize Kore Oct 14, 2017
.travis.yml [qa] Switch to py3 Jul 15, 2016
CONTRIBUTING.md Initialize Kore Oct 14, 2017
COPYING Initialize Kore Oct 14, 2017
INSTALL Initialize Kore Oct 14, 2017
Makefile.am Initialize Kore Oct 14, 2017
README.md corrected README.md Apr 12, 2018
autogen.sh Bugfix: Replace bashisms with standard sh to fix build on non-BASH sy… Oct 3, 2014
configure.ac blocked old wallets from connecting to the network. Aug 7, 2018
easyinstall.sh added easyinstall.sh Jun 27, 2018
libkoreconsensus.pc.in Initialize Kore Oct 14, 2017


Kore Core integration/staging tree

Build Status


What is Kore?

Kore is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Kore uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Kore Core is the name of open source software which enables the use of this currency.


Kore Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

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 Kore Core.

The contribution workflow is described in CONTRIBUTING.md.


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

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.


Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

If you have a translation request please reach out via email or through Discord or through Telegram.