No idea what you are referring to.. we didn't created the miners.

This is ur github right??
https://github.com/LightBitDev/LightBit/blob/master/src/crypto/yespower/yespower.c#include "yespower.h"
int yespower_hash(const char *input, char *output)
{
yespower_params_t params = {
.version = YESPOWER_1_0,
.N = 2048,
.r = 32,
.pers = "LITBpower: The number of LITB working or available for proof-of-work mining",
.perslen = 73
};
return yespower_tls(input, 80, ¶ms, (yespower_binary_t *) output);
}
This is CPUChain :
https://github.com/cpuchain/cpuchain/blob/master/src/crypto/yespower/yespower.c#include "yespower.h"
int yespower_hash(const char *input, char *output)
{
yespower_params_t params = {
.version = YESPOWER_1_0,
.N = 2048,
.r = 32,
.pers = "CPUpower: The number of CPU working or available for proof-of-work mining",
.perslen = 73
};
return yespower_tls(input, 80, ¶ms, (yespower_binary_t *) output);
}
Apparently replacing CPU with LITB results in an additional 1 charaction and hence ur Personalisation string is now 75 instead of 73 characters.
Im just explaining the post from the cpu-optiminer dev, if u use the actual 73 characters (aka, cutting the last 2 letters

), this coin is minable with the offical cpu-optiminer as well !!!
Aah now I get it. Thanks for the kind answer. Will definitely forward this information to our dev. But we are listed on 4 pools now and they already modified the miner to support it.
Thanks again for the information.
Thanks to the cpu-optiminer dev too.