Well,
Not that I support scam coins, and not stating an opinion about the coins is question, but the OP is wrong about a few things in terms of code and explorers.
For now, lets just start with the the line he claims hides the subsidy amount of a block , does nothing of the sort.
if (fDebug && GetBoolArg("-printcreation"))This line is saying: If the Debug flag is true and the parameter "printcreation" is true:
The Debug flag is turned on with a parameter when first starting the coin daemon/client. "printcreation" is a specific parameter to print out the block creation info in the debug log.
If both these conditions are not true, the next line that "hides" the subsidy does not execute and does nothing.
However, the debug print statement does nothing of the sort.
printf("GetProofOfWorkReward(): create =%s nSubsidy=%"PRId64"\n", FormatMoney(nSubsidy).c_str(), nSubsidy);The printf statement is simply that, print(in this case to the debug log).
"GetProofOfWorkReward(): create =%s nSubsidy=%"PRId64"\n"
Means the literal words: GetProofOfWorkReward(): create =
The %s means the first string argument declared after the quotes, in this case : FormatMoney(nSubsidy).c_str(),
The c.str() simply means to cast nSubisidy as a string instead of the numeric type that it is. This does not change the value or anything of the sort, only returns it as a different type.
%"PRId64" simply means to expect a 64 bit number, instead of a string.
What all this means is that Create= will show a nice formatted representation of subsidy and nSubsidy=%"PRId64 will show the raw number.
nSubisdy is declared in the above code and is not changed in these lines, so it will print to the debug log the correct number.
Now the Block explorers.
There is something wrong with the explorer or the setup of the explorer you are using.
If you do any research on me, you will discover that using and writing block explorers is one of the major projects I have done here for a few years.
I have used, modified and ran explorers based an ABE. Most recently I have written a completely new block explorer system from scratch and my block explorer service is based on the new system.
www.cryptocoinexplorer.comNow, I will admit that I do not have any experience with so called "Block Crawlers", which are not really block explorers in my opinion as they do not create and maintain a database separate from the coin daemon.
However, I highly doubt they are using the "Debug output" to get their information. If they are, that is not good at all.
If you want to prove the daemon is "lying" try this:
issue this command:
Assuming the block in question is block 1. Use whatever block you question.
then:
getblock {Block hash from step one}That is the information my explorer system uses and to a degree ABE will use (Though Abe will also use the blk.dat file to try and extract information)
Now, before you decide to go off on some crazy rant, I suggest you look a bit into who I am and my reputation around here, you might just find I know what I am talking about.
