The official Internet of People cryptocurrency
Branch: master
Clone or download
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 switched to bdb5.3 May 28, 2017
contrib bumped to 5.0.1 Sep 25, 2017
depends fixed building for win May 28, 2017
doc more replacement of fermat info Jun 10, 2017
qa fixed wrong replacement Jun 10, 2017
share new logo Jun 23, 2017
src bumped to 5.0.1 Sep 25, 2017
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore added new MinerCap system May 9, 2017
.travis.yml fix and simplify Travis CI integration Aug 2, 2017
CNAME Create CNAME Jun 21, 2017 String replacement from bitcoin to IoP in all directories. Sep 8, 2016
COPYING update license template Aug 8, 2017
INSTALL String replacement from bitcoin to IoP in all directories. Sep 8, 2016 Update Jun 30, 2017 started removing fermat references Jun 10, 2017 fixed wrong replacement Jun 10, 2017 more replacement of fermat info Jun 10, 2017 update title and license Aug 8, 2017 bumped to 5.0.1 Sep 25, 2017
_config.yml Set theme jekyll-theme-midnight Jun 21, 2017 warn about needing autoconf if autoreconf is not found Feb 12, 2016 bumped to 5.0.1 Sep 25, 2017 String replacement from bitcoin to IoP in all directories. Sep 8, 2016 bumped to 5.0.1 Sep 25, 2017 Fixed 14.04 package dependencies, real mail address Sep 20, 2016 fixed 16.04 dependency Sep 28, 2016 Support for Ubuntu 16.10 Apr 4, 2017

IoP Core

Build Status

What is IoP?

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

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

The contribution workflow is described in

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.


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/

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


Please read the installation document.


Copyright © 2009-2017 Libertaria Corp., Decentralized Society Foundation, IoP Ventures LLC

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

See COPYING for more information or see