Topic: LottoShares - Dice 0% Edge - 80LTS Airdrop to all DOGE owners - page 4. (Read 62741 times)
October 08, 2014, 12:56:17 PM
What a tool this guy is... he will never be involved with another coin thats for sure.
October 08, 2014, 02:12:40 AM
Update:
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
Does that mean project is over?
October 08, 2014, 02:10:18 AM
Update:
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
Does that mean project is over?
October 07, 2014, 06:13:20 AM
Update:
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
I've been trying to resolve two problems with LottoShares but have not managed to do so.
The first is a forking problem when the checkpointing server is running. The checkpointing server allows draws to take place but causes forks to take place when checkpoints aren't accepted by some clients.
The second is decentralizing the draw/random number generation. Using the block hash and a private key to generate unpredictable randomness is centralized and ultimately unsatisfactory. I think the second problem may only be resolvable in the context of a (bitshares style) delegate model.
Unfortunately I've been unable to resolve these problems in LTS despite a huge amount of effort. I have now decided to redirect my efforts to other projects.
Thanks to everybody who took part and I'm sorry it didn't turn out as well as we had all hoped.
October 02, 2014, 05:32:46 AM
bter is back online with the current blockchain, your deposits should work as expected.
Yes, i can confirm Bter is back online and all my transactions were deposited today after a several days delay.
October 02, 2014, 02:06:43 AM
Quote
For the record, (I'm sure you know, but maybe it will help someone else) in general the best practice for .conf format is:
addnode=54.68.63.254
addnode=146.185.173.192
addnode=54.68.63.254
addnode=146.185.173.192
thanks for the catch
by the way, bter is back online with the current blockchain, your deposits should work as expected.
October 01, 2014, 09:22:26 PM
-reindex until you pass block 103626 for now.
mine worked after second try.
mine worked after second try.
try connecting to my node:
146.185.173.192
you can add this to your lottoshares.conf file
connect=146.185.173.192
Got it up and running again. When the re-index didn't work, I had to delete everything except wallet and conf then rebuild lottosharesd, but I forgot to copy the damn .txt files from release to src when I compiled the first several times (Ubuntu 14.04 server), and was getting the "merklerootGenesisBlock' failed" error, until I finally saw the notes, and remembered. Anyway, my node is also back up and running again, as well as my block crawler.
For the record, (I'm sure you know, but maybe it will help someone else) in general the best practice for .conf format is:
addnode=54.68.63.254
addnode=146.185.173.192
using connect=xx.xx.x.xx is described to "Connect only to the specified node(s)" as opposed to addnode which will "Add a node to connect to and attempt to keep the connection open.
October 01, 2014, 10:56:24 AM
coin mine a long time, first 80 and others will be 4-12month , now the price really down...
October 01, 2014, 10:25:38 AM
I had the best block issue also the fix is easy. save the wallet.dat file(C:\Users\(your user name)\AppData\Roaming\LottoShares), now delete files in BOTH the roaming\lottoshares AND its actual installation directory. download the latest version and re install. Once the wallet is re installed replace the new wallet.dat file in the above directory with your saved wallet.dat and boom, bamm, pow you have a snyced wallet and your shares back.
October 01, 2014, 05:47:31 AM
mine is working normaly, but I had this problem before
October 01, 2014, 04:31:25 AM
-reindex until you pass block 103626 for now.
mine worked after second try.
mine worked after second try.
try connecting to my node:
146.185.173.192
you can add this to your lottoshares.conf file
connect=146.185.173.192
October 01, 2014, 03:52:03 AM
-reindex until you pass block 103626 for now.
mine worked after second try.
mine worked after second try.
October 01, 2014, 02:57:54 AM
I've checked active nodes from my wallet's connection and saw there is a global problem:
lottosharesd getpeerinfo | grep startingheight
Most of them really stuck at either block 103626 or block 103634. This issue concerns both official block explorer and Bter exchange.
I try to open new wallet under Windows and could sync only upto 103626 block. After waiting about 3 hours I closed the wallet but when I try to start it again it crashes with error (found in debug log file) "Error: Failed to connect best block".
I suppose we need the dev. to act urgently since here is a second day of LTS global network issue.
lottosharesd getpeerinfo | grep startingheight
Code:
"startingheight" : 105698,
"startingheight" : 103634,
"startingheight" : 103626,
"startingheight" : 103634,
"startingheight" : 103626,
"startingheight" : 103634,
"startingheight" : 103634,
"startingheight" : 103634,
"startingheight" : 103064,
"startingheight" : 106054,
"startingheight" : 103626,
"startingheight" : 103634,
"startingheight" : 107236,
"startingheight" : 103634,
"startingheight" : 103634,
Most of them really stuck at either block 103626 or block 103634. This issue concerns both official block explorer and Bter exchange.
I try to open new wallet under Windows and could sync only upto 103626 block. After waiting about 3 hours I closed the wallet but when I try to start it again it crashes with error (found in debug log file) "Error: Failed to connect best block".
I suppose we need the dev. to act urgently since here is a second day of LTS global network issue.
October 01, 2014, 12:43:06 AM
it crashes at startup 
do you have the latest version wallet?? what error it shows? October 01, 2014, 12:00:15 AM
it crashes at startup
September 30, 2014, 02:50:13 PM
Last Active: September 08, 2014, 06:05:12 PM
why dev have long time no login?
why dev have long time no login?
he logged in today
September 30, 2014, 11:24:05 AM
Last Active: September 08, 2014, 06:05:12 PM
why dev have long time no login?
why dev have long time no login?
September 30, 2014, 11:15:44 AM
I am getting a "failed to connect best block error" and my wallet will not open. To solve the issue I deleted the files in the roaming folder and re installed. The wallet proceeded to d/l the blockchain but stopped about 10 hours shy of snycing. I shut the client down and tried to reopen it but the same error comes up. Is anyone else having this issue or have any fixes?
I've got the same error and was able to bypass it by relaunching lottoshares wallet with reindex option.
Add "-reindex" in command line or "reindex=1" in lottoshares.conf file.
I've got the same problem and same solution
see this page: https://en.bitcoin.it/wiki/Running_Bitcoin#Bitcoin.conf_Configuration_File
change "bitcoin" as "lottoshares".
Thanks again for trying to help but this appears to be a little beyond my current level of knowledge.
September 30, 2014, 11:13:58 AM
is this fail project,...
why do you think it's a fail project? cuz price isn't increasing??It cannot fail because it hasn't started yet. 95% of the coins haven't yet confirmed. In a years time we will have a better idea of the success or otherwise.
September 30, 2014, 11:11:23 AM
is this fail project,...
why do you think it's a fail project? cuz price isn't increasing?? Jump to: