just set up the luckycoin pool at https://lky.epools.org
everything as usual: 1.5% pool fee, PPLNS & stability
drop in, help to spread the hash rate!
Topic: [ANN] LuckyCoin LKY | Lucky Blocks | Fast | Fun | Fair - page 8. (Read 112483 times)
New security update for the Luckycoin network:
https://bitcointalksearch.org/topic/annlky-luckycoin-security-update-236714
Titan
https://bitcointalksearch.org/topic/annlky-luckycoin-security-update-236714
Titan
Steadily above .00003 on cryptsy. If no one noticed. 
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Are you sure? Usually when you sync with block chain already there, it may be fine. Do a test from scratch, that is, erase everything in the config dir except the wallet file, then try to sync...and good luck
I tried three different machines with one downloading the block chain from scratch.
There were no problems. I can send coins between the old and the new client without problems.
The transactions confirm and are visible in the block chain.
In which situation do you think the client should break?
What did you change? The long string inside the ParseHex? If so, you need to change the same in main.h, and it is only when the genesis block executed you see the effect. Every time I change it, and start from scratch (clean everything in config dir), I need to re-adjust the genesis block (old one no longer works). If you use an existing chain and continue sync with it, it has no problem. But it uses the old params. Maybe I missed something there, maybe you changed different things, anyway just make sure from scratch it will work.
The public key is in main.h:1589 in the method CheckSignature() of the class CAlert.
https://github.com/LuckyCoinFoundation/Luckycoin
It is also in the genesis block construction in main.cpp. Both should be changed at the same time.
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Are you sure? Usually when you sync with block chain already there, it may be fine. Do a test from scratch, that is, erase everything in the config dir except the wallet file, then try to sync...and good luck
I tried three different machines with one downloading the block chain from scratch.
There were no problems. I can send coins between the old and the new client without problems.
The transactions confirm and are visible in the block chain.
In which situation do you think the client should break?
What did you change? The long string inside the ParseHex? If so, you need to change the same in main.h, and it is only when the genesis block executed you see the effect. Every time I change it, and start from scratch (clean everything in config dir), I need to re-adjust the genesis block (old one no longer works). If you use an existing chain and continue sync with it, it has no problem. But it uses the old params. Maybe I missed something there, maybe you changed different things, anyway just make sure from scratch it will work.
The public key is in main.h:1589 in the method CheckSignature() of the class CAlert.
https://github.com/LuckyCoinFoundation/Luckycoin
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Are you sure? Usually when you sync with block chain already there, it may be fine. Do a test from scratch, that is, erase everything in the config dir except the wallet file, then try to sync...and good luck
I tried three different machines with one downloading the block chain from scratch.
There were no problems. I can send coins between the old and the new client without problems.
The transactions confirm and are visible in the block chain.
In which situation do you think the client should break?
What did you change? The long string inside the ParseHex? If so, you need to change the same in main.h, and it is only when the genesis block executed you see the effect. Every time I change it, and start from scratch (clean everything in config dir), I need to re-adjust the genesis block (old one no longer works). If you use an existing chain and continue sync with it, it has no problem. But it uses the old params. Maybe I missed something there, maybe you changed different things, anyway just make sure from scratch it will work.
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Are you sure? Usually when you sync with block chain already there, it may be fine. Do a test from scratch, that is, erase everything in the config dir except the wallet file, then try to sync...and good luck
I tried three different machines with one downloading the block chain from scratch.
There were no problems. I can send coins between the old and the new client without problems.
The transactions confirm and are visible in the block chain.
In which situation do you think the client should break?
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Are you sure? Usually when you sync with block chain already there, it may be fine. Do a test from scratch, that is, erase everything in the config dir except the wallet file, then try to sync...and good luck
Is there a luckycoin info site online that includes current actual difficulty ?
Is my site wrong?
I don't see luckycoin on coinchoose.com.
Hmmm...I see it.
Sal, Luckycoin occasionally drops out of the list when the block explorer goes offline.
Is there a luckycoin info site online that includes current actual difficulty ?
Is my site wrong?
I don't see luckycoin on coinchoose.com.
Hmmm...I see it.
Titan, glad to see this being worked on. I've been a supporter from the start.
Great, thank you!
Titan
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
The pubic key for the alert system is for checking alert messages only as far as I can see.
I have the modified client working and it now ignores the litecoin messages.
The modified client is able to send and receive coins.
Titan
Is there a luckycoin info site online that includes current actual difficulty ?
Is my site wrong?
I don't see luckycoin on coinchoose.com.
I use http://lky.p2pool.nl/stats/ to find retarget time.
Is there a luckycoin info site online that includes current actual difficulty ?
Is my site wrong?
Approaching the 50,000 block mark!
Titan, glad to see this being worked on. I've been a supporter from the start.
What is it?
Network alert - All users must upgrade to Litecoin 0.6.9.1
Network alert - All users must upgrade to Litecoin 0.6.9.1
Its because the creator of the coin forgot to remove something from Litecoin coding it happened on FTC and they now removed it. It was something left over that should of been removed and it also needs to be removed from Lucky however theirs no sign of Lucky creator anywhere seems missing in action
Thanks for the hint. The Luckycoin client uses still the public key of the Litecoin network to check alert messages.
I will replace the public key in the next security update with a new one for the Luckycoin network
Titan
Replacing pubkey will change the genesis block, which will not work I think. It is easy to disable the message and I saw this is done by the alphacoin nicely.
Is there a luckycoin info site online that includes current actual difficulty ?
Im just glad hes stepped up to carry the torch
Thank you for the community support!
Those of you who are old enough will realize that the explosion of the new coin networks over the last month has something of the intensity of the early days of the internet in the nineties.
From that perspective I found it intriguing to support one of the networks in this embryonic state. So I decided to jump in and provide some technical and business expertise to this venture.
Titan
When will the updates be made to the client and when will difficulty changes be made to it to adjust quicker or to be more fair for people?
I have already generated the new keys for the alert system. I have to test this client with the network to see if this works without side effects.
The difficulty adjustment cannot be changed without a hard fork. The miners are just playing games with the hash rate to get more coins.
The fluctuations will level off with a higher average network hash rate. The Coinchoose crowd gives and takes about 100Mh/s.
I plan the next round of updates towards the weekend.
Titan
Jump to: