[ANN] ptsweb.beeeeer.org - Protoshares mining sub-pool

[pvaladares]

It would be helpful for new people working under linux to have the following instruction stated in first post:

Code: [Select]

sudo apt-get update
sudo apt-get install yasm -y git make g++ build-essential libminiupnpc-dev
sudo apt-get install -y libboost-all-dev libdb++-dev libgmp-dev libssl-dev dos2unix
git clone https://github.com/thbaumbach/ptsminer
cd ~/ptsminer/src
make -f makefile.unix
./ptsminer <your PTS address> <number of threads>

[xolokram]

sorry, for the rare posts, i'm currently focusing on upgrading the primecoin pool/webpage/stats etc.pp.
as i was focusing on pts too much the last couple of weeks (the todos were piling up )

@zzz111:
it's ok, you can do that.

@Gilligan:
per round

a round (to find a block) takes usually several thousands shares
this is your portion of this specific round

beeeer's pts pool is paying you proportional on a block/round (not like the XPM pool, where you're paid per share)

- xolokram

[zzz111]

I have 4 computers, may I use the same wallet to mine together(no workers for beeeeer pool )?
They use same ip(WLAN), won't conflict?
 

[Armchair Miner]

Thanks for posting this, I had the same problem and the restart of the PTS wallet has fixed it.

On the other hand, it raises the question with the PTS wallet itself. Why is it showing the green check mark "synchronized" when in fact it is not.

PS Later I'm thinking it might have something to do with the fact that I changed my wireless connection earlier yesterday. Other coin wallets were also showing they were synchronized when in fact they were not.

EDIT: FIXED!
Restart of the wallet fixed the problem, the payment was received immediatley, this may go to the FAQ too

Hello,

I reached the payout minimum of 0.2
29384 2013-12-07 06:33:13 155 / 388561 -> 0.00958 PTS / 24.02 PTS -> PAID

I sow this in the first post "your payout will be executed, when blocks are confirmed (delay of 120 blocks) and you reach 0.2 PTS"

I also get paid (in my account in beeeer) for
29706 2013-12-08 00:38:29 273 / 1453678 -> 0.00451 PTS / 24.02 PTS -> added

which shows that more than 300 blocks have already passed since the PAID one.
But the payment is still not received in my wallet.
THe address match perfectly , I checked like 12 times.

My user is PqP7P1mpytqAA7gPT7TGiMM4Amo3H7aKsu

[albatraoz]

Am I the only one having issues compiling PTSMiner on a Debian 6 system perhaps? It's a KVM virtual machine.

Error below =

make -f makefile.unix
g++ -Wl,-z,relro -Wl,-z,now  -o ptsminer  obj/cpuid.o obj/sha512_avx.o obj/sha512_sse4.o obj/sha512.o obj/sph_sha2.o obj/sph_sha2big.o obj/main_poolminer.o  -Wl,-Bdynamic -l boost_system -l boost_filesystem -l boost_program_options -l boost_thread -Wl,-Bdynamic -l z -l dl -l pthread
/usr/bin/ld: warning: libboost_system.so.1.54.0, needed by /usr/local/lib/libboost_filesystem.so, may conflict with libboost_system.so.1.42.0
obj/main_poolminer.o: In function `void boost::this_thread::sleep<boost::posix_time::seconds>(boost::posix_time::seconds const&)':
main_poolminer.cpp:(.text._ZN5boost11this_thread5sleepINS_10posix_time7secondsEEEvRKT_[void boost::this_thread::sleep<boost::posix_time::seconds>(boost::posix_time::seconds const&)]+0x2e0): undefined reference to `boost::this_thread::hiden::sleep_until(timespec const&)'
obj/main_poolminer.o: In function `CMasterThread::run()':
main_poolminer.cpp:(.text._ZN13CMasterThread3runEv[CMasterThread::run()]+0x15b): undefined reference to `boost::thread::start_thread_noexcept()'
collect2: ld returned 1 exit status
make: *** [ptsminer] Error 1


------


Everything necessary for the compile is installed afaik, as I've tried re-doing it aswell.

[bfgod]

EDIT: FIXED!
Restart of the wallet fixed the problem, the payment was received immediatley, this may go to the FAQ too

Hello,

I reached the payout minimum of 0.2
29384 2013-12-07 06:33:13 155 / 388561 -> 0.00958 PTS / 24.02 PTS -> PAID

I sow this in the first post "your payout will be executed, when blocks are confirmed (delay of 120 blocks) and you reach 0.2 PTS"

I also get paid (in my account in beeeer) for
29706 2013-12-08 00:38:29 273 / 1453678 -> 0.00451 PTS / 24.02 PTS -> added

which shows that more than 300 blocks have already passed since the PAID one.
But the payment is still not received in my wallet.
THe address match perfectly , I checked like 12 times.

My user is PqP7P1mpytqAA7gPT7TGiMM4Amo3H7aKsu

[btc2084]

@zvs: I guess my question is: Why do I get such noisy looking output?  For newbs like me, I just want stats coming out of the miner that are meaningful, numbers I can compare with others for performance tuning, and to let me know if there is something wrong with the system.  With so many constant "collisions" I have no idea if things are working. It doesn't inspire confidence. The word collision, speaking figuratively, just doesn't sound like a positive thing. So the only thing I know is "something might not be working well here because word "COLLISION" is repeatedly being thrown up on the screen, therefore, perhaps I should be mining something else.

I went back to XPM for a while but the beeeeer.org xpm miner hasn't been respond any more either.   It sucks but I am considering going back to ypool.

[...]

@BTC2084

Is this your question too?

Looks like 6417 shares to me.

[Gilligan]

So is this:

103 / 177692

The amount of shares submitter per?

[zvs]

29656 2013-12-07 21:55:48 103 / 177692 -> 0.01392 PTS / 24.02 PTS -> added
29650 2013-12-07 21:34:19 49 / 79565 -> 0.01479 PTS / 24.02 PTS -> PAID
29648 2013-12-07 21:25:26 953 / 1778041 -> 0.01287 PTS / 24.02 PTS -> added
29596 2013-12-07 18:12:58 57 / 79500 -> 0 PTS / 0 PTS -> ORPHAN
29591 2013-12-07 18:03:42 46 / 115562 -> 0.00956 PTS / 24.02 PTS -> added
29585 2013-12-07 17:48:27 486 / 813232 -> 0.01435 PTS / 24.02 PTS -> added
29564 2013-12-07 16:17:20 420 / 700573 -> 0.01440 PTS / 24.02 PTS -> added
29544 2013-12-07 15:03:58 60 / 90714 -> 0.01589 PTS / 24.02 PTS -> added
29538 2013-12-07 14:53:16 117 / 212476 -> 0.01323 PTS / 24.02 PTS -> added
29528 2013-12-07 14:28:59 223 / 367670 -> 0.01457 PTS / 24.02 PTS -> added
29520 2013-12-07 13:47:38 221 / 390817 -> 0.01358 PTS / 24.02 PTS -> added
29506 2013-12-07 13:01:07 294 / 530815 -> 0.01330 PTS / 24.02 PTS -> added
29484 2013-12-07 12:01:59 608 / 1028396 -> 0.01420 PTS / 24.02 PTS -> added
29447 2013-12-07 10:04:38 95 / 150580 -> 0.01515 PTS / 24.02 PTS -> added
29441 2013-12-07 09:47:13 53 / 106155 -> 0.01199 PTS / 24.02 PTS -> added
29434 2013-12-07 09:34:27 839 / 1510695 -> 0.01334 PTS / 24.02 PTS -> added
29384 2013-12-07 06:33:13 242 / 388561 -> 0.01496 PTS / 24.02 PTS -> added
29360 2013-12-07 05:44:26 213 / 356817 -> 0.01434 PTS / 24.03 PTS -> PAID
29348 2013-12-07 05:00:34 418 / 620529 -> 0.01618 PTS / 24.02 PTS -> added
29327 2013-12-07 03:44:11 109 / 185814 -> 0.01409 PTS / 24.02 PTS -> added
29317 2013-12-07 03:18:40 541 / 926693 -> 0.01402 PTS / 24.02 PTS -> added
29288 2013-12-07 01:29:43 373 / 643612 -> 0.01392 PTS / 24.03 PTS -> added

That is the part I don't get.

@BTC2084

Is this your question too?

Looks like 6417 shares to me.

[Gilligan]

@kfuzion

It looks like almost everyone has a ratio ~30 collisions per share. Could be a little more/less. It's not that you're not being paid for 97% of your collisions, you need X amount of collisions (on average) to get a share. Or maybe 30(ish) collisions = 1 share.No way around it, and it's nothing to do with inefficiency. If everyone got 1 collision = 1 share, PTS would've been entirely mined out 2 weeks ago. The whole way cryptography works is, there's a lot of guessing if you don't know how to break the encryption. 99.99999999% of the work done is guesswork, but there's no way around it.

