Create proof of existence chain for images & File Crypto!
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Failed to load latest commit information.
.settings sub Jul 22, 2018
.tx Initial commit Jul 22, 2018
bin sub Nov 5, 2018
build-aux/m4 sub Nov 5, 2018
build-dash-qt-dat-Debug qt Aug 6, 2018
build-dash-qt-dat-Release sub Aug 6, 2018
contrib sub Aug 11, 2018
depends sub Nov 4, 2018
doc Update Aug 11, 2018
docs Initial commit Jul 22, 2018
imginstall Update Aug 1, 2018
qa Initial commit Jul 22, 2018
share sub Jul 22, 2018
src sub Nov 9, 2018
.classpath Initial commit Jul 22, 2018
.cproject Merge branch 'master' of Aug 13, 2018
.gitattributes Initial commit Jul 22, 2018
.project sub Jul 22, 2018
.travis.yml Initial commit Jul 22, 2018 Initial commit Jul 22, 2018
COPYING Initial commit Jul 22, 2018
INSTALL Initial commit Jul 22, 2018
LICENSE Initial commit Jul 22, 2018 sub Jul 22, 2018 Update Jul 22, 2018
aclocal1.11 sub Aug 6, 2018 sub Aug 6, 2018 sub Nov 6, 2018 sub Aug 6, 2018


This project consist create a blockchain to images buying/share/signed.

Sign Images APP Website

ImageCoin Core staging tree

Copyright (c) 2009-2016 Bitcoin Core Developers

Copyright (c) 2014-2017 Dash Core Developers

Copyright (c) 2018- ImageCoin Core Developers

What is ImageCoin?

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


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

Building process

compiling ImageCoin from git

Use the autogen script to prepare the build environment.


Always verify the signatures and checksums.

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure with CXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.


If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging message are written there.

The -debug=... command-line option controls debugging; running with just -debug will turn on all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play ImgCashs" on the test network, if you are testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option. In regression test mode blocks can be created on-demand; see qa/rpc-tests/ for tests that run in -regtest mode.


SibCore is a multithreaded application, and deadlocks or other multithreading bugs can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configure CXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of what locks are held, and adds warning to the debug.log file if inconsistencies are detected.