I figured that was per share of the eventually mined block. I guess there's room for both types but it seems odd for me for the pool organizer to be taking all the risk. I was on the Slush thread and I see their pot got emptied soon so it seems like this is not an uncommon problem.
Slush's pool doesn't do PPS so there's less risk. They pay out a proportion of that produced by the block based on the shares you've found (using a formula to reduce hopping). PPS pays out for every share submitted. So in periods of bad luck the pool pays out and hopes to catch up on the periods of good luck. Profit margins are so small on pools that 'paying out of profits' isn't much of an option during the bad periods. A 2% fee is only 0.5 btc per block. So to cover for one block's worth of bad luck, or one single orphan, will take 50 blocks for the pool operator to recover from in fees. |
|
|
|
This mandatory build alters the way the difficulty is computed during retargets . What exactly does the difficulty change do and why? They haven't given much time for people to update given that it's a forking change. It's likely to cause problems with pools and exchanges with users on old clients wondering why they're not getting any of their coins confirmed. |
|
|
|
Nice. CoiledCoin is the only one, of the coins that got a lot of attention, missing that I noticed. |
|
|
|
It should ideally be: Miner->Stratum server->Litecoind directly and bypass pushpool entirely But you could put the proxy between the miner and the stratum server if they're using a miner that only does getwork. You'll likely have to write code for the stratum server to update your pools backend database with share information,etc (I haven't looked at the python server code). If your Java is better that your Python you might find fireduck's SockThing easier to get going. |
|
|
|
I was thinking of more along the lines of having everyone allocated as a spam user, unless they contact me to request a "writer" status.
How about have the user have to send a token devcoin amount to an address. When that is received the account is activated. This is similar to how the bitcoin wiki works. |
|
|
|
May I ask you when I use stratum, long poll has no importance?
That is correct. When you use stratum the long poll system is not used. All notifications about new blocks are handle by the stratum protocol. |
|
|
|
May I ask you if the stratum pool support merged mining? Thanks!
Yes it does. The recent increase in difficulty on ixcoin and devcoin (and hashrates which can be seen on vircurex.com) is due to the activation of merge mining on my stratum server. |
|
|
|
I experienced an almost hour-long streak of rejects on all my rigs today:
...
This happened simultaneously with 6 rigs and 3 internet connections.
Unfortunately one of the back end bitcoind's crashed last night and was refusing connections. I'm investigating why this happened and how to work around it if it happens again. |
|
|
|
|
What's the best hash someone found on this payout method, do you know?
|
|
|
|
|
Pool is down due to a server issue. I expect it to be up in about 10 minutes.
EDIT: Pool is back up. I've reset the bitcoin server wallet. This means there are currently no funds in it until a couple of blocks have gone by when the transaction to top it up again goes through. I'll notify here when the funds are back in it.
EDIT2: Pool funds are transferred and withdrawals should be working.
|
|
|
|
|
Has anyone played with the OP_EVAL capability of CoiledCoin? This was the alternative to bitcoin's P2SH back when it was first discussed. CoiledCoin went and made every address use this which was supposed to result in some nice capabilities. I was curious if anyone would pick that up and run with it.
|
|
|
|
I suspect it pre-dates qt, as it uses multicoin, which was a system intended to let you design coins in the config file without having to hack the code. I think qt came along later.
The source I have has a 'qt' directory and it doesn't look like multicoin - it looks like it's based on the original bitcoin source. |
|
|
|
I get an exception on subcribe. So it does not work at all. BTW, your pool is the only one with this problem so far. Slush, BTCGuild, Ozcoin, BTCOxygen, MtRED, 50BTC... all do work with slush's stratum proxy.
I'll investigate, thanks for the report. |
|
|
|
Bitparking merge mining has resumed.
I've activated merge mining on the bitparking pool stratum servers now so you may notice an increase in hash rate and difficulty on Devcoin. |
|
|
|
|
Oops, found a bug. The bug affects total pool statistics, not user statistics. I've fixed the cause and am now in the process of correcting pool stats. Sorry for the restarts.
Edit: Pool stats fixed. And we found a stratum bitcoin block which is a good sign that I didn't break bitcoin block generation when adding merged mining to stratum.
|
|
|
|
|
Merge mining is enabled on stratum now so we should start seeing the hash rate of the alt coins increasing. I'll be monitoring closely the next couple of days to make sure I haven't broken anything, in particular the generation of bitcoin blocks!
|
|
|
|
|
Pool will have 5 minutes of downtime to install merge mining updates.
Edit: Upgrade done. Let's see if it sticks...
|
|
|
|
|
Show Posts
