P2Pool release 3.0 tag: 3.0 hash: a4cde222d397b47ae5646ca74a8036025d745df8 EDIT: Outdated, go to https://bitcointalk.org/index.php?topic=18313.msg971005#msg971005Changes: * 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.
|
|
|
|
If luck is the explanation of the frequency of block discovery, then we are discovering 10% below what is possible on average. The below average discovery rate could indicate resource diversion, which has already been shown publicly to occur. You could say that "Luck" is how to explain away resource diversion.
However, P2Pool is open source - there's no closed server that could be secretly diverting hashes. Please, do audit the source. It's either a bug somewhere (which I've been trying like mad to find) or just really bad luck. |
|
|
|
|
P2Pool is back to normal now. Thanks to everyone who quickly upgraded for generating a forked sharechain that got everyone else mining again.
|
|
|
|
ubuntu , p2poll script and cgminer work, but i see stderr
qdi, git pull and try again. |
|
|
|
|
Anyone using previously posted versions needs to stop using them.
|
|
|
|
|
JayCoin: I was paranoid about non-difficulty-1 shares possibly triggering bugs in miners, so I fixed the difficulty to 1 (or .9998.., rather, whatever it is)
|
|
|
|
Trying a different approach - get commit 68c11d56a46f388 (current master HEAD) instead! It reverts completely to the old behavior and doesn't drop peers. Windows: http://u.forre.st/u/oirgpput/p2pool_win32_0.11.1-39-g68c11d5.zipYou will get some errors occasionally, but they should only be like: 2012-05-18 00:52:25.520715 > exceptions.ValueError: unknown share type: 6
|
|
|
|
|
Looking into this. More news soon.
|
|
|
|
It's trivial to get the IPs of every p2pool miner, and spread the DDoS across them. Many (most?) mining pools can withstand far more bandwidth being thrown at them, than the equivalent in miners' connections, so the DDoS will require less bandwidth to pull off. Furthermore, since such a DDoS takes out the miners' connection, it effectively prevents any failover including solo mining.
To contrast, not only do other pools have higher DDoS resistance in terms of bandwidth, but they generally keep their miners' IPs private, so when/if the pool goes down, the miners are free to failover to another pool.
There are hundreds of P2Pool nodes (my node has heard of 292 active in the past day). Does any pool have a network link that can sustain multiple gigabits per second? |
|
|
|
|
The bug I discovered in Bitcoin has no affect on or relationship to P2Pool. (:
|
|
|
|
|
vindimy, what does run_p2pool.py --version print?
|
|
|
|
Also, I have a quick question, if you solve the bitcoin block do you also solve a namecoin block at the same time? I'm pretty sure that is what merged mining means.
Any Bitcoin block will definitely (at least for now) be a Namecoin block, because Bitcoin's difficulty is higher than Namecoin's. |
|
|
|
.11.1 keeps saying Couldn't link returned work's merkle root with its handler. This should only happen if this process was recently restarted!
It's been running all night, restarted earlier and it's still saying that occasionally.
It might be a buggy miner.. Which are you using? Do you have the miner configured to connect to multiple pools? |
|
|
|
Stop answering to my site graphs and to the miners.
Been having this issue for several versions, I usually restart like 15 times until it works. I'm using 2008 r2 x64
Do you remember specifically which version last worked fine? |
|
|
|
Is it normal to get stuck at this screen and stop answering? I've already restarted a few times. All the versions do this. Do i wait or keep restarting? http://screencast.com/t/uVYh9xNKgB5What do you mean by "stop answering"? Versions since 0.10.4 on Windows use the IOCP API, which may be causing problems. What version of Windows are you using, and does 0.10.3 run without problems? |
|
|
|
P2Pool release 0.11.1 tag: 0.11.1 UPGRADE REQUIRED SOONWindows binary: http://u.forre.st/u/xyewbxrx/p2pool_win32_0.11.1.zipSource ZIP: https://github.com/forrestv/p2pool/zipball/0.11.1Source TAR: https://github.com/forrestv/p2pool/tarball/0.11.1This release's sole purpose is to test possible fixes to our luck problems and provide useful data that may also help. It is a mandatory upgrade because it breaks compatibility with previous releases. Major changes: * Broadcast all block solutions, bitcoin/p2pool-stale or not, until they're 5 blocks old * Submit blocks over P2P connection to bitcoind, in addition to RPC * Automatically report caught exceptions as bug reports This switchover is different from previous ones - Instead of a scheduled time, all nodes will automatically switch 22 hours after 95% of the P2Pool hash rate has upgraded. Therefore, please upgrade as soon as possible so you're not part of the last 5%! EDIT: The current proportion of the hash rate upgraded is visible as the "2" line on the last chart at http://forre.st:9332/static/graphs.htmlEDIT: Released 0.11.1 with IOCP disabled by default.
|
|
|
|
|
Show Posts