This is what I was trying to say.  The ratio is about 30:1.  That is all I needed to know.  As long as that is how it is for everyone I am good with it.

Thanks for breaking it down for me.

Gilligan~

[kfuzion]

@BTC2084

I think the collisions are a good thing but I am confused on why I have so many collisions that result in shares submitted and only get paid on a few.  I am currently running 14 threads and am getting around 5000 collisions per day and only get paid on about 22 per day.

I think it works this way (although I have asked and nobody has responded):

 - Each collision results in either a SHARE or a REJECTED response.
 - Each SHARE represents your part of a Block or Chain (not sure of the correct terminology)
 - You do NOT get paid per SHARE.
 - You get paid on multiple SHARE submissions in the same Block or Chain.  If I submit 40 SHAREs in the same Block/Chain I might get paid .00156 but if I submit 250 SHAREs in the same Block/Chain I might get paid .0146 for the work that my miners did on that particular Block/Chain.

I am just guessing that this is how it works based on my experience.  It seems that as the difficulty has risen (and the value of PTS) the payouts have gotten few and far between.  But Xolo's pool is the best by far.  The dude is dedicated.

Feel free to correct me on any incorrect assumptions.

Gilligan~

Gilligan, I think you are confusing shares/minute and collisions/minute. You only get paid for the shares. Collision = COULD BE A SHARE, COULD BE NOTHING. If it prints a new line, it's a share or reject. If you do perhaps 100 collisions per minute, you might get 5 shares per minute. The miner keeps a running tally of the number of shares. Every time a new line is printed that says either Share or reject, it gets added to the tally.

1. Collision - nothing is printed UNLESS... (see 2)
2. If the collision is a share, it prints "collision is found"
3. Same print, next line: "share submitted"
4. If it's a share, prints "SHARE" on the next line
5. If it's a rejected share, prints 'REJECTED" on the next line.

Now, if you're running 14 cores, only having 22 shares a day is laughably low. Figure out what's wrong.

These are my stats, from running my laptop getting ~1 share/minute, plus 20 cores on Azure (doing 250 or so c/m, probably 10+ish shares/min).

29758 2013-12-08 03:31:27 1465 / 1615041 -> 0.02180 PTS / 24.03 PTS -> block waiting for confirmations
29706 2013-12-08 00:38:29 1324 / 1453678 -> 0.02188 PTS / 24.02 PTS -> block waiting for confirmations
29656 2013-12-07 21:55:48 148 / 177692 -> 0.02000 PTS / 24.02 PTS -> block waiting for confirmations
29650 2013-12-07 21:34:19 77 / 79565 -> 0.02324 PTS / 24.02 PTS -> block waiting for confirmations

So, over 6 hours, I have about 3000 shares - 500 an hour, 8.25 a minute, roughly.

What CPU, have you checked on your miner to see what it's printing out, etc? I have ~6% rejected on my dual-core laptop, servers are all around 1%, maybe less rejected.

Another thing you could have wrong - did you incorrectly type in your wallet address on any of your miners?

It looks like almost everyone has a ratio ~30 collisions per share. Could be a little more/less. It's not that you're not being paid for 97% of your collisions, you need X amount of collisions (on average) to get a share. Or maybe 30(ish) collisions = 1 share.No way around it, and it's nothing to do with inefficiency. If everyone got 1 collision = 1 share, PTS would've been entirely mined out 2 weeks ago. The whole way cryptography works is, there's a lot of guessing if you don't know how to break the encryption. 99.99999999% of the work done is guesswork, but there's no way around it.

[btc2084]

@xolokram, is it expected that nearly every stats post should include a "collision found"?

If it is "normal" perhaps the message could be shortened and the unique non-collisions should be shown -?

