[350 GH/s] "Eligius" (experimental) pool: almost feeless PPS, hoppers welcome

[Luke-Jr]

I would like to know how invalid blocks get handled.

If a block is invalid, it is completely ignored by future block generation, as if it never happened: shares contributed toward that block are "reinstated" toward the currently-in-progress block, and payouts are as if they never happened.

Also, I think that if all of us, who have external IP, connect our clients to his pool to receive newly found blocks we will a bit decrease the chance of invalid blocks - because solved blocks will spread faster in p2p network.

luke, is it enough to "-addnode pool.bitcoin.dashjr.org" upon our bitcoind start? or "-addnode 173.242.112.53" ?

You can try it, but longpolling should be just as effective, if not more. Do note that the public peer on my server is used for #bitcoin-watch, NOT the pool. For security reasons, the pool's node is not externally accessible at all, and only communicates with the #bitcoin-watch node.

[djex]

Could you please investigate this. Something seems odd with the payout system and as well as how it keeps track of earned rewards.

0000000000001058cc4b850fc2f1f906f3ad4a2a276cc326f1811fb4d1b74ec4: You earned 1.63719062 BTC, and were immediately paid 1.63617631 BTC.
000000000000186bfede5c3e9d599a1aec8a6fb37854f8d30aa1536e0c81557d: You earned 1.61041198 BTC, and were immediately (over)paid 1.61243335 BTC.
000000000000560b1ffd8af896cd5b0ed668f03aa9a7728a5fa2182c5ee76e2e: You earned 0.10549032 BTC, and were not paid due to balance being under 1 BTC.
0000000000001a2585f316f81b20623e693845515f216f3ecb787583f4b79874: You earned 0.88415731 BTC, and were not paid due to balance being under 1 BTC.
00000000000038e334a9c559b7f49cd76fb8f2d99537be7fc8d1cf69ed01bfdb: You earned 0.32138317 BTC, and were immediately paid 1.30396680 BTC.
0000000000004d8ce1babf4fdbf153f813ec4776ea53f7e36cd4897886349f0d: You earned 1.04322469 BTC, and were immediately paid 1.04706787 BTC.
0000000000000415d30f8bc59fc4ed45f2bd7661c2ef3f89aed2e2c9cd2023a8: You earned 0.32683516 BTC, and were not paid due to balance being under 1 BTC.
000000000000279a59e47b514a7064f0d177642f978cc5e5a425505a0dab06c5: You earned 0.59436705 BTC, and were not paid due to balance being under 1 BTC.
000000000000198ed4cb0586b718bc901865d1e94cb859cd1c4af043379d9aa8: You earned 0.77644269 BTC, and were immediately paid 1.68449708 BTC.
You have an outstanding balance of 0.01536158 which will be paid as soon as you either earn a total of over 1 BTC, or don't mine on the pool for a full week.

Thanks for your reply. My final payment came in this morning. Not sure why but it was delayed. Could of been something with the network.

Also the information you provided was quite helpful. Is there any way you could have your server put together a file for each address with content like you put above. It would make it easier to track earnings and possibly save some confusion in the future. Just an idea / suggestion. I might if I have some time today, put together a script to do it using the json you have provided already.

[Luke-Jr]

Also the information you provided was quite helpful. Is there any way you could have your server put together a file for each address with content like you put above. It would make it easier to track earnings and possibly save some confusion in the future. Just an idea / suggestion. I might if I have some time today, put together a script to do it using the json you have provided already.

I looked into doing this, but it would be fairly complex. Right now, replaying the entire history (to get the details I showed you above) takes almost 10 seconds already, and I would need to maintain an open file for every address throughout. That would be 10 seconds during which miners would be running out of data, idle. I keep it low by caching the balances, but that wouldn't work for the format above.

[quaaark]

I think the pool is having problems

[Luke-Jr]

I think the pool is having problems

Was trying to help debug a memory leak in pushpoold for jgarzik, but it shouldn't have been down for any significant amount of time. Most miners should automatically reconnect.

[quaaark]

I think the pool is having problems

Was trying to help debug a memory leak in pushpoold for jgarzik, but it shouldn't have been down for any significant amount of time. Most miners should automatically reconnect.

Cool

[Luke-Jr]

We're hitting some pretty major I/O bottlenecks with SQLite. I'm going to migrate the db to MySQL to mitigate the problems. During that time, the pool will be down. Hopefully it won't be too long, but the db is currently already 1 GB...

[TurdHurdur]

Is it time for NoSQL already?

[Luke-Jr]

Migration complete. Hit a few hiccups on the way, but I think I minimized total downtime to under 30 minutes. During that time, miners may have idled, or lost shares. Unfortunately, it seems we found a block during that time too. I expected that in such a case, the rewards would just be off slightly and it would make up the difference in the next block, but apparently it took the whole 50.03 BTC to itself. I'll figure out a way to get that fixed, probably with a sendmany once it's been confirmed (and I write the code to tell the pool I did it). In the meantime, Eligius should be stable again, and much faster with getworks. Until I get that 50 BTC made up, the pool payouts will likely be delayed by one block while it tries to make it up on its own. Will post more when I have an update.

