I wrote the script which compare code in one coin with code in other already inspected coins.
You might wish to consider extending the range of inspected coins that you bring to bear.
The rather tragic heritage of this coin is explicitly laid out in, of all places,
https://github.com/darkether/darkether/blob/master/COPYING (you couldn't make it up). ...
Copyright (c) 2014 bitpop
Copyright (c) 2014 hackcoin Developers
Copyright (c) 2013-2014 NovaCoin Developers
Copyright (c) 2011-2012 PPCoin Developers
Copyright (c) 2009-2014 Bitcoin Developers
bitpopcoin was abandoned by
bitpop and he welcomed re-use of the bitpopcoin source:
https://bitcointalk.org/index.php?topic=665896.0 but I doubt his vision stretched this far.
The heritage is “tragic” (or tragi-comic depending on the degree of your Bitcoin monotheism) because hackcoin was a
opportunistic hybrid launched over a year ago that combines elements of blackcoin, darkcoin and novacoin. It was promptly filched by infamous serial crapcoin dev Carsen Keck to
form the codebase for Dreamcoin and from there diffused into a bunch of other alts (apparently including shrms, arch and nebuchadnezzar, hence their appearance in xadsa418’s analysis).
In this particular instance, the reconfiguration fron bitpopcoin is minimal, so much so that after “harmonising” irrelevant differences (e.g. nullifying pure branding differences, project build and repos admin config differences) a straightforward diff reveals the full extent of the changes to the (June 2014) codebase:
http://pastebin.com/FFTS2FFBThe hackcoin codebase which was cloned for bitpopcoin was already obsolete when hackcoin
itself was launched; by that time Dogecoin had already
migrated to Bitcoin Core 0.9.
I have yet to hallucinate any positive rationale for launching a new altcoin using such an elderly codebase and features. I can’t imagine that it’s the kind of heritage that is likely to provide much support for an inspiring development roadmap.
Cheers
Graham