[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[roy7]

Also, we're 82% of the way there now. Almost done.

lol.

[1713544617]

1713544617

[1713544617]

1713544617

[1713544617]

1713544617

[organofcorti]

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.

Expect 1.2 days (as the web page says )
Past mining doesn't effect when you will find a block ...

Maybe he was too subtle, but that's the joke he was making.

If he'd written "I know its been a long wait, but I expect it should only take about one more day to get a block" it would have been funnier. And more accurate

Also, we're 82% of the way there now. Almost done.

And now back to ~1.2 days until the next block. I expect.

[mdude77]

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.

Expect 1.2 days (as the web page says )
Past mining doesn't effect when you will find a block ...

Maybe he was too subtle, but that's the joke he was making.

If he written "I know its been a long wait, but I expect it should only take about one more day to get a block" it would have been funnier. And more accurate

Also, we're 82% of the way there now. Almost done.

And now back to ~1.2 days until the next block. I expect.

Be positive people!  I expect one in the next 5 mins.  And another one after that!  After all, past performance doesn't affect future results.

M

[organofcorti]

I know its been a long wait, but now it should only take about one more day to get a block.  Just FYI.

Expect 1.2 days (as the web page says )
Past mining doesn't effect when you will find a block ...

Maybe he was too subtle, but that's the joke he was making.

If he written "I know its been a long wait, but I expect it should only take about one more day to get a block" it would have been funnier. And more accurate

Also, we're 82% of the way there now. Almost done.

And now back to ~1.2 days until the next block. I expect.

Be positive people!  I expect one in the next 5 mins.  And another one after that!  After all, past performance doesn't affect future results.

M

However, the expectation is of a new block in ~1.2 days.

[KyrosKrane]

Well, we finally broke the streak! ...

Pool Luck (7 days, 30 days, 90 days): 49.5% 88.2% 85.2%

... yeah.

[jedimstr]

Yay, time for another 5 day dry spell until the next one.  Maybe we'll break the record again.

[jacob019]

3 blocks in 20 hours  

seems luck remembered we were owed a few

[jedimstr]

3 blocks in 20 hours  

seems luck remembered we were owed a few

Shhhh... LadyLuck may hear you.... And give us another bad streak out of spite.

[kano]

3 blocks in 20 hours  

seems luck remembered we were owed a few

2 blocks in 21 hrs
3 blocks in 107 hrs

[jacob019]

3 blocks in 20 hours  

seems luck remembered we were owed a few

2 blocks in 21 hrs
3 blocks in 107 hrs

Block #294121 - 2014-04-04 08:13:16
Block #294292 - 2014-04-05 03:35:13
Block #294304 - 2014-04-05 05:06:18
---3 blocks in 20 hours 53 minutes

[kano]

3 blocks in 20 hours  

seems luck remembered we were owed a few

2 blocks in 21 hrs
3 blocks in 107 hrs

Block #294121 - 2014-04-04 08:13:16
Block #294292 - 2014-04-05 03:35:13
Block #294304 - 2014-04-05 05:06:18
---3 blocks in 20 hours 53 minutes

2 blocks.

3 = fail at maths.

[jacob019]

Sorry friend, seems we're both developers who use much more advanced math than addition, so I don't see how we could disagree on basic addition.
The following blocks were found by P2Pool at the specified time:
Block #294121 - 2014-04-04 08:13:16
Block #294292 - 2014-04-05 03:35:13
Block #294304 - 2014-04-05 05:06:18

Between the 4/4 08:13:00 and 4/5 05:06:59, that's a 21 hour 53 second period within which three blocks were found.  Given your work with cgminer, it seems you have some great programming skills, but here you chime in to tell me I'm wrong when it's clearly not the case.  Embarrassed to admit you're wrong?

[Krak]

Sorry friend, seems we're both developers who use much more advanced math than addition, so I don't see how we could disagree on basic addition.
The following blocks were found by P2Pool at the specified time:
Block #294121 - 2014-04-04 08:13:16
Block #294292 - 2014-04-05 03:35:13
Block #294304 - 2014-04-05 05:06:18

Between the 4/4 08:13:00 and 4/5 05:06:59, that's a 21 hour 53 second period within which three blocks were found.  Given your work with cgminer, it seems you have some great programming skills, but here you chime in to tell me I'm wrong when it's clearly not the case.  Embarrassed to admit you're wrong?

I'm pretty sure it's because you're not including the time leading up to the first block. That needs to be taken into account.

[PatMan]

Jacob - think about it dude......

I'll have what you're smoking......

[smooth]

Can you guys put your energy into finding blocks please.

[jacob019]

Three blocks were found in 21 hours.  I see the logic though, three rounds took longer.

[jonnybravo0311]

Since you all are discussing blocks and how long it is taking to find them, perhaps I could get a little help on the payouts.  I understand p2pool has a higher variance than traditional pools.  I understand the ddos-resistant nature of the setup.  I believe in it - enough to have setup and run my own p2pool node on a Mac, and post a tutorial on how to do so in another forum.

Having written that, I'm wondering how the payouts are affected by long droughts between block finds, and hope someone can clarify things for me.  Let's take a couple of examples and walk through them.  For the sake of the discussion, we will assume that there is a constant 200GH/s miner, a difficulty that does not increase and an expected payout of 0.01BTC per day in all of the examples.

Example 1: Miner finds a valid share every 4 hours.  Pool finds a block every 24 hours.
This is the average example, so I would expect payout to be right on that 0.01BTC per day.  Is my understanding correct?

Example 2: Miner finds a valid share every 4 hours.  Pool finds a block every 96 hours.
In this example, the miner is still working and finding shares; however the pool has hit a string of bad luck and doesn't find a block for 4 days.  Does the miner get rewarded for having submitted shares successfully during the entire 96 hours, or will only a given window of those shares be counted?  In other words, when the pool finds the block, does the miner get paid for 4 days of work, or 1?  My understanding is that this is a bad luck case, and the miner would only get the expected 0.01BTC once the pool finds the block.  Is my understanding correct?

Example 3: Miner finds 4 invalid shares (orphans) per day.  Pool finds a block every 24 hours.
Here the miner's shares are beat getting into the share chain - at least that is what I assume orphaned means, if my understanding is wrong, then please define orphaned and dead shares as they relate to p2pool.  My understanding here is that the miner would not be paid out anything because all of the shares submitted are invalid.  Is this correct?

Example 4: Miner finds 4 valid shares a day for 3 days, but finds all invalid shares on the 4th day.  Pool finds block on the 5th day.
So, the miner has been chugging along for 4 days, happily submitting shares.  Unfortunately on the 4th day all of the submitted shares were invalid.  If things follow the pattern I've laid out in previous examples, then the miner doesn't get paid for his efforts because the only shares seen in the past 24 hours are invalid ones.  Is my understanding correct?

Example 5: Miner finds 8 valid shares in a day.  Pool finds 2 blocks a day.
Since the examples have been all doom and gloom up to this point, let's look at the other side of the coin - where lady luck shines on us a bit.  Here the miner is finding and submitting twice the expected amount of work and the pool is finding double the number of blocks.  In this case, I expect that the miner would be making 4 times the expected payout.  Twice as much because he's finding double the shares and twice as much again because the pool is finding 2 blocks in that 24 hour window.  Is this correct?

Thanks in advance to everyone for helping!

[mdude77]

Sharing the alert:


Get 0.9.1 immediately if you are using 0.9.0!!  See the alert on the top:

News: ♦♦ A bug in OpenSSL, used by Bitcoin-Qt/Bitcoin Core, could allow your bitcoins to be stolen. Immediately updating Bitcoin Core to 0.9.1 is required in some cases, especially if you're using 0.9.0.

!!!!!

https://bitcoin.org/bin/0.9.1/

M

[smooth]

Sharing the alert:


Get 0.9.1 immediately if you are using 0.9.0!!  See the alert on the top:

News: ♦♦ A bug in OpenSSL, used by Bitcoin-Qt/Bitcoin Core, could allow your bitcoins to be stolen. Immediately updating Bitcoin Core to 0.9.1 is required in some cases, especially if you're using 0.9.0.

!!!!!

https://bitcoin.org/bin/0.9.1/

M

Does p2pool itself use openssl?

[smooth]

Having written that, I'm wondering how the payouts are affected by long droughts between block finds, and hope someone can clarify things for me.

I'm really, really lazy when it comes to forum posts so I have to confess TLDR.

But let me say this, when we have droughts, nobody gets paid. End of story. Doesn't matter if you are a large miner, a small miner, or in between, you get nothing.

Obviously that is not good for variance.

Small miners who don't always have shares active on the (3 day) chain will have it a bit worse in relative terms (though much less bad in absolute terms, imagine having an electric bill of $1000/day and no blocks to show for it), but its bad for everyone.