Acoin (POD-CryptoAsian)
TypeScript C++ C Python Shell Objective-C++
Switch branches/tags
Nothing to show
Clone or download
acoin-project
acoin-project Checkpoint
Latest commit d8f6c1a Oct 23, 2014
Permalink
Failed to load latest commit information.
contrib Initial commit Sep 1, 2014
doc Initial commit Sep 1, 2014
qa Initial commit Sep 1, 2014
share Initial commit Sep 1, 2014
src Checkpoint Oct 23, 2014
.gitattributes Initial commit Sep 1, 2014
.gitignore Initial commit Sep 1, 2014
COPYING Initial commit Sep 1, 2014
INSTALL Initial commit Sep 1, 2014
Makefile.am Initial commit Sep 1, 2014
README.md Fix URL Sep 13, 2014
autogen.sh Initial commit Sep 1, 2014
configure.ac Checkpoint Oct 23, 2014
pkg.m4 Initial commit Sep 1, 2014

README.md

Acoin integration/staging tree

http://www.a-coin.info

Copyright (c) 2009-2013 Bitcoin Developers

Copyright (c) 2014 Acoin Developers

What is Acoin?

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

For more information, as well as an immediately useable, binary version of the Acoin Core software, see http://www.a-coin.info

License

Acoin Core is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Acoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.md) or are controversial.

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

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.

debug.log

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 bitcoins" 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 -regest mode.

DEBUG_LOCKORDER

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