[WORKER] collision found: 1242542 <-> 40513559 #1000 @ 1386472274 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:24 | 153.1 c/m | 5.7 sh/m | VL: 552 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 30604881 <-> 19421341 #1018 @ 1386472288 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:32 | 152.7 c/m | 5.7 sh/m | VL: 553 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 65629335 <-> 30914487 #1032 @ 1386472289 by 1
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:37 | 152.9 c/m | 5.8 sh/m | VL: 554 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 50249271 <-> 53188474 #1054 @ 1386472304 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:45 | 153.1 c/m | 5.8 sh/m | VL: 555 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 32570834 <-> 33910633 #1074 @ 1386472335 by 7
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:54 | 152.7 c/m | 5.8 sh/m | VL: 556 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 38802225 <-> 61508252 #1088 @ 1386472328 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:10:57 | 153.6 c/m | 5.9 sh/m | VL: 557 (97.5%), RJ: 14 (2.5%), ST: 0 (0.0%)
[WORKER] collision found: 17402851 <-> 64986577 #1102 @ 1386472349 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:11:09 | 151.3 c/m | 5.9 sh/m | VL: 558 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 1892214 <-> 3952790 #1126 @ 1386472380 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:11:20 | 150.8 c/m | 5.9 sh/m | VL: 559 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 22628022 <-> 24608202 #1158 @ 1386472404 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:11:33 | 150.7 c/m | 5.9 sh/m | VL: 560 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 8619426 <-> 5349253 #1172 @ 1386472418 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:11:41 | 149.9 c/m | 5.9 sh/m | VL: 561 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 22290692 <-> 27419937 #1210 @ 1386472438 by 6
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:11:54 | 150.6 c/m | 5.9 sh/m | VL: 562 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[WORKER] collision found: 26180219 <-> 54544671 #1256 @ 1386472346 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:12:19 | 148.6 c/m | 5.7 sh/m | VL: 563 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 34070194 <-> 33872883 #1272 @ 1386472367 by 7
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:12:27 | 148.2 c/m | 5.7 sh/m | VL: 564 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 36833859 <-> 51622397 #1286 @ 1386472365 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:12:30 | 149.0 c/m | 5.8 sh/m | VL: 565 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[WORKER] collision found: 32326278 <-> 36101018 #1342 @ 1386472385 by 1
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:13:06 | 145.3 c/m | 5.5 sh/m | VL: 566 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 35712283 <-> 5097742 #1374 @ 1386472407 by 7
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:13:16 | 146.2 c/m | 5.5 sh/m | VL: 567 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 9198751 <-> 57142063 #1392 @ 1386472406 by 6
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:13:20 | 147.0 c/m | 5.6 sh/m | VL: 568 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 34419075 <-> 49111167 #1512 @ 1386472480 by 0
[WORKER] collision found: 50367191 <-> 32523970 #1514 @ 1386472484 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:14:01 | 149.2 c/m | 5.4 sh/m | VL: 569 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:14:01 | 149.2 c/m | 5.4 sh/m | VL: 570 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 5984402 <-> 58099286 #1520 @ 1386472480 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:14:03 | 149.3 c/m | 5.5 sh/m | VL: 571 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)
[WORKER] collision found: 64570807 <-> 12618303 #1524 @ 1386472480 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 21:14:04 | 149.4 c/m | 5.6 sh/m | VL: 572 (97.6%), RJ: 14 (2.4%), ST: 0 (0.0%)

[btc2084]

@Gilligan

Would be nice if we get credit for submitting even if we have collisions but still it seems like if it were possible to avoid them the pool would make more, right?  Thanks for sharing your perspective. I'm trying to understand it still.

I know I am being a bit paranoid when I suggest that so many collisions might be theft but it seems like they started suddenly and in the past not nearly as many occurred.

...

 - You get paid on multiple SHARE submissions in the same Block or Chain.  If I submit 40 SHAREs in the same Block/Chain I might get paid .00156 but if I submit 250 SHAREs in the same Block/Chain I might get paid .0146 for the work that my miners did on that particular Block/Chain.

I am just guessing that this is how it works ...

Gilligan~

[Gilligan]

@BTC2084

I think the collisions are a good thing but I am confused on why I have so many collisions that result in shares submitted and only get paid on a few.  I am currently running 14 threads and am getting around 5000 collisions per day and only get paid on about 22 per day.

I think it works this way (although I have asked and nobody has responded):

 - Each collision results in either a SHARE or a REJECTED response.

 - Each SHARE represents your part of a Block or Chain (not sure of the correct terminology)

 - You do NOT get paid per SHARE.

 - You get paid on multiple SHARE submissions in the same Block or Chain.  If I submit 40 SHAREs in the same Block/Chain I might get paid .00156 but if I submit 250 SHAREs in the same Block/Chain I might get paid .0146 for the work that my miners did on that particular Block/Chain.

