It stopped as soon as I posted his. Now he's staking to his own address.

Here's an example: http://khashier.com/tx/6a875588f9753ffee10b6df872c6db62ab48e744026a0a0d84f0d09f55dbad98

Somebody is staking their coins directly into the Just-Dice staking wallet.

Here's an example: http://khashier.com/tx/2c54d03bc4d0eaaa097b19f447fe90e202950bc118252a96ddb6265a09f9dcb3

It splits the 1 CLAM reward into 2222 separate pieces and gives them to Just-Dice. I don't know if it's someone's idea of a denial of service attack or what's going on. It seems very unlikely to me that someone accidentally set "splitsize=0.00045" and "rewardto=xJDCLAMZ..." in their CLAM config file.

The address is staking pretty often. It has sent us 23 CLAMs worth of dust so far in less than 24 hours.


Should I repeat the question for you?

what is BTI and why do you keep posting about it on the CLAM thread?

Yes, but he asked for "safe" places. It's generally not considered a good idea to store your coins with a third party : "not your private keys = not your CLAMs" as Andreas often says (or something like that, anyway). I don't know of any reason not to trust the listed third parties, but it's safer to control your own private keys.

Yes. There's the CLAM client: https://github.com/nochowderforyou/clams/releases/tag/v1.4.17

That's sweet of you to say, but I would be in favor of you guys supporting CLAM. The more the merrier I say.

Edit: by the way, I have sworn off gambling after my last bad run at yolo-dice (https://i.imgur.com/guQkNU1.png), so I won't be participating in any of your future promotions. Thanks for them though - they were fun!

How about a third option: "neither; keep the contests coming" as well? That's what I'd pick.

If I had to choose between you opening the investment and keeping the contests running I would choose keeping the contests running.

If people want to invest in the bankroll they can convert their shitcoins to BTC and invest those.

Well said. I've given you 50 merits to help you continue the great work you're doing here.

Do you have a link to the terms & conditions for this promotion please?

I'd like to know for instance:

* Do I have to bet on the "Match Result" specifically, or does any bet on UEFA final qualify?
* Is the free bet's amount the same in BTC or USD? Suppose I bet $100 worth of BTC today, but the price of BTC halves before the world cup. Do I get a free bet for the amount of BTC I bet (which will only be worth $50 by then) or is my free bet for twice the amount of BTC I bet today (so the free bet is still worth $100).
* What are the limitations on claiming the free bet? One per account? Per person? Per household? Per IP address? Other?

Thanks, but it doesn't work for me. As soon as I try to run the CLAM client I get an error and it quits:


I used my own blk0001.dat, with this sha256sum:

510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  blk0001.dat

I guess it's the same as yours. Other than that I'm guessing we are using incompatible versions of leveldb.

Edit: how does the start of your debug.log look when it's failing? Do you see a different "transaction index version" number?

The bootstrap file is fine. I recently imported the whole thing. I suspect it's the "vtx.empty()" condition which is true.

It would be interesting to have a copy of the clam folder which reliably causes this error. I don't need the 2GB blk* file - I already have that. And I have the bootstrap.dat too. So just the other files.

Until recently the contests were explicitly designed such that they were incapable of bringing any profit to the site, since 100% or more of net player losses were given out as the prize pool.

Only the last two (including this one) contests have had the possibility of paying out less than 100% of net player losses.

It's close enough...

I just noticed that the sum of the sizes of my blk* files is *exacly* the size of the bootstrap.dat I imported:


-rw------- 1 user user 2097155946 May 18 20:10 blk0001.dat
-rw------- 1 user user  467920500 May 19 03:43 blk0002.dat
-rw-rw-r-- 1 user user 2565076446 May 18 00:08 bootstrap.dat.old


I still have "connect=0" in the clam.conf, so it hasn't had a chance to find any blocks newer than the ones in the bootstrap.

Edit: it turns out the two blk files put end to end are identical to the bootstrap file:


~/.clam$ head -c 2097155946 bootstrap* | sha256sum
510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  -
~/.clam$ sha256sum blk*1*
510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  blk0001.dat
~/.clam$ tail -c 467920500 bootstrap* | sha256sum
a2d30d536d57eab41d930e2f8d753e60d4af83c1d1fe5dad6c7f5c39475b3d42  -
~/.clam$ sha256sum blk*2*
a2d30d536d57eab41d930e2f8d753e60d4af83c1d1fe5dad6c7f5c39475b3d42  blk0002.dat

Yes, so long as it's syncing fast enough for you you don't need the bootstrap.dat file.

My client is still importing the bootstrap.dat I gave it about 24 hours ago. It's at block 1954760 at the moment, which these blk* file sizes:

-rw------- 1 user user 2097155946 May 18 20:10 blk0001.dat
-rw------- 1 user user  304629563 May 19 01:18 blk0002.dat

The sha256 for the first file:

510d0cabb4208d9a545a0e05fab2c0c29c225d699e0601a16b2891facbd2ce98  blk0001.dat

Will report back when the import crashes or finishes.

Edit: it finished:


That's all the blocks:


I don't know why some people are having trouble importing my bootstrap.dat file. Maybe it doesn't work on Windows? Did anyone try on a proper OS?

I don't use Windows and haven't for many years. I think the last version I used was XP.

We're talking about importing from a bootstrap.dat file. Bootstrap files don't contain orphans, and no network connections are made until the bootstrap.dat import finishes.

I see a problem when the bootstrap.dat reaches 4 GB, due to the use of an unsigned int, but don't see a 2 GB limit yet:

https://github.com/nochowderforyou/clams/blob/v1.4.17/src/main.cpp#L2870


Edit: I tried making a bootstrap.dat file which started with 4000 MB of zero bytes and then had the regular block data. The client quickly skipped the first 4000 MB and started complaining:

2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a35224a39798eca9ad889966aeb5a9da7b960ffb9869db35
2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 1 00000feca63cbde350712358668e0fe90e96c97efab3f0ff5fd9f3147dd2f53e
2018-05-18 12:16:03 ERROR: ProcessBlock() : already have block 2 0000042f7f9811948352d2ecc9215916f2276a5259ca4cdc4ccfb77a72ed8ebc

as expected. But then, after 96 MB of block data it wrapped around:

2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8571 000006ff5c3a5829e0da80d9afb609435e887c51123f5afeb5f6afe5da819423
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8572 0000022cc43c5975e8ec01d978179b1fa3b26e9fad73aa2306c85f82854fad35
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 8573 00000574ef1a20a79eb9c3525ed69af881e778f2100559d340fbc06ca1252240
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 0 00000c3ce6b3d823a35224a39798eca9ad889966aeb5a9da7b960ffb9869db35
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 1 00000feca63cbde350712358668e0fe90e96c97efab3f0ff5fd9f3147dd2f53e
2018-05-18 12:16:10 ERROR: ProcessBlock() : already have block 2 0000042f7f9811948352d2ecc9215916f2276a5259ca4cdc4ccfb77a72ed8ebc

So that's the 4 GB bug, but we won't be seeing that yet.

I tried putting 2100 MB of zero bytes before the bootstrap data and it seemed to be able to skip the >2 GB of junk just fine. So I don't know what the problem is yet.

My import that I started earlier is still running. I'll leave it running and see whether it eventually fails or not.

clam.conf is a file in the same folder as your wallet.dat. You make it yourself - it's a regular text file.

It could be an issue with 2GB filesize limit I guess, or a signed 32 bit variable in the code perhaps. 2^31 = 2147483648.

I would suggest putting "connect=0" in the clam.conf to stop the client ever going to "live sync".