This project consist create a blockchain to image buying/share/signed (Image Cash)
Branch: master
Clone or download
Latest commit e591189 Feb 5, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
.settings sub Jun 16, 2018
.tx Initial commit Jun 14, 2018
.vscode sub Jun 14, 2018
IMGCInstall Update Feb 5, 2019
bin sub Aug 13, 2018
build-aux/m4 sub Jun 19, 2018
contrib sub Jun 19, 2018
depends Add files via upload Jun 16, 2018
doc Add files via upload Sep 23, 2018
docs sub Jun 27, 2018
qa Initial commit Jun 14, 2018
share sub Jun 28, 2018
src sub Nov 2, 2018
.classpath Initial commit Jun 14, 2018
.gitattributes Initial commit Jun 14, 2018
.gitignore Initial commit Jun 14, 2018
.travis.yml Initial commit Jun 14, 2018 Initial commit Jun 14, 2018
COPYING Initial commit Jun 14, 2018
INSTALL Initial commit Jun 14, 2018
LICENSE Initial commit Jun 14, 2018 sub Jun 16, 2018 Update Jul 5, 2018 Initial commit Jun 14, 2018 Update Jun 21, 2018 Create Nov 27, 2018
libimgcashconsensus.pc add by l Aug 13, 2018 Initial commit Jun 14, 2018


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

Sign Images APP Website

ImgCash Core staging tree

Copyright (c) 2009-2016 Bitcoin Core Developers

Copyright (c) 2014-2017 Dash Core Developers

Copyright (c) 2018- ImgCash Core Developers

What is ImageCash?

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


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

Building process

compiling ImgCash 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.