[ANN] beeeeer.org - Primecoin mining pool!

[Gilligan]

With the new payout system coming online, do we have to move to the 0.6 version or are we ok on the older versions?

[xolokram]

you will have to move to v0.6 (or at least: you should move to v0.6)

currently there is no penalty or difference in performance to v0.5 (except for Grom's leaked experimental miner), but i will add a penalty later, because v0.6 has some features to reduce the workload on the server side, which is actually helpful for everyone, because this reduces the number of rejects. i don't really think that it is useful to have all these old versions (there are still single miners with v0.3) floating around.

- xolokram

[xhabit]

hm ... one day befor i'was move my miner to v.5.rc2 ... other question what is with the coins what was mine and was not pay out?

[xolokram]

hm ... one day befor i'was move my miner to v.5.rc2

i'm sorry about that, but i guess it's just bad luck for you. there's no perfect timing for such a huge update.
you'll have a few days to update your miners.

other question what is with the coins what was mine and was not pay out?

like i said before:
the blocks from the old payout system will be executed once they are confirmed by the primecoin network
just like they were paid before the cppsrb update (this will take ~2.5 days for all remaining/needed confirmations)

the new payout system will kick in once the confirmations are through from now on
expect the first payout for the new cppsrb system in ~2.6 days (+ some delay due to monitoring setup)

- xolokram

[masterOfDisaster]

Updated my miners (all Windows, some x86, some x64) to 0.6RC1 and can report that they are able to submit shares. And as expected there are only chains of length 7+ submitted. Good work!

[xhabit]

so, v.6. is up and running at the first miner ...

yes, bring the first share:

[MASTER] work received
Probable prime chain found for block=3d1adf447009cc8df7c762fa0b86b4ca190d89721833a3f33e5e7b628affeb43!!
  Target: 09.e6bdcb
  Chain: 1CC07.5115c8
[MASTER] submitted share -> SHARE

[Gilligan]

Confirmed. One of my systems has been upgraded and is successfully submitting 7's (hopefully 8's and 9's soon too!).  I will upgrade rest of systems tonight.

Thanks for all your work Xolokram.

Gilligan~

EDIT1:  Back to back 8's reported.

[xolokram]

ok, thanks for all the information you're adding here. i'm done with the first initial updates.

expect some more updates (especially on the web frontend) tomorrow / on monday.
i'm aware of the fact, that you can't see stats about your submitted shares by now; i'll add this asap.

let's hope everything will be ok. good night.

- xolokram

ps. i should replace the "shares / second" counter by something useful

[gog1]

can user stats also be divided into pre CPPSRB vs post CPPSRB.  having all those old 6 shares showing up in your stats make keeping track of the ratio of different length shares submitted difficult.

Thanks.

[hawas]

miner 0.6 up and running here, all well, a couple of 7 shares submitted.

Congrats for switching to the new payout system, been waiting for it

Edit
Holy, workers already down to 3000? Ok, it was temporary.

[super3]

Are 6-chains/old miners currently ignored or do we have to switch now? I have to recompile my Linux miners so it would be nice to make sure that bug are figured out on the few system so I only have to recompile once.

[gog1]

Are shares being counted properly or user stats updated properly?  I see some of my miners are showing time 0:56 while some are 20:56 (I a in Eastern Timezone).  I'm pretty sure I submitted some shares in the past 30 minutes base on the reports from the miner.  But I don't see the stats page updated, addr AcpjiZSC7fGigXGQzXYbfXDy3bTNRJHCGa

[Gilligan]

@gog1
I'm missing a bunch too.  Must be an update issue because Sy isn't showing any of the v0.6 finds.  I am logging my own to ensure they get credited.

Gilligan~

[xhabit]

smal question: why the blocks stay fix on 500? if i look ... SyStats der are mutch more. what is the diff?

{
 "address": "AdKXNNnue9jyHUJFmY1sF4vZn5V3cH1Mau",
 "payout_current": 0.0005714811783784708,
 "payout_pps": 0.0007441797970874334,
 "shares": 2331,
 "blocks": 500,
 "shares_per_block": 4.662,
 "details": {
  "6": 0.9159159159159159,
  "7": 0.07893607893607893,
  "8": 0.004719004719004719,
  "9": 0.000429000429000429
 }
}

{}

[xolokram]

6-chains are confirmed by the pool, but they will not have any value. please switch to v0.6 to get rid of the 6-chains after all asap. i was thinking about rejecting them, but that would've been way more confusing to people i guess, because what i've learned form the past: they're not properly reading what i'm writing here (ending in a lot of "why do i have so much rejects?" posts).

currently there are no known issues with v0.6, everything should be fine, you can compile & run the newest version.

as far as i know: Sy's stats is using the old payout system, thus his informations will end with block #206442 currently

the user stats on beeeeer.org are currently bound to your last 500 blocks (of the old payout system!!) you've submitted shares to (except for the payouts, which are still rolling in for the next ~2 days)

like i said before: the web frontend is not ready, wait for updates to see information about your current stats

- xolokram

/edit:
i added the stats about your latest submitted shares
they are bundled via time intervals of 20 seconds
see e.g. http://www.beeeeer.org/user/ANKZ8GNu2tpMV8u99dQwWdWky3xk4HrFYE