LottoShares - Dice 0% Edge - 80LTS Airdrop to all DOGE owners

[FreeTrade]

Now can you make a profit long term at 0%?  I thought the house needed a slight edge?  Good luck!

We make a profit on the Lottery (15% house edge) and break even on Dice (0% house edge).

The Dice game attracts players, and some of them play the Lottery - so it is something of a loss-leader.

Also Dice players increase demand and liquidity for LTS.


Warning: Don't play dice yet - it only starts paying out after block 10500. About 16 hours time.

[testz]

Version 1.0.5 released for Windows and Mac OSX: https://github.com/LottoShares/lottoshares/releases
In version 1.0.5 we remove floating points from calculations, version 1.0.4 should also works, but to be at safe side, please use 1.0.5.

Warning: Don't play dice yet - it only starts paying out after block 10500. About 16 hours time.

[ycz]

I have a question regarding the LottoShares distributed for ShareCoin...

On 1.0.0, I can see I get 7080 LTS (many of them are immature for now). But when I installed 1.0.5, the 7080 LTS all disappeared...

Is the hard fork supposed to do so? Or something's wrong?

Thanks.

[testz]

I have a question regarding the LottoShares distributed for ShareCoin...

On 1.0.0, I can see I get 7080 LTS (many of them are immature for now). But when I installed 1.0.5, the 7080 LTS all disappeared...

Is the hard fork supposed to do so? Or something's wrong?

Thanks.

We also have hard fork at version 1.0.2. Try to resync, for this, using version 1.0.5:
- Close the client
- Delete all except wallet.dat from C:\Users\<UserName>\AppData\Roaming\LottoShares
- Start the client again

[ycz]

I got my balance back by...

1. Download 1.0.5 client and install
2. Have a totally fresh start (including a new, black wallet.dat)
3. Improve my private keys and ask to rescan

Now it seems working fine.

[FreeTrade]

Fork looks like it has gone according to plan!

Dice game is operational!

Have fun!

[FreeTrade]

Some screenshots  -


How to play




Check your winnings

[kokojie]

question: do I have to re-backup my wallet each day after playing some dice games? since I see the winnings all come in as different addresses?

[FreeTrade]

question: do I have to re-backup my wallet each day after playing some dice games? since I see the winnings all come in as different addresses?

That's a good point.

The wallet works in the same way as the Litecoin/Bitcoin wallet - a new wallet generates a bank of new addresses . . . 100 I think . . it uses those addresses for new change addresses.

So if you make a new wallet and backup, receive some funds, then play 101 games . . . the 101st game winnings (and subsequent games) wouldn't be in your backup.

You can obviate the potential problem by creating a larger keypool on startup . . . there's a command line option for it. Maybe start with a keypool of 10,000 and that should keep you going for a while

[thisisausername]

So I compiled this on Linux and I'm getting:

Code:

user@computer ~/lottoshares-1.0.5 $ qmake *.pro RELEASE=0 USE_UPNP=-
Project MESSAGE: Building without UPNP support
...
user@computer ~/lottoshares-1.0.5 $ make -j5
...
user@computer ~/lottoshares-1.0.5 $ ./lottoshares-qt 
lottoshares-qt: src/main.cpp:3120: bool InitBlockIndex(): Assertion `block.hashMerkleRoot == merklerootGenesisBlock' failed.

Has anyone else run into this / have any ideas for a fix?

[FreeTrade]

So I compiled this on Linux and I'm getting:

Code:

user@computer ~/lottoshares-1.0.5 $ qmake *.pro RELEASE=0 USE_UPNP=-
Project MESSAGE: Building without UPNP support
...
user@computer ~/lottoshares-1.0.5 $ make -j5
...
user@computer ~/lottoshares-1.0.5 $ ./lottoshares-qt 
lottoshares-qt: src/main.cpp:3120: bool InitBlockIndex(): Assertion `block.hashMerkleRoot == merklerootGenesisBlock' failed.

Has anyone else run into this / have any ideas for a fix?

Sounds like it's not finding the .txt files -

Here's the details on how to fix -
https://bitcointalk.org/index.php?topic=694341.msg7841608#msg7841608

[thisisausername]

Sounds like it's not finding the .txt files -

Here's the details on how to fix -
https://bitcointalk.org/index.php?topic=694341.msg7841608#msg7841608

Thanks for the quick reply.

Code:

user@computer ~/lottoshares-1.0.5 $ cp release/*.txt .

was actually what was needed (since I was trying to run the GUI, not the daemon.)

Seems like those text files should definitely be in both src and the root directory of the release so that building using normal building conventions works successfully.

[depboy]

I seem to be running into wallet issues with this coin.  Ive been mining it the last few days.  I've tried a couple of times to move some LTS to Bter, but they don't show up.  The TxIDs don't seem to show up on the blockexplorer either.

Are these issues fork related?

[FreeTrade]

I seem to be running into wallet issues with this coin.  Ive been mining it the last few days.  I've tried a couple of times to move some LTS to Bter, but they don't show up.  The TxIDs don't seem to show up on the blockexplorer either.

Are these issues fork related?

Yes, there was new code and a planned fork at 10468 - it sounds like you might not have updated yet - try grabbing the latest source or binaries and doing a reindex.

[depboy]

I seem to be running into wallet issues with this coin.  Ive been mining it the last few days.  I've tried a couple of times to move some LTS to Bter, but they don't show up.  The TxIDs don't seem to show up on the blockexplorer either.

Are these issues fork related?

Yes, there was new code and a planned fork at 10468 - it sounds like you might not have updated yet - try grabbing the latest source or binaries and doing a reindex.

I had updated.  I've been running v1.0.5.0.  Is that not the latest version?

Edit: And before you ask, yes, I did delete the old blockchain and re-sync the updated wallet.

[FreeTrade]

Here's the last few checkpoints -

14701,27b59965fa77fb6644f1d45ac3e89e6bc46da2e1207f7dae1a8e2272274e4e64,1408194712,b34146b217e4216a083a9dedbf678bcb0a543cb92b6943190f7a88602a9d436e
14702,370ff7a825dd6166e45cd07ff8c0551a137d0cd708b9b8deb98c7a0bb45d6899,1408194721,f0f29de37e514d53a4d4cfe1f20f38430aa22e80c2ce05c8783ce8fe1ca7b6bf
14704,0051fbc0f81e8487fe539531328a106bc1711614c487432a16787ad97f943fb1,1408194818,dfc5054991c7b5052ff1a64101cc85ae579dcbe1d1110d9acd99f540677a340f
14703,d7ff85257f3ef3248f616c0db5254fc9abd3b748b65e03c6d253d9647d59b7af,1408194760,6e20e0a665f50b319ab9ee0237699d132137a507c21d49183e64c1eeb39ccc72
14705,15f7151abb865392e7db0eec9b320f0d716941927c3ef16b98792c0ff4d0eca8,1408194924,eae40e032c30dc7e13ee1a0a0190d9ee7497c47fdaa17eab1b0f3d5e0abccbe5

Block explorer seems good.

You might be off on an orphan chain.

[depboy]

But I shouldn't have ended up on an orphan chain if I deleted everything but wallet.dat and re-installed the updated wallet, should I?

[FreeTrade]

But I shouldn't have ended up on an orphan chain if I deleted everything but wallet.dat and re-installed the updated wallet, should I?

No, you certainly shouldn't have. What block are you up to, how many connections do you have?

[depboy]

2 active connections, and I'm only up to block 14462

[FreeTrade]

2 active connections, and I'm only up to block 14462

Hmmm. . . and in your 'checkpoint.txt' file - what's are the latest checkpoint entries?