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

[Luke-Jr]

BTW, whoever is username "135dgT3qkdzac3DWMQfwwSeq2cH" needs to fix their miner to send the full address or it can't pay you...

[RustyShackleford]

Hey Luke, what do the "negative" balances indicate on http://luke.dashjr.org/programs/bitcoin/pool/balances.json?

[Luke-Jr]

Hey Luke, what do the "negative" balances indicate on http://luke.dashjr.org/programs/bitcoin/pool/balances.json?

The pool overpaid. Usually due to shares not factored into the final generation reward (meaning the pool underpaid someone else). I just put a 1 BTC buffer into the script, so 1 BTC (spread equally across all miners) will be delayed until the next block. Hopefully that will mitigate the vulnerability.

[dishwara]

You don't seem to understand how my pool pays out. There are no payout sends, you get original coins direct from the coinbase.

You saying MINT coins, instead of coins from other pools which at least get one transaction.

[TurdHurdur]

I don't think it needs any stats other than perhaps how much you've paid yourself. Though, is it always the top address in the To column of the block? Beyond that, I hope you gave some consideration to my suggestion.

[dishwara]

I think, its a small not bug but feature used wrongly.
The following pics below shows all addresses with an 9 digit number. I think that 9 digit represents the amount of bitcoin they mined.
1+8 decimal points. Luke some where mentioned (not sure) that a miner gets his coins only if its more than 1btc.
I think the same goes here. Until a miner mines more than 1 bitcoin, his address is not shown in the current block.
I am now running my miner for more than an hour, still my address not shown.
I believe when my miner reaches 1 bitcoin in current share , my address will be shown with a 9 digit number.(100000000- its the minimum 9 digit number & all the numbers in the screen shot is more than this number)

[djex]

Took me ~3 min for my address to show up. Not sure why yours isn't.

[geebus]

Could someone having trouble with ufasoft come on #bitcoin-dev so we can troubleshoot it?

Your problem with Ufasoft is that it does not send an authentication header on the first request.

You have to respond to it with a 401 WWW-Authenticate string, and then once it replies with the auth, return a getwork.

[Luke-Jr]

Your problem with Ufasoft is that it does not send an authentication header on the first request.

You have to respond to it with a 401 WWW-Authenticate string, and then once it replies with the auth, return a getwork.

If I omit the authentication in a request manually, I get a 401 just fine...

[Luke-Jr]

I don't think it needs any stats other than perhaps how much you've paid yourself.

I consider my own pool output to be just as private as anyone else mining on it. I only posted my earnings above to promote the pool, and confirm that it isn't just me receiving above-expected earnings.

As far as fees, the address receiving the 0.00000001 BTC per second is 1LGiiiQF6EW8Eoop5KyGmkSDGnYZRd94EE. With the new 1 BTC minimum, it will probably not show up very often.

The first address in a transaction is the "leftovers", generally due to the non-payouts of earnings under 1 BTC. It will obviously be filled by the payouts later on when those members reach their 1 BTC minimum. These funds remain in Eligius's client. If there ever becomes a problem with it consistently delaying payouts, I can manually do a sendmany with them to "catch up" (although I don't have anything written to offset such a send in the payout code yet).

[Luke-Jr]

Just an advance notice: the current block is overbilled; a total of 52.8665594 BTC is due to be paid out, but most likely the reward won't be that much.
As a result, the address 15syQPo3NadEtD4UVv34ixjkZvztCHCcX1 has been chosen (more or less randomly) to be paid only ~1.56 BTC out of his due ~4.43 BTC. The remainder will be paid at the next block. Since this is random, it's quite possible some factor may end up in another address being the one delayed. So if you happen to receive unexpectedly less and your balance has over 1 BTC remaining, this is why.

[Luke-Jr]

Here's some more useless data: http://luke.dashjr.org/programs/bitcoin/pool/blocks/?C=M;O=A

[thedrs]

• Transactions are included in blocks based on my policies: non-standard transactions accepted, but a flat transaction fee required of 0.00004096 BTC per 512 bytes

Luke-jr,
Can you please explain this to a newbie ? What does it mean and why do you need it ...
Do I need to change some setting on my rpcminer-cpu client ?

[Luke-Jr]

• Transactions are included in blocks based on my policies: non-standard transactions accepted, but a flat transaction fee required of 0.00004096 BTC per 512 bytes

Can you please explain this to a newbie ? What does it mean and why do you need it ...
Do I need to change some setting on my rpcminer-cpu client ?

This is no effect on mining. Basically, it means the pool won't participate/confirm transactions without a (tiny) fee, so it is immune to transaction spam.[/list]

[LightRider]

Just an advance notice: the current block is overbilled; a total of 52.8665594 BTC is due to be paid out, but most likely the reward won't be that much.
As a result, the address 15syQPo3NadEtD4UVv34ixjkZvztCHCcX1 has been chosen (more or less randomly) to be paid only ~1.56 BTC out of his due ~4.43 BTC. The remainder will be paid at the next block. Since this is random, it's quite possible some factor may end up in another address being the one delayed. So if you happen to receive unexpectedly less and your balance has over 1 BTC remaining, this is why.

That's weird.

[Luke-Jr]

It ended up being 1QDs3u4NawCmPBfMxWzZARbwjWwEQdTFTd who was shorted 1.68134587 BTC. Unfortunately, there is a flaw in my payout code which has chosen this same poor fellow to be shorted again this block, if it doesn't cover everything. I need to rethink the payout weighing code. Hopefully before this block is found, but in any case he will be paid in full eventually.

[djex]

Why doesn't my current balance add up to my balances on generated blocks I participated in?

The last two blocks I had 92341597 and 32904892 which equals 125246489 -> 1.25 BTC but my current balance shows 25092928.

My address is: 1DiDC5jb96GR2d5LVsWuSdSB3q5zbns2Bo

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

[dishwara]

Why doesn't my current balance add up to my balances on generated blocks I participated in?

The last two blocks I had 92341597 and 32904892 which equals 125246489 -> 1.25 BTC but my current balance shows 25092928.

My address is: 1DiDC5jb96GR2d5LVsWuSdSB3q5zbns2Bo

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

http://blockexplorer.com/address/1DiDC5jb96GR2d5LVsWuSdSB3q5zbns2Bo

You checked this?
you sure u didnt receive in your bitcoin client?
Some times Bitcoin client needs restart to get blocks & connection.

[cosurgi]

I just wanted to let you know guys that this pool works very good for me. I am getting exactly the expected amounts.

None are still confirmed. but it's OK. I would like to know how invalid blocks get handled.

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" ?

[Luke-Jr]

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.