Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 678. (Read 2591920 times)
Almost 30% updated, keep it coming!
P2Pool release 3.0 tag: 3.0 hash: a4cde222d397b47ae5646ca74a8036025d745df8
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
I'm pointing one of my miners to a local instance of this... hoping it works better than last time.
M
The pool has been exceedingly lucky since the 14th June, with a mean round length of 0.6975. This means you'll get paid much more than PPS.
However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
Yes, because we have "dry days" just before. As someone said: in long run it is all the same.However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
P2pool have few BIG advantages over other pools, thats why I support it, not only for income.
In fact, I pay more for electric power than I make coins on my machine. But I like Bitcoin idea too much
LOL. Too bad we don't have more of you people.
Too many profiteers around here wishing to suck the gold stream dry like BFL and gigavps.
updated my node, thanks forrestv!
20% of network is updated so far, download and install fresh version!
Nevermind, I'm an idiot.
The correlation is just crazy
Is there any way to reduce the verbosity of the logs that P2Pool keeps? I've searched this topic but come up empty-handed.
If you're running from source edit main.py, around line 894 to this:
if time.time() > last_time + 60:
This will print out pool stats one a minute instead every 15 seconds or less.
Is there any way to reduce the verbosity of the logs that P2Pool keeps? I've searched this topic but come up empty-handed.
15% of pool is on v3. Keep updating ppl!
The pool has been exceedingly lucky since the 14th June, with a mean round length of 0.6975. This means you'll get paid much more than PPS.
However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
Yes, because we have "dry days" just before. As someone said: in long run it is all the same.However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
P2pool have few BIG advantages over other pools, thats why I support it, not only for income.
And that's the reason you should continue mining at p2Pool, despite the lower earnings. I have no doubt that the current round length problem will be fixed eventually, but at the moment you are paying a price for the p2Pool advantages.
The pool has been exceedingly lucky since the 14th June, with a mean round length of 0.6975. This means you'll get paid much more than PPS.
However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
Yes, because we have "dry days" just before. As someone said: in long run it is all the same.However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
P2pool have few BIG advantages over other pools, thats why I support it, not only for income.
In fact, I pay more for electric power than I make coins on my machine. But I like Bitcoin idea too much
Q: how exactly is calculated expected time to block when block found? Current pool hash rate or some average of time that block was mined?
I`m still not sure that our luck chart is good... If we founding blocks "in time" I`m gettin much more than from any pps pool... For me luck is much higher than 90%
What's your average daily earnings and average hashrate for the current difficulty period? If you can tell me that, I'll tell you whether or not you're getting more or less than expected.I`m still not sure that our luck chart is good... If we founding blocks "in time" I`m gettin much more than from any pps pool... For me luck is much higher than 90%
I`m taking 0.025 per block or more (even 0.05) from P2pool.
I was mining on 2 pps pools and get about 0.07-0.075 BTC/day.
For me P2pool is best
16-06:
0.04103741 BTC
0.03053837 BTC
0.03054256 BTC
0.03571901 BTC
0.03559559 BTC
Total: 0,17343294
15-06:
0.03603529 BTC
0.03502059 BTC
0.03518694 BTC
0.03513995 BTC
0.04118142 BTC
Total: 0,18256419
ANY PPS pool give me that
BTW fixed BTCLauncher, uploaded to skydrive. There was bug in saving run_p2pool.exe patch to options.
The pool has been exceedingly lucky since the 14th June, with a mean round length of 0.6975. This means you'll get paid much more than PPS.
However, this is a reflection of the variance inherent in bitcoin mining. If you recorded your fortnightly average, you'd find it much less than PPS, since the average p2Pool roundlength for the last two weeks was 1.204.
The average round length since the start of p2Pool is about 1.11. So, since the start of p2Pool, average miner earnings are less than PPS.
Q: how exactly is calculated expected time to block when block found? Current pool hash rate or some average of time that block was mined?
I`m still not sure that our luck chart is good... If we founding blocks "in time" I`m gettin much more than from any pps pool... For me luck is much higher than 90%
What's your average daily earnings and average hashrate for the current difficulty period? If you can tell me that, I'll tell you whether or not you're getting more or less than expected.I`m still not sure that our luck chart is good... If we founding blocks "in time" I`m gettin much more than from any pps pool... For me luck is much higher than 90%
I`m taking 0.025 per block or more (even 0.05) from P2pool.
I was mining on 2 pps pools and get about 0.07-0.075 BTC/day.
For me P2pool is best
16-06:
0.04103741 BTC
0.03053837 BTC
0.03054256 BTC
0.03571901 BTC
0.03559559 BTC
Total: 0,17343294
15-06:
0.03603529 BTC
0.03502059 BTC
0.03518694 BTC
0.03513995 BTC
0.04118142 BTC
Total: 0,18256419
ANY PPS pool give me that
BTW fixed BTCLauncher, uploaded to skydrive. There was bug in saving run_p2pool.exe patch to options.
Honestly, without looking at the code, this sounds like it's begging to be exploited as an attack vector.
Gotta keep that FUD machine well oiled, enh?
It's fine. It validates the header, and if its correct and ahead of the local node it builds on that instead until the local node catches up. An attacker would need to burn a block just to make p2pool nodes burn less than a block. They'll, of course, stop skipping when their local node advances down another path.
In the future p2pool nodes could watch for the local node to reject a block and then reject it themselves to further narrow things, but I don't see an issue currently. There are other more effective attacks available.
P2Pool release 3.0 tag: 3.0 hash: a4cde222d397b47ae5646ca74a8036025d745df8
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
updated and running fine.
@ forrestv:
great job!
I think it would be good to update the first post of this thread, because most people looking for updates will search there at first. imho
I would like to ask for a x64 build again tho
Look @ my skidrive http://sdrv.ms/NtmDt5
Only for bitcoin! Litecoin module not complied/included.
My node also updated.
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
Honestly, without looking at the code, this sounds like it's begging to be exploited as an attack vector. 
P2Pool release 3.0 tag: 3.0 hash: a4cde222d397b47ae5646ca74a8036025d745df8
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
Windows binary: http://u.forre.st/u/lgljvrzx/p2pool_win32_3.0.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/3.0
Source tarball: https://github.com/forrestv/p2pool/tarball/3.0
Changes:
* P2Pool will "skip ahead" to building on blocks not yet processed by the local bitcoind based on block headers received from P2Pool peers. This should significantly reduce the number of orphaned blocks we have if everyone upgrades.
* Latency/high CPU usage caused by requesting shares from old nodes is fixed by now not downloading shares more than a day old
This change increments the share version to 3, so once 50% of people upgrade, the rest will be notified by messages on their P2Pool console. So, please upgrade! Note that this isn't a hard fork of the P2Pool chain, so old nodes will continue to work, only spamming the upgrade messages.
Node upgraded with version 3. I too would like to check the Win64bit version if possible please.
I would like to ask for a x64 build again tho
Jump to: