Topic: [PROOF] Altcoin Scam - page 4. (Read 6967 times)

Thanks OP need more like you to keep this place honest, it was also in poor taste that the scam dev borrowed the name of an already existing coin that has a very decent and honest hard working dev. Hope people don't confuse this scammers work with that of the original coffeecoin now renamed coffeecoin V2 cfc2.

Since you know javascript, you might want to take a look at
http://bitcoinjs.org/

But honestly C++,  is pretty much a must for
an aspiring crypto dev.

It also takes a while to understand how the protocol
works. For that, here is a classic thread
https://bitcointalksearch.org/topic/satoshi-client-operation-node-discovery-41722

plus the documentation
https://bitcoin.org/en/developer-documentation

hope that helps.

Thank you for scan ARCoin source code

Thanks for the brief tip

Thanks for the brief tip

Great work. 

GOOD and nice explanation guy!
I use an generic information on my images! And yes, you're a good developer and 1,000 times better than me... Thanks for you post and explanation! On next scamcoins I'll quote your text! OK?
But here I have the proofs using the code that you said!
FIRST:


SECOND:


THIRD:



Thanks

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.


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.

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

Now, 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:



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. 

Congratulation on the find and your great explanation !

don´ t worry, Mr. Machado is now officially "scam sniffer" 

Yes, if the developer want to do he can do, but can find for developers that have access to source-code!

Well done OP! We can't be sure scam coins were mined, but it is certainly possible! and dev can also hide the coins from a block explorer. So, all alts can do this?

Guys, I've compiled this SHITCOIN to developer and my friend request a low level sniff on this code and I find this! So, It's scam and I'm asking for a fee to find new scams because the Developers can need a seal that is a good choice to invest!

Hot damn,  good job on sniffing out scam coins.  We need more of these kinds of service before people start throwing their money everywhere when it should go here to this guy.

Thanks for this, I wonder how many other coins are similar. Probably the same dev.

You got it.

Guys, I'm talking about CoffeeCoin [COF]!

@Lucksee

You need invest your time to learn and patience!

Obligatory request on behalf of all proto-coders:

Where can I begin to learn how to comprehend all the disciplinces of the cryptofields with only a basic 101 understanding of programming?

 (Personally, I've only coded with javascript...)?

Basically, if I want to dive deeper into the code of crypto... where do I begin "khan academy" style?
C++?

I'm relieved to hear that. I knew the original COF was useless, but the CFC2 wallet seems to work OK and I'm hoping they go up in price now the previous devs mess has been fixed.