Skip to content
The IoP blockchain client reimplemented.
Branch: master
Clone or download
Pull request Compare This branch is 446 commits ahead, 5211 commits behind bitcoin:master.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github
.tx replaced bitcoin->iop in files Sep 30, 2017
build-aux/m4
contrib
depends
doc updated release notes Mar 12, 2019
share changed icons to new logo Mar 12, 2019
src Merge branch 'newmining' into v6.3.0 Mar 12, 2019
test
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore
.travis.yml
CONTRIBUTING.md
COPYING Put back inadvertently removed copyright notices Oct 3, 2017
INSTALL.md
Makefile.am
README.md
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh Sep 21, 2016
configure.ac
libiopconsensus.pc.in renamed forgotten file Sep 30, 2017
pack-common.sh
pack-ubuntu1404.sh fixed dependencies ubuntu14 Oct 15, 2017
pack-ubuntu1604.sh fixed dependencies ubuntu16 Oct 15, 2017
pack-ubuntu1610.sh updated release notes and bumped package Oct 21, 2017
pack-ubuntu1804.sh

README.md

IoP Core integration/staging tree

Build Status

https://iop.global

RELEASE NOTE v6.3.0

The IoP Blockchain client version 6.3.0 is now available

Changes

  • Updated user interface with the new logo.
  • Updated subsidy calculation with lower halving interval. Additional rewards compensate for lower halving interval and coins lost to fermat beta mining. Max Supply is now just below 21 million IOP, as initially planned. This version will hard fork from previous versions on block 149999. Please update as soon as possible.

RELEASE NOTE v6.2.0

We are proud to announce a complete redesign of the IoP Core wallet. You can now buy IOP directly from inside the wallet software thanks to our collaboration with Indacoin.

RELEASE NOTE v6.1.0

This major release is meant to replace the old version of the IoP Blockchain client. While the consensus remains fully compatible, the structure of the data directory does not. Please read the release notes very carefully if you update from version 5.0.1 or below.

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.

License

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

The contribution workflow is described in CONTRIBUTING.md.

The Discord channel should be used to discuss complicated or controversial changes before working on a patch set.

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

There are also regression and integration tests, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: test/functional/test_runner.py

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.

You can’t perform that action at this time.