Skip to content
Helping children get an education around the world
Branch: master
Clone or download
Latest commit 108f98b Feb 18, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.tx First commit Feb 15, 2019
build-aux/m4 First commit Feb 15, 2019
contrib First commit Feb 15, 2019
depends First commit Feb 15, 2019
doc First commit Feb 15, 2019
docker First commit Feb 15, 2019
educoin-docs First commit Feb 15, 2019
qa First commit Feb 15, 2019
share First commit Feb 15, 2019
src Main chain release Feb 18, 2019
.gitattributes First commit Feb 15, 2019
.gitignore First commit Feb 15, 2019
.travis.yml First commit Feb 15, 2019
CMakeLists.txt First commit Feb 15, 2019 First commit Feb 15, 2019
COPYING First commit Feb 15, 2019 First commit Feb 15, 2019 First commit Feb 15, 2019 First commit Feb 15, 2019 First commit Feb 15, 2019 First commit Feb 15, 2019

Educoin Core staging tree 0.12.3

master: Build Status develop: Build Status

What is Educoin?

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


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

Development Process

The master branch is meant to be stable. Development is normally done in separate branches. Tags are created to indicate new official, stable release versions of Educoin Core.

The contribution workflow is described in


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. Further details on running and extending unit tests can be found in /src/test/

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/

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

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.


Changes to translations as well as new translations can be submitted to Educoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

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

Translators should also follow the forum.

You can’t perform that action at this time.