EmerCoin Official Development Tree
Clone or download
Pull request Compare This branch is 10254 commits ahead, 707 commits behind peercoin:master.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
.github Mention reporting security issues responsibly Nov 10, 2016
.tx qt: Set transifex slug to 0.14 Jan 2, 2017
bin change the target of the emc symlink Mar 1, 2017
build-aux/m4 Use zlib as library, remove from sources Dec 12, 2018
contrib Added emercoind-install.sh into contrib Jan 13, 2019
depends [depends] Don't build libevent sample code Nov 29, 2017
doc build: bump version to 0.7.4 Jan 14, 2019
qa [Wallet] unset change position when there is no change on exact match May 31, 2017
share Revert "test new icons" Jan 25, 2018
src openssl: replace outer executable with direct calls. Jan 17, 2019
.gitattributes Separate protocol versioning from clientversion Oct 29, 2014
.gitignore 'Manage DNS' - placeholder text, .gitignore += *.pro.user Apr 1, 2018
.travis.yml Test that pushes to bitcoin/bitcoin are signed per verify-commits Feb 1, 2017
CONTRIBUTING.md Merge #9675: Fix typo and spelling inconsistency in CONTRIBUTING.md Feb 16, 2017
COPYING Update license year 2019 Jan 1, 2019
INSTALL.md Update INSTALL landing redirection notice for build instructions. Oct 5, 2016
Makefile.am merge with bitcoin 0.14.2 Jul 10, 2017
README.md port changes from 0.6.3 Sep 4, 2017
autogen.sh Add MIT license to autogen.sh and share/genbuild.sh Sep 21, 2016
confFreeBSD.sh Particularly fixed ifdef ENABLE_WALLET Nov 24, 2018
configure.ac build: bump version to 0.7.4 Jan 14, 2019
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes Dec 14, 2015
push.sh Added push.sh Aug 9, 2016

README.md

Emercoin Core integration/staging tree

https://emercoin.com/

What is Emercoin?

Emercoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world and enables of storing information as key/value pairs in blockchain. Emercoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. For minting Emercoin uses Proof-of-Stake, Proof-of-Work and Auxilary-Proof-of-Work mechanisms. Emercoin 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 Emercoin Core software, see here.

License

Emercoin Core is released under the terms of the GPL3 license. See COPYING for more information or the GNU site.

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 Emercoin development team members simply pulls it.

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

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

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.

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 messages 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 emercoins" 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.

DEBUG_LOCKORDER

Emercoin 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 which locks are held, and adds warnings to the debug.log file if inconsistencies are detected.