“Monsters are real, and ghosts are real too. They live inside us, and sometimes, they win.” — Stephen King
So, what is “Ghostrider”?
Well, there are both long and short answers to that question.So let’s look at both of them.
The short one is fairly straightforward, if you are familiar with crypto and how coins are mined etc; “It’s a collection of algorithms, the x16r and CryptoNight families, cycled in random and not so random patterns used to gain consensus on the on chain generation and transaction of coins.”
The slightly longer, somewhat more comprehensible answer is that it is a marriage of the RVN hashing algorithm “x16r” and the Monero/Bytecoin family of algorithms “CryptoNight”. Applying CryptoNight hash to a bitcoin based codebase has not been done before to the best of my knowledge and as such may end up spurring additional waves of development or glorious amalgamation..
There are 16 members in the x16r family and 8/9 members (not counting the “light/heavy” variants) in the CryptoNight family bringing the total up to 24/5 cycling algorithms. The x16r family of algorithms are more or less all fairly computationally intensive (core clock for gpu miners) as the math is fairly simple but intense. What the CryptoNight contributes is memory intensiveness (mem clock for gpu miners or cache for cpu miners) which you can think of as the “in between” calculations on the way to a result.
Combining memory and core intensive algorithms at this level of scale will clearly favor CPU/GPU miners over FPGAs and ASICS with both scaling better (may not be 100% technically accurate but for the sake of an explanation to the average crypto user this works) across the range of task types.
But ASICS are the big bad Boogy Man, no?
Yes, but they are also very expensive to design and implement and at them moment, given publically available data on ASIC scaling and design, the more hashing implementations that need to be included in each chip raise the cost in a fairly exponential fashion.
Our team are fully committed to going fork happy adding additional algorithms or implementations to the mix at the first sign of ASICS on the chain. Rendering them immediately obsolete.
So you’re not ASIC immune?
Nope, no one is. However, we’re ready to remove any ASICS found on the chain by forking in traditional and nontraditional ways.
FPGAS are AWESOME and can rape any coin!
Sort of yes and sort of no. I do not think you will find many FPGAs on CryptonightV8 as it implements several features that slow down FPGA processing. Those same features can be rolled out across most of the rest of the amalgamation of algorithms to produce similar effects. This limits FPGAs by making them unprofitable vs significantly lower cost GPUs.
Furthermore, a limiting feature of FPGAS is their at the moment relatively dinky capacity for storing hashing implementations on the boards themselves while running. Currently several boards need to be daisy chained to implement x16r on its own, adding the additional 8/9 members of the CryptoNight family to that mix would severely increase the number of boards required to implement the algorithm. This will limit FPGA interest as the cost point for entry will become very high.
Again, as with ASICS, the team are fully committed to rendering FPGA attacks on the chain obsolete through forking, new custom implementations along with whatever else may end up becoming necessary.