[Luke-Jr]

These addresses and amounts will be deferred until the bugged block matures (100 confirmations):
1HcbN4NTAcUhcXVfgs2KooVhtK6nwUkaog  -764408220
16u6Z8N5zf3GpUwsTApUvMKGw6HZU7h1qd  -402464413
1KoBYhF3uNS5ZvGTd4RNjWc7VbMqQfDwzy  -367798848
1QDs3u4NawCmPBfMxWzZARbwjWwEQdTFTd  -278997383
14rJYeAPkXGDRVeTcEn7czE9xNaU5aRi64  -280856126
1DhV9Xf9wfXmngaW2WbjEti8WoRJzrHCC7  -279276194
1CiWEKiF5J5Xarxu1MMM7YMuZ51xBMs3Bw  -218262942
173Qmir9hTmvkb3Cmvgj78AV2CjL5azZYS  -107295962
1Dh225PqFhD8eDFzqPoT8j5uhPF2j815Cb  -190614135
19kQaXvKVWAF6oAsdsyuzWZqxLnttT3eAj  -102416760
12mcF29MTcJxpKhe4PiggpneTpFQqux1Ho  -104043161
1EFotQdsKSR1dbDRdH4iFbHmtVax1TjNBi  -159758994
19uXX5nHK9hYQqvEYUi1tBGieLqYB5aSN4  -117007896
13BNLook5Bf6gUXJjCGu5Hkds3BEj2q1nB  -109758797

I felt it would be unfair to delay the payouts of everyone whose balances only just finally added up to over 1 BTC, so there is still about 17 BTC that the pool will continue to fit in across transaction fees and other gaps in the coinbase as soon as it can.

Sorry for any inconvenience.

Also, until the 50 BTC is fully distributed, my own GPU miner will not be receiving any funds.

Edit: 1HcbN4NTAcUhcXVfgs2KooVhtK6nwUkaog has volunteered to wait for a manual send of some older delayed funds, so the pool self-recovery should go a bit faster.

[Riley]

My balance on 1KmTsdzjvrkZcMxtdoR9WdHwb8Bn5v6fpd decreases a couple of times a day. What's going on?

[Luke-Jr]

My balance on 1KmTsdzjvrkZcMxtdoR9WdHwb8Bn5v6fpd decreases a couple of times a day. What's going on?

The balance includes rewards for the current block. If you don't maintain your mining yields, or if another miner joins, before the block is found, that amount will decrease. If you get paid, that is not included in the balance anymore.

[RustyShackleford]

When an address is "paid" should we expect to see it show in blockexplorer or does it then go in a queue to be paid with the next or possibly subsequent block found by the pool?

[Luke-Jr]

When an address is "paid" should we expect to see it show in blockexplorer or does it then go in a queue to be paid with the next or possibly subsequent block found by the pool?

It should be part of the generation in blockexplorer.

[Luke-Jr]

The bugged block has been distributed here: http://blockexplorer.com/tx/f32022e1da8a8046a4c7e76a8ad6e8322aa14e15555b8dc6159936df5850a6a3

[luffy]

what is the current block finding rate for this pool? i see the pool hash rate between 10 and 20 Gh.

[Luke-Jr]

what is the current block finding rate for this pool? i see the pool hash rate between 10 and 20 Gh.

[09:50:49] <luke-jr> ;;bc,calc [bc,eligius]
[09:50:50] <gribble> The average time to generate a block at 16721739.3391 Khps, given current difficulty of 109670.13329248 , is 7 hours, 49 minutes, and 28 seconds

We had a nice peak of 31 GH before the debugging and MySQL switch. Spread the word so we can reach 100

[RustyShackleford]

When an address is "paid" should we expect to see it show in blockexplorer or does it then go in a queue to be paid with the next or possibly subsequent block found by the pool?

It should be part of the generation in blockexplorer.

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

Thanks

[Luke-Jr]

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

It has only earned 0.60927445 BTC total, so far. Payout is once it reaches a minimum 1 BTC.

Also, Ufasoft should work now. Fixed a bug in pushpool related to standard compliance. "The response MUST include a WWW-Authenticate header field (section 14.47) containing a challenge applicable to the requested resource."

[RustyShackleford]

Can you check on 1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3 for me then? Seems to have been paid more than once in a few blocks but not showing up in any blocks http://blockexplorer.com/address/1CWw7iNrhz7uHoTDTqAE2RZS9pwsD9Rfr3

It has only earned 0.60927445 BTC total, so far. Payout is once it reaches a minimum 1 BTC.

My bad, I read the line backwards The "paid" was for a different address