I know you want to advertise Darkcoin, but you need to keep it real. More hashing functions doesn't mean more secure. Quark is still the king of multiple hashing imo.
Darkcoin in terms of hashing functions it is a combination of Quark's 6 hashing functions and Qubit-coin's 5 hashing functions, so in total Darkcoin has 11. Five of Quark's hashing functions (Blake, Grøstl, JH, Keccak and Skein) were the finalists of the NIST competition
https://en.wikipedia.org/wiki/NIST_hash_function_competitionQuark is using 9 rounds of hashing: while using 6 rounds from Blake, Blue Midnight Wish, Grøstl, JH, Keccak and Skein it adds 3 more rounds of hashing
randomly: so the computer doesn't know whether it will be Keccak or Grøstl or Blake. And that's one of the uniqiue beauties of Quark. Unfortunately, Darkcoin or Qubitcoin don't do that: the computer remains certain about which hashing function will be used.
Another advantage of Quark might be, Darkcoin's block generation time is 2.5minutes (150seconds), while Quark is 30 seconds. Which means that Quarks algorithm with an element of randomness (unpredictability) will have to be cracked in 30 seconds to create a double-spend fork, while for Darkcoin this window of opportunity for the attacker is 5 timeslonger: 150 seconds with no element of randomness. If you take all these factors into account, Quark is still the most secure - it's not only about the number of hashing functions."
I would think it may be more difficult to design a ASIC with more hashing functions than fewer. While Quark has 9 rounds, there are only 6 functions. There are three random rounds (3, 6, 9). After the 2nd, 5th and 8th round, one bit is checked in the 512 bit hash as it has been calculated thus far. If that bit is on, then one particular hash function will be used. If it is off, then another hash is used. It is a basic
if else statement. It is a one of the types of statements common to all the Quark hash functions. Checking that bit is easier than programming an extra hash function. If the Quark or the X11 hash functions can be put into an ASIC, then handling the randomness will not be a problem. While the ASIC doesn't know what Quark hashes will be used for a particular block, it will figure it out along the way just as a desktop client or android wallet can do in C++ or Java.