I am just guessing that this is how it works based on my experience.  It seems that as the difficulty has risen (and the value of PTS) the payouts have gotten few and far between.  But Xolo's pool is the best by far.  The dude is dedicated.

Feel free to correct me on any incorrect assumptions.

Gilligan~

[btc2084]

@xolokram, thanks for the update. Here's the result on my Dell XPS 8700, Intel i7-4770 @ 3.40Ghz w/ 8GB RAM.

Note that I'm not sure the version number is correct for Hotfix#3.

I'm really clueless in the whole "Collision" thing but is it possible that someone is seeing the submission and somehow submitting to a different pool, "stealing" the submission and still somehow getting it in beforehand.  Does it seem right that so many are collisions?  If I am mining an not getting anything with PTS but collisions shouldn't I switch to another coin?

Thanks for the work Xolo. It does look like this fix corrected the REJECTION issues!


C:\Program Files\ptsminer_v0n_x64>ptsminer_avx_intel PtxgdYBcduwpkpcFb564NLKwmswJtcMQcP 8
********************************************
*** ptsminer - Pts Pool Miner v0.7 RC2 <experimental>
*** by xolokram/TB - www.beeeeer.org - glhf
***
*** press CTRL+C to exit
********************************************
using AVX
spawning 8 worker thread(s)
[WORKER[WORKER3] Hello, World!
[WORKER5] Hello, World!
[WORKER7] Hello, World!
[WORKER1] Hello, World!
0] Hello, World!
[WORKER2] Hello, World!
[WORKER3] GoGoGo!
[WORKER5] GoGoGo!
[WORKER6] Hello, World!
[WORKER0] GoGoGo!
[WORKER4] Hello, World!
[WORKER4] GoGoGo!
[WORKER2[WORKER1] GoGoGo!
] GoGoGo!
[WORKER6] GoGoGo!
[WORKER7] GoGoGo!
connecting to 54.201.26.128:1337
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[WORKER] collision found: 37138841 <-> 55733640 #50 @ 1386464732 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:27 | 130.4 c/m | 2.6 sh/m | VL: 1 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 23022064 <-> 29620132 #64 @ 1386464753 by 1
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:33 | 132.4 c/m | 4.1 sh/m | VL: 2 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 44043751 <-> 40433732 #74 @ 1386464752 by 0
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:35 | 143.2 c/m | 5.8 sh/m | VL: 3 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 46794233 <-> 45953484 #102 @ 1386464773 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:46 | 145.7 c/m | 5.7 sh/m | VL: 4 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 60679311 <-> 21827609 #112 @ 1386464769 by 1
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:48 | 152.7 c/m | 6.8 sh/m | VL: 5 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 11169502 <-> 44658328 #132 @ 1386464788 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:05:57 | 151.7 c/m | 6.8 sh/m | VL: 6 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 30973006 <-> 9895520 #150 @ 1386464811 by 3
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:06:04 | 150.0 c/m | 7.0 sh/m | VL: 7 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 36988808 <-> 11659484 #156 @ 1386464814 by 6
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:06:05 | 153.4 c/m | 7.9 sh/m | VL: 8 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 53385407 <-> 50311390 #254 @ 1386464868 by 4
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:06:40 | 158.8 c/m | 5.6 sh/m | VL: 9 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 65879588 <-> 63916448 #260 @ 1386464870 by 6
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:06:42 | 159.2 c/m | 6.1 sh/m | VL: 10 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 7558581 <-> 15603233 #294 @ 1386464901 by 5
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:06:55 | 158.9 c/m | 5.9 sh/m | VL: 11 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[WORKER] collision found: 22462866 <-> 34206375 #318 @ 1386464914 by 2
[MASTER] submitted share -> SHARE
[STATS] 2013-Dec-07 19:07:10 | 154.3 c/m | 5.7 sh/m | VL: 12 (100.0%), RJ: 0 (0.0%), ST: 0 (0.0%)
[MASTER] work received - sharetarget: 07ffffffffffffffffffffffffffffffffffffffffffffffffffffffbeefde4d
[WORKER] collision found: 41371619 <-> 8658999 #372 @ 1386464871 by 7

hi,
I'm sorry for the late reply. i'm compiling the windows binaries right now, i'll update this (and the first) post when they're uploaded to mediafire

here's the hotfix #3: *CLICK* (Windows 64Bit Binaries)
containing the 'rejections-on-a-block-workaround-by-reconnecting'-fix
...
- xolokram