[ANN] beeeeer.org - Primecoin mining pool!

[xolokram]

Hi,

this is the official announcement for our Primecoin mining pool www.beeeeer.org
As of writing this, ypool is not the only Primecoin pool any longer.

Some stats/features:

• 1% fee atm (this will possibly change to something between 1-3%)
• 3200 confirmations per block
• no registration needed, username is your primecoin-payout-address
• miner software based on mikaelh's client
• beta testing phase (something WILL go wrong, but we'll work on every little bug/problem ASAP)
• 'getwork' protocol with longpolling support
• you enter payout queue when you reach 3 XPMs (this will probably change)
• all shares (6-chains and above) are equally valued (this will probably change)
• high end visual stunning plain-text web interface

ToDo:

• [MINER] config file support
• [MINER] less verbose
• [MINER] reconnect bug
• [POOL] better web interface
• [POOL] stats ... lots of stats!!
• [POOL] different share values based on chain-length
• [POOL] proportional payout (e.g. 24h PPLNS, DGM, etc.) INFO
• [POOL] link to the miner (when everything is ready/stable)
• [M&P] 'gbt' protocol
• [M&P] 'xpt' protocol

Link:
www.beeeeer.org

Client / Miner:
bitbucket: source
github: source
windows binary: primeminer v0.1 *beta*
(contains 32 and 64 bit version)

usage:
primeminer -pooluser=[xpm-payout-address] -poolpassword=0 -poolip=beeeeer.org -poolport=9912 -genproclimit=[threads-to-use]

compilation:
linux: make -f makefile.unix primeminer
mingw: make -f makefile.unix primeminer.exe
(mac&solaris, pls edit makefile on your own, I dont have a suitable test environment)

jhPrimeminer should work too, BUT mumus version has a bug in the 'getwork'-protocol (refering v7.x, see attachment for source code fix)

jhPrimeminer tells you, that the shares were rejected by the pool. That's wrong. Just check your personal stats on the web interface and you will see the correct details for the current round/block.

FAQ:

Any known issues?
Unfortunately, when the pool restarts or the client's connection is not stable, there's a chance that the client will not re-connect properly (this seems to happen more often with the windows version, than with the linux version), we're working on the problem. When this happens, you will get a lot of share-rejects, because your miner is working on some old data. Restart your miner is the only known solution right now.

Why 'beeeeer.org'?
Everybody loves beer, that's why. (Ok, almost everybody)

Has the server crashed again?
If the status page isn't available: yup - something really bad happened. We're still in beta/testing phase, don't panic, everything will be ok.

- xolokram, glhf

ps. yes, i shamelessly copied parts of the ypool announcement
pps. props to mikaelh, sunnyking & fuzzybear for their work
ppps. did i miss something?

[xolokram]

[RESERVED]

[FuzzyBear]

Nice i'll have to give this a try tonight, I'll make the thread sticky for you

[Quirlorimbo]

I'm in!

[xolokram]

Wow, that was fast, thank you.

btw. the jhPrimeminer should work too (!!!!!!!!!)
but mumus version of jhPrimeminer has to be fixed first, there's a bug in his 'getwork' protocol code (I will add the .diff file later, for his code)

- xolokram

ps. quirlorimbo is my "partner-in-crime"
pps. added the windows binary & 'getwork' fix for mumus' jhPrimeminer (v7.1) to the first post

[xeroc]

thanks..

btw .. you cannot use -u and -p:
-------------------
terminate called after throwing an instance of 'std::runtime_error'
  what():  Add the parameter -pooluser=<user> and -poolpassword=<password>
-------------------

use -pooluser= and -poolpassword= instead.


Is there a chance you publish the sources for the server?

[xolokram]

yeah, you're right --- stupid copy&paste mistake --- I will correct that.

atm I don't plan to publish the source code for the server, sorry.

- xolokram

[xeroc]

Can you explain what i see on your website in /user/#id!?

[xolokram]

Can you explain what i see on your website in /user/#id!?

sure, the values you see there are your shares and the corrosponding count for the current round/block

"0" -> rejected - mostly due to a pool restart (when your client doesn't ask for new work soon enough)
"6", "7", "8", "9" -> shares (6-chain, 7-chain etc.)
"<block-height>" -> you've found the block (the round ends, the block gets saved for later payout info and is visible in the "blocks" info page)
"<negative value>" -> this could've been a share, but it's stale

stale & 'rejected' values should be <1%
as I stated in the first post, there's the chance, that the (windows) client doesnt reconnect to the pool properly, when the server gets restarted --- this typically leads to 'rejected' values

- xolokram

ps. there was a restart this morning due to a crash, I'm investigating --- all shares were restored

[theprofileth]

Um for those of us who don't regularly patch things with .diff files, how the hell do we fix the jhprimeminer with the .diff file?
Also nice to see a new pool try to challenge ypool's reign. Though I am kinda upset over the 3 xpm min, it should be 2 in my opinion.
But really I am really sad that I can't use any of these to mine due to the getwork issue, as they are vastly superior to the previous versions IE v7.1 and below

[xolokram]

Um for those of us who don't regularly patch things with .diff files, how the hell do we fix the jhprimeminer with the .diff file?
Also nice to see a new pool try to challenge ypool's reign. Though I am kinda upset over the 3 xpm min, it should be 2 in my opinion.
But really I am really sad that I can't use any of these to mine due to the getwork issue, as they are vastly superior to the previous versions IE v7.1 and below

Ask someone nicely who has a working compilation-environment for jhPrimeminer or do a patch/pull request? Or maybe configure your own environment? Or use the other client?

I'm mostly working in Linux, that's why I concentrate on the *nix/mingw software. jhPrimeminer support and the quick look into mumus' client source code was not my main focus, I just wanted to fix the 'getwork' protocol issue ASAP.


The xpm-payout-barrier is something we can discuss here
Since payouts will be automatically executed I think this barrier shouldnt be too low to keep the xpm-network-transaction-fee on an acceptable level.


Yeah, challenging ypool is quite tough. Does someone know what shares yPool is counting on their block stats page ?? (5,6,7,8,9... chains or 6,7,8,9... chains?)


- xolokram

ps. I made a pull request for mumus jhPrimeminer for the 'getwork' protocol issue, let's see what he thinks about it...

[theprofileth]

Sorry I did not mean to be rude, just I REALLY want to mine at your pool but if I can't use the latest jhprimeminer I am really just losing out on about half of my hashing power (yes the newer versions are that much better)
So in summary, I want to mine really bad at your pool even if it is less profitable, I just don't want to mine there if it can't do any good.

[xolokram]

no problem.

I just don't wanted to offer my compilation of jhPrimeminer here because I configured my Visual Studio environment (which is needed for jhPrimeminer) very dirty --- this means it's not really optimized (regarding: used libs / compile options / AVX suppot etc. pp.). I just wanted to check if the miner gets work from the pool and is doing something useful. I hope  "hg5fm" will offer a fixed version of the "mumus" miner ASAP, or maybe the creator of the "RdB" version (never heard of that before) will fix it (my pull request is already on github).

I may look into the configuration for jhPrimeminer and release a fixed version on my own, when I got time for this. Atm the pool & my miner are the first priority.

- xolokram

ps. pool restarted due to smaller code changes

[mhps]

Nice. Just had this on my screen

xxxx147693d1c235cca3b!!
  Target: 09.dbfc73
  Chain: TWN06.aa17xx
[WORKER] share submitted -> SHARE

So was it a 6-chain share? Does it mean I get the same payout for finding a 6-chain and a 9-chain?

[xolokram]

Nice. Just had this on my screen

xxxx147693d1c235cca3b!!
  Target: 09.dbfc73
  Chain: TWN06.aa17xx
[WORKER] share submitted -> SHARE

So was it a 6-chain share? Does it mean I get the same payout for finding a 6-chain and a 9-chain?

yup, you've found a 6-chain share

the console output tells you:
- the difficulty aka target length - needed to 'identify' a block (this value will change if a new block has been found on the network and your client is informed about that (every ~60 seconds))
- what you've found: Chain: TWN06.aa17xx
which decodes into <kind><length>.<fractional length>
where <kind> can be: 1CC, 2CC or TWN (describes what kind of primechain you've found)
length is most important as it will tell you if it's a 6,7,8 or 9-chain share (atm they have the same value regarding the payout, but maybe we will change that later for future blocks)

- xolokram