>>>>>>>>>>>>>LightBit AIRDROP<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Doing a 30LITB giveaway in 2hours!!!! . If you are mining at http://hashpex.com/ at 8pm (GMT-4) - Washington DC time. (in 2hours time) You will share in the airdrop. Airdrop closes at 8.01pm so make sure you are mining. 30LITB Split between all workers. More airdrops to come soon!
Topic: 🗲[ANN] [POW] LightBit - CPU mineable coin [No Premine] [Fair Launch]🗲 - page 10. (Read 7168 times)
August 18, 2019, 05:15:09 PM
August 18, 2019, 06:12:51 AM
Hi all, a new pool for LightBit has joined the market!
It can be found at http://pool.customspeed.nl !
The pool is setup with YIIMP, the connection in located in Europe, the is set to 1.0% and the payout of confirmed blocks are done every 2 hours.
This pool has already ran as the pool for LAPO (LAX, lyra2zz) for 8 months and has supported it with ease.
The CPU mining clients/workers that are available on the several Githubs can also be used with this pool.
Happy mining!
It can be found at http://pool.customspeed.nl !
The pool is setup with YIIMP, the connection in located in Europe, the is set to 1.0% and the payout of confirmed blocks are done every 2 hours.
This pool has already ran as the pool for LAPO (LAX, lyra2zz) for 8 months and has supported it with ease.
The CPU mining clients/workers that are available on the several Githubs can also be used with this pool.
Happy mining!
Hello! Thanks for supporting LightBit. Will add your pool in the ANN right away!
August 18, 2019, 06:05:29 AM
Hi all, a new pool for LightBit has joined the market!
It can be found at http://pool.customspeed.nl !
The pool is setup with YIIMP, the connection in located in Europe, the is set to 1.0% and the payout of confirmed blocks are done every 2 hours.
This pool has already ran as the pool for LAPO (LAX, lyra2zz) for 8 months and has supported it with ease.
The CPU mining clients/workers that are available on the several Githubs can also be used with this pool.
Happy mining!
It can be found at http://pool.customspeed.nl !
The pool is setup with YIIMP, the connection in located in Europe, the is set to 1.0% and the payout of confirmed blocks are done every 2 hours.
This pool has already ran as the pool for LAPO (LAX, lyra2zz) for 8 months and has supported it with ease.
The CPU mining clients/workers that are available on the several Githubs can also be used with this pool.
Happy mining!
August 17, 2019, 03:36:23 AM
AIRDROP HAS NOW INCREASED TO 30LITB (Split between all workers) Readup for more information.
August 17, 2019, 02:59:31 AM
>>>>>>>>>>>>>LightBit AIRDROP<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< HAPPENING IN 2 HOURS!
Doing a 20LITB giveaway in 2hours!!!! . If you are mining at hashpex.com at 6am (GMT-4) - Washington DC time. (in 2hours time) You will share in the airdrop. Airdrop closes at 6.01am
20LITB Split between all workers. More airdrops to come! Come mine with us at http://www.hashpex.com
Doing a 20LITB giveaway in 2hours!!!! . If you are mining at hashpex.com at 6am (GMT-4) - Washington DC time. (in 2hours time) You will share in the airdrop. Airdrop closes at 6.01am
20LITB Split between all workers. More airdrops to come! Come mine with us at http://www.hashpex.com
August 17, 2019, 12:36:22 AM
But we are listed on 4 pools now and they already modified the miner to support it.
4 Pools?
Edit:
i have found it, but why you add this not @ the description?
Its better for all Miner
)https://pool.rplant.xyz/
http://cpu-pool.com/
http://nomp.hashpool.eu/
http://hashpex.com/
Wonderful thank you for the information!!!!
Apologies for not being clear. I mean four different mining pools.
Links -
1 http://nomp.hashpool.eu/
2 https://pool.rplant.xyz/
3 http://cpu-pool.com/
4 http://hashpex.com/
Yeah we will add them on the ANN too. Thanks for your interest and suggestion. Much appreciated!
August 15, 2019, 10:43:07 PM
🗲 Exchange Listing 🗲
🗲 We are happy to announce that we are listed on Ex4ange Exchange!
https://ex4ange.org/?LIGHTBIT-DOGE
Note - Trade at your own risk!
- Translation to english is in progress.
- Do not mine directly to the exchange address.
Thanks for your interest!
🗲 We are happy to announce that we are listed on Ex4ange Exchange!
https://ex4ange.org/?LIGHTBIT-DOGE
Note - Trade at your own risk!
- Translation to english is in progress.
- Do not mine directly to the exchange address.
Thanks for your interest!
August 15, 2019, 07:07:27 PM
Do not forget my stock exchange =)
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
Excellent!
It'll be good once you've got a working english translation for the exchange!
August 15, 2019, 06:15:04 AM
🗲 Exchange Listing 🗲
🗲 We are happy to announce that we are listed on CryptoHub Exchange!
https://cryptohubexchange.com/market/LITB/
Note - Trade at your own risk!
- Do not mine directly to the exchange address.
Thanks for your interest!
🗲 We are happy to announce that we are listed on CryptoHub Exchange!
https://cryptohubexchange.com/market/LITB/
Note - Trade at your own risk!
- Do not mine directly to the exchange address.
Thanks for your interest!
August 14, 2019, 09:44:55 PM
No need for a new miner, the official cpu-optiminer works fine
cpuminer.exe -a yespower -N 2048 -R 32 -K "LITBpower: The number of LITB working or available for proof-of-work mini" -o stratum+tcp://XXX -u YYY
Note how the personalisation string cuts off with just 73 chars instead of the full string.
cpuminer.exe -a yespower -N 2048 -R 32 -K "LITBpower: The number of LITB working or available for proof-of-work mini" -o stratum+tcp://XXX -u YYY
Note how the personalisation string cuts off with just 73 chars instead of the full string.
Yep. Got it. Thanks again for the information and support. Much appreciated.
The wallet accepts hash generated using the truncated pers string so it's not a miner issue.
That pers string is now part of the POW specification for the coin. Changing it now is changing
the specification.
Having a seperate parameter for the pers length is bad design. It is not necessary, strlen works fine,
and just creates opportunities for errors, as happened here.
August 14, 2019, 09:43:07 AM
Do not forget my stock exchange =)
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
Sure thing, I will not.
Please contact me on Discord.
Thanks!
August 14, 2019, 09:38:04 AM
Do not forget my stock exchange =)
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
https://ex4ange.org/index.php?LIGHTBIT-DOGE
Language translation in progress
August 14, 2019, 05:55:35 AM
But we are listed on 4 pools now and they already modified the miner to support it.
4 Pools?
Edit:
i have found it, but why you add this not @ the description?
Its better for all Miner
)https://pool.rplant.xyz/
http://cpu-pool.com/
http://nomp.hashpool.eu/
http://hashpex.com/
Apologies for not being clear. I mean four different mining pools.
Links -
1 http://nomp.hashpool.eu/
2 https://pool.rplant.xyz/
3 http://cpu-pool.com/
4 http://hashpex.com/
Yeah we will add them on the ANN too. Thanks for your interest and suggestion. Much appreciated!
August 14, 2019, 04:12:14 AM
But we are listed on 4 pools now and they already modified the miner to support it.
4 Pools?
Edit:
i have found it, but why you add this not @ the description?
Its better for all Miner
)https://pool.rplant.xyz/
http://cpu-pool.com/
http://nomp.hashpool.eu/
http://hashpex.com/
August 14, 2019, 03:42:44 AM
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
Code:
#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
Code:
#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.
No need for a new miner, the official cpu-optiminer works fine
cpuminer.exe -a yespower -N 2048 -R 32 -K "LITBpower: The number of LITB working or available for proof-of-work mini" -o stratum+tcp://XXX -u YYY
Note how the personalisation string cuts off with just 73 chars instead of the full string.
Yep. Got it. Thanks again for the information and support. Much appreciated.
August 14, 2019, 02:04:09 AM
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
Code:
#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
Code:
#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.
No need for a new miner, the official cpu-optiminer works fine
cpuminer.exe -a yespower -N 2048 -R 32 -K "LITBpower: The number of LITB working or available for proof-of-work mini" -o stratum+tcp://XXX -u YYY
Note how the personalisation string cuts off with just 73 chars instead of the full string.
August 14, 2019, 01:16:57 AM
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
Code:
#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
Code:
#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.
August 14, 2019, 12:51:49 AM
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
Code:
#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
Code:
#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 !!! August 14, 2019, 12:38:02 AM
No idea what you are referring to.. we didn't created the miners.
August 13, 2019, 11:58:48 PM
Jump to: