No description, website, or topics provided.
Switch branches/tags
Nothing to show
Clone or download
madcoin-project Merge pull request #12 from gades/master
Proof of work MUST BE disabled on 24000
Latest commit d48282b Oct 12, 2018

README.md

MadcoinCoin [MDC] Source Code

http://www.madcoin.life

Copyright (c) 2009-2015 Bitcoin Core Developers

Copyright (c) 2014-2016 PivX Developers

Copyright (c) 2017-2018 MadcoinCoin Developers

Specifications

Specification Value
Block Spacing 120 seconds
Staking Minimum Age 8 hours
Reward 10 MDC
Max Supply 55 Million MDC

Channels

Specification Value
Bitcointalk https://bitcointalk.org/index.php?topic=4566622
Discord https://discord.gg/Ycbxah9
Website http://madcoin.life
Explorer http://block.madcoin.life:3001

License

Madcoin 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 Madcoin 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 with the devs and community.

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.txt) 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 Madcoin.

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.