Due to popular demand, new data: http://eligius.st/~luke-jr/raw/5/payout_queue.txt
This isn't very useful to be honest, since there are no block boundaries. Unless I am missing something important?
Topic: [OLD] Eligius: ASIC, no registration, no fee CPPSRB BTC + 105% PPS NMC, 877 # - page 190. (Read 458487 times)
July 22, 2011, 08:37:31 AM
This isn't very useful to be honest, since there are no block boundaries. Unless I am missing something important?
July 22, 2011, 06:34:57 AM
Due to popular demand, new data: http://eligius.st/~luke-jr/raw/5/payout_queue.txt
This isn't very useful to be honest, since there are no block boundaries. Unless I am missing something important?
It seems to list users that are over the threshold sorted from oldest to most recent... I guess I agree that the list would need to be divided into block/50BTC segments according to up-to-date user balances to be useful.
July 22, 2011, 05:21:12 AM
Due to popular demand, new data: http://eligius.st/~luke-jr/raw/5/payout_queue.txt
This isn't very useful to be honest, since there are no block boundaries. Unless I am missing something important?
July 21, 2011, 09:28:49 PM
Due to popular demand, new data: http://eligius.st/~luke-jr/raw/5/payout_queue.txt
July 21, 2011, 02:49:18 PM
Whoever owns 1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE is a n00b and broke sharesrv by sending "1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE\n" as their username. I fixed and hot-patched it, so everything's fine now, but stats weren't updated while it was broken. Also, the username is still invalid-- so it is being treated as donated shares like any other invalid address. Since this one might be non-obvious, I thought I'd better post about it to try to wake whoever it is up... how do you get \n into a username anyway? -.-
Always .trim() input.
And always use trim instead of (insert your language's default way of doing it here) to avoid incoming "your language is horrible"
July 21, 2011, 12:59:07 AM
Whoever owns 1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE is a n00b and broke sharesrv by sending "1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE\n" as their username. I fixed and hot-patched it, so everything's fine now, but stats weren't updated while it was broken. Also, the username is still invalid-- so it is being treated as donated shares like any other invalid address. Since this one might be non-obvious, I thought I'd better post about it to try to wake whoever it is up... how do you get \n into a username anyway? -.-
Always .trim() input.
July 21, 2011, 12:12:46 AM
Payouts are done with "generate" transactions. If you get paid in any given block, you should see it in your wallet almost immediately, but it won't be spendable or be counted in your balance until it gets 120 confirmations.
That's what I thought would be the case but after 3 hours and having transactions from my other pool showed up, I started wondering. Anyway probing deeper and finding the transaction in block explorer made me figure I must had just experienced the same bitcoin client bug after missing transaction which some of the others had posted about. Shutting down and running bitcoin client with the -rescan option fixed that.
July 20, 2011, 09:49:27 PM
Payouts are done with "generate" transactions. If you get paid in any given block, you should see it in your wallet almost immediately, but it won't be spendable or be counted in your balance until it gets 120 confirmations.
July 20, 2011, 11:55:48 AM
Anybody knows if payout depends on whether the last block (crossing the payout floor) has gotten 120 confirmations or not?
July 20, 2011, 11:52:05 AM
Your argument assumes that there is such a thing as "x% completed" on a block. Any share has the same probability to be a valid block and invalid blocks are just bad luck because somebody else was quicker with a new block while your client did not yet get word of that block. Once you got notified there's no drawback anymore since the chances are the same. Only during the time period where somebody has published a new block and bitcoind is not yet aware of it are shares lost.
No, the problem here is that there are two sets of probabilities involved – the normal pool luck, and the risk of a block being invalid. Since all shares have equal chance of meeting the difficulty requirement it means that valid and invalid blocks would, on average, require the same amount of work. The problem then, as I see it, is that invalid blocks don't have a good luck counterpart – as I said, there are no lucky hashes that pay double. So, if a PPS pool has a 1% rate of invalid blocks it means that it will reward its miners 1% more than it earns for the valid blocks.
July 20, 2011, 09:55:21 AM
Whoever owns 1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE is a n00b and broke sharesrv by sending "1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE\n" as their username. I fixed and hot-patched it, so everything's fine now, but stats weren't updated while it was broken. Also, the username is still invalid-- so it is being treated as donated shares like any other invalid address. Since this one might be non-obvious, I thought I'd better post about it to try to wake whoever it is up... how do you get \n into a username anyway? -.-
Copy and paste by dragging down to the next line?
Fortunately, mine starts with 1MT
July 20, 2011, 09:43:01 AM
Whoever owns 1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE is a n00b and broke sharesrv by sending "1MY3ypFCDSbFYnM9jw4YvPnCfEDQz9sGGE\n" as their username. I fixed and hot-patched it, so everything's fine now, but stats weren't updated while it was broken. Also, the username is still invalid-- so it is being treated as donated shares like any other invalid address. Since this one might be non-obvious, I thought I'd better post about it to try to wake whoever it is up... how do you get \n into a username anyway? -.-
July 20, 2011, 09:07:36 AM
Your argument assumes that there is such a thing as "x% completed" on a block. Any share has the same probability to be a valid block and invalid blocks are just bad luck because somebody else was quicker with a new block while your client did not yet get word of that block. Once you got notified there's no drawback anymore since the chances are the same. Only during the time period where somebody has published a new block and bitcoind is not yet aware of it are shares lost.
Invalid blocks can't really be prevented, it can only be reduced by connecting the pools and solo-miners better so that the time is reduced in which a collision can occur. But it can't be reduced to 0.
It's the same with offline time, by the way. During the 8 hours that Eligius was offline recently which resulted in a 33-hour round, no shares were really lost although a couple of blocks were generated. So it's perfectly OK to pay for shares on invalid, old and long running rounds since a valid block can be found with every share and the probability is independent of how long the round has been running / not running.
Invalid blocks can't really be prevented, it can only be reduced by connecting the pools and solo-miners better so that the time is reduced in which a collision can occur. But it can't be reduced to 0.
It's the same with offline time, by the way. During the 8 hours that Eligius was offline recently which resulted in a 33-hour round, no shares were really lost although a couple of blocks were generated. So it's perfectly OK to pay for shares on invalid, old and long running rounds since a valid block can be found with every share and the probability is independent of how long the round has been running / not running.
July 20, 2011, 02:42:58 AM
I see a spike on the reward graph that seems to indicate there was an invalid block in the last long round. It's the first I've noticed on Su, and considering the number of valid blocks since the server was started up I'd say the ratio is quite good.
But, what I'm wondering, is how well paying full PPS for rounds that include invalid blocks will work in the long run. It feels like it, eventually, will push the pool's balance into the red since there are no "extra valid" blocks that pay double to help correct the relation between luck and available funds.
I assume this is something that has been given thought, but it feels like something worth a bit of discussion as well.
But, what I'm wondering, is how well paying full PPS for rounds that include invalid blocks will work in the long run. It feels like it, eventually, will push the pool's balance into the red since there are no "extra valid" blocks that pay double to help correct the relation between luck and available funds.
I assume this is something that has been given thought, but it feels like something worth a bit of discussion as well.
July 20, 2011, 02:22:34 AM
is there a JSON output for individual user stats
July 19, 2011, 11:42:10 PM
Ha, that explains it alright!
Thanks for the quick answers, I appreciate it.
Thanks for the quick answers, I appreciate it.
July 19, 2011, 11:31:18 PM
Interesting, thanks.
Related question: Why such a tiny payout for the last couple short blocks? Seems like the other 40odd btc ought to have been paid out too instead of just 2-3 btc going out.
I may well be missing something
Last two blocks were very short; people only earned 2 BTC and 3 BTC total each, respectively. The remainder was used to pay off debt incurred by the 30 hour block before that... Related question: Why such a tiny payout for the last couple short blocks? Seems like the other 40odd btc ought to have been paid out too instead of just 2-3 btc going out.
I may well be missing something
July 19, 2011, 11:30:31 PM
I keep having issues connecting to the server since about 12~18hrs ago. Every so often, I'll see that my miner's gone to the backup pool and looking at the hash rates, it seems like 30~40% of the time 
July 19, 2011, 11:26:24 PM
Interesting, thanks.
Related question: Why such a tiny payout for the last couple short blocks? Seems like the other 40odd btc ought to have been paid out too instead of just 2-3 btc going out.
I may well be missing something
Related question: Why such a tiny payout for the last couple short blocks? Seems like the other 40odd btc ought to have been paid out too instead of just 2-3 btc going out.
I may well be missing something
July 19, 2011, 11:10:34 PM
Is there a page that lists where you are as far as being paid off?
If not, that'd be a fantastic feature, to be able to see how many people are owed how much before it's your turn.
Only the next block is calculated: http://eligius.st/~luke-jr/raw/5/current_block.json If not, that'd be a fantastic feature, to be able to see how many people are owed how much before it's your turn.
Jump to: