Thanks to whoever donated 95BTC to the pool 
https://bitcointalksearch.org/topic/m.1656014 
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 580. (Read 2591920 times)
March 22, 2013, 02:30:03 PM
March 22, 2013, 12:58:08 PM
News for p2pool LTC users.
https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232
See gwyverlb's excellent writeup to get the most out of p2pool.
https://github.com/forrestv/p2pool/commit/d2e2257e959812186f0c78384decb37d8181c4d4
All p2pool LTC users should upgrade to the latest p2pool git for this important fix that should help speed up our found blocks and reduce the risk of block orphans.
https://github.com/forrestv/p2pool/pull/86
This should fix the flood of "hash > target" errors that bogs down p2pool. Hopefully forrestv pulls soon so you can upgrade everything with a single pull.
If you have problems with repetitive tracebacks in stratum.py while mining LTC, try upgrading to cgminer-2.11.2+. They fixed some kind of corruption bug. You were losing some work!
https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232
See gwyverlb's excellent writeup to get the most out of p2pool.
https://github.com/forrestv/p2pool/commit/d2e2257e959812186f0c78384decb37d8181c4d4
All p2pool LTC users should upgrade to the latest p2pool git for this important fix that should help speed up our found blocks and reduce the risk of block orphans.
https://github.com/forrestv/p2pool/pull/86
This should fix the flood of "hash > target" errors that bogs down p2pool. Hopefully forrestv pulls soon so you can upgrade everything with a single pull.
If you have problems with repetitive tracebacks in stratum.py while mining LTC, try upgrading to cgminer-2.11.2+. They fixed some kind of corruption bug. You were losing some work!
Good to see submitblock is fixed on litecoin:-) Maybe there should be also version check, so when submitblock *is* supported on litecoin, it will be also used?
I like p2pool and I think it gives a bit more reward than traditional pools. However, when using p2pool with litecoin, I noticed my web browsing was clearly slowed down.. tested my network connection and found out that speed was ok, but ping latency had increased from 40 ms to 300 ms! Maybe it's because of the too low difficulty with litecoin?
March 22, 2013, 12:46:15 PM
Thanks to whoever donated 95BTC to the pool
?95BTC = $6,650 at current price. For real?
M
Ah, sry, I missread the transaction. 25BTC was donated.
25BTC is a very geneorous gift. Thank you again.
where do you see this?
M
http://blockchain.info/tx/6521b0513f3077a983b82eb92cc95ecc24ad2a7ca3afdba082ef71ea8d25a868
Thanks, Gavin!
March 22, 2013, 09:07:27 AM
Thanks to whoever donated 95BTC to the pool
?95BTC = $6,650 at current price. For real?
M
Ah, sry, I missread the transaction. 25BTC was donated.
25BTC is a very geneorous gift. Thank you again.
where do you see this?
M
http://blockchain.info/tx/6521b0513f3077a983b82eb92cc95ecc24ad2a7ca3afdba082ef71ea8d25a868
March 22, 2013, 08:38:48 AM
Thanks to whoever donated 95BTC to the pool
?95BTC = $6,650 at current price. For real?
M
Ah, sry, I missread the transaction. 25BTC was donated.
25BTC is a very geneorous gift. Thank you again.
where do you see this?
M
March 22, 2013, 08:05:19 AM
Thanks to whoever donated 95BTC to the pool
?95BTC = $6,650 at current price. For real?
M
Ah, sry, I missread the transaction. 25BTC was donated.
25BTC is a very geneorous gift. Thank you again.
March 22, 2013, 07:55:39 AM
I just pushed a commit that should fix the traceback. All it does is ignore the extra argument cgminer provides to mining.subscribe (which is cgminer's version).
tyvm. that fixed the message, not being able to use stratum, and cgminer crashing.
M
March 22, 2013, 07:53:16 AM
Thanks to whoever donated 95BTC to the pool
?95BTC = $6,650 at current price. For real?
M
March 22, 2013, 07:52:04 AM
Thanks to whoever donated 95BTC to the pool
March 22, 2013, 06:08:53 AM
I am testing p2pool now and have a few questions. My machine makes 30-35 MH/s with bfgminer. The output of the bfgminer says that accepted shares are around 30, but the stats page says: Accepted shares:0, and at the p2pool console i see: Exprected time to share: 21h . What does this mean? Would i receive a payment for these 30 shares or i have to mine more ~21 hours to receive payment?
Miner reporting sd=1 hasres. To get payout in p2pool you need sd=500 or more share (read pool log for current share diff).On 35MH you can not get even single share for all day of mining... all depends on luck. It says 21Hrs = you can get share in 12hrs or in 30hrs... too big variance too little hash power.
Try mine TRC instead of BTC.
March 22, 2013, 05:42:00 AM
I am testing p2pool now and have a few questions. My machine makes 30-35 MH/s with bfgminer. The output of the bfgminer says that accepted shares are around 30, but the stats page says: Accepted shares:0, and at the p2pool console i see: Exprected time to share: 21h . What does this mean? Would i receive a payment for these 30 shares or i have to mine more ~21 hours to receive payment?
Shares submitted is not chain shares found. At 35mh/s, it will take a long time to find a share.. and that share won't get you very much BTC. It'll be very little BTC in fact. Right now you're spending more money on electricity than you will recoup from BTC.
M
March 22, 2013, 05:13:34 AM
I am testing p2pool now and have a few questions. My machine makes 30-35 MH/s with bfgminer. The output of the bfgminer says that accepted shares are around 30, but the stats page says: Accepted shares:0, and at the p2pool console i see: Exprected time to share: 21h . What does this mean? Would i receive a payment for these 30 shares or i have to mine more ~21 hours to receive payment?
March 22, 2013, 03:45:43 AM
News for p2pool LTC users.
https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232
See gwyverlb's excellent writeup to get the most out of p2pool.
https://github.com/forrestv/p2pool/commit/d2e2257e959812186f0c78384decb37d8181c4d4
All p2pool LTC users should upgrade to the latest p2pool git for this important fix that should help speed up our found blocks and reduce the risk of block orphans.
https://github.com/forrestv/p2pool/pull/86
This should fix the flood of "hash > target" errors that bogs down p2pool. Hopefully forrestv pulls soon so you can upgrade everything with a single pull.
If you have problems with repetitive tracebacks in stratum.py while mining LTC, try upgrading to cgminer-2.11.2+. They fixed some kind of corruption bug. You were losing some work!
https://bitcointalksearch.org/topic/a-guide-for-mining-efficiently-on-p2pool-includes-fud-repellent-and-faq-153232
See gwyverlb's excellent writeup to get the most out of p2pool.
https://github.com/forrestv/p2pool/commit/d2e2257e959812186f0c78384decb37d8181c4d4
All p2pool LTC users should upgrade to the latest p2pool git for this important fix that should help speed up our found blocks and reduce the risk of block orphans.
https://github.com/forrestv/p2pool/pull/86
This should fix the flood of "hash > target" errors that bogs down p2pool. Hopefully forrestv pulls soon so you can upgrade everything with a single pull.
If you have problems with repetitive tracebacks in stratum.py while mining LTC, try upgrading to cgminer-2.11.2+. They fixed some kind of corruption bug. You were losing some work!
March 22, 2013, 12:40:46 AM
I just pushed a commit that should fix the traceback. All it does is ignore the extra argument cgminer provides to mining.subscribe (which is cgminer's version).
March 21, 2013, 10:31:48 PM
Now that p2pool seems to have recovered, I'm trying to use it again. I found whenever cgminer 2.11.x tries to connect, I get this error from p2pool. 2.10.5 doesn't do it. With my machine with one GPU, cgminer is able to mine. With the machine with 4 GPUs, cgminer hangs and then crashes. This is on win7 x64. What gives?
If it's cgminer crashing and not P2Pool the cgminer thread would be a better place to find a solution. I've seen the kind of stacktrace you got with connectivity problems.
p2pool gives the error when cgminer tries to connect.
I know the cgminer guys read here, maybe they'll pipe up.
M
Also, while 2.10.5 works, it isn't working right. On the 4xgpu box, it sits there for a good 30 seconds just showing the version before it starts. Then it starts on LP instead of stratum. I get this when using the windows .exe build for 11.2, as well as directly with python with latest source git. My 1 gpu rig connects right up immediately with stratum.
M
March 21, 2013, 09:52:44 PM
Now that p2pool seems to have recovered, I'm trying to use it again. I found whenever cgminer 2.11.x tries to connect, I get this error from p2pool. 2.10.5 doesn't do it. With my machine with one GPU, cgminer is able to mine. With the machine with 4 GPUs, cgminer hangs and then crashes. This is on win7 x64. What gives?
If it's cgminer crashing and not P2Pool the cgminer thread would be a better place to find a solution. I've seen the kind of stacktrace you got with connectivity problems.
p2pool gives the error when cgminer tries to connect.
I know the cgminer guys read here, maybe they'll pipe up.
M
March 21, 2013, 09:02:38 PM
Now that p2pool seems to have recovered, I'm trying to use it again. I found whenever cgminer 2.11.x tries to connect, I get this error from p2pool. 2.10.5 doesn't do it. With my machine with one GPU, cgminer is able to mine. With the machine with 4 GPUs, cgminer hangs and then crashes. This is on win7 x64. What gives?
If it's cgminer crashing and not P2Pool the cgminer thread would be a better place to find a solution. I've seen the kind of stacktrace you got with connectivity problems.
March 21, 2013, 07:37:16 PM
Now that p2pool seems to have recovered, I'm trying to use it again. I found whenever cgminer 2.11.x tries to connect, I get this error from p2pool. 2.10.5 doesn't do it. With my machine with one GPU, cgminer is able to mine. With the machine with 4 GPUs, cgminer hangs and then crashes. This is on win7 x64. What gives?
M
Code:
2013-03-21 20:20:56.830000 > Squelched JSON error:
2013-03-21 20:20:56.830000 > Traceback (most recent call last):
2013-03-21 20:20:56.830000 > File "c:\python27\lib\site-packages\twisted\proto
cols\basic.py", line 455, in dataReceived
2013-03-21 20:20:56.830000 > self.lineReceived(line)
2013-03-21 20:20:56.830000 > File "C:\mining\p2pool\p2pool\util\jsonrpc.py", l
ine 164, in lineReceived
2013-03-21 20:20:56.830000 > _handle(line, self, response_handler=self._matc
her.got_response).addCallback(lambda line2: self.sendLine(line2) if line2 is not
None else None)
2013-03-21 20:20:56.830000 > File "c:\python27\lib\site-packages\twisted\inter
net\defer.py", line 1187, in unwindGenerator
2013-03-21 20:20:56.830000 > return _inlineCallbacks(None, gen, Deferred())
2013-03-21 20:20:56.830000 > File "c:\python27\lib\site-packages\twisted\inter
net\defer.py", line 1045, in _inlineCallbacks
2013-03-21 20:20:56.830000 > result = g.send(result)
2013-03-21 20:20:56.840000 > ------
2013-03-21 20:20:56.840000 > File "C:\mining\p2pool\p2pool\util\jsonrpc.py", l
ine 85, in _handle
2013-03-21 20:20:56.840000 > result = yield method_meth(*list(preargs) + lis
t(params))
2013-03-21 20:20:56.840000 > exceptions.TypeError: rpc_subscribe() takes exactly
1 argument (2 given)
2013-03-21 20:20:56.840000 > Squelched JSON error:
2013-03-21 20:20:56.840000 > Traceback (most recent call last):
2013-03-21 20:20:56.840000 > File "c:\python27\lib\site-packages\twisted\proto
cols\basic.py", line 455, in dataReceived
2013-03-21 20:20:56.840000 > self.lineReceived(line)
2013-03-21 20:20:56.850000 > File "C:\mining\p2pool\p2pool\util\jsonrpc.py", l
ine 164, in lineReceived
2013-03-21 20:20:56.850000 > _handle(line, self, response_handler=self._matc
her.got_response).addCallback(lambda line2: self.sendLine(line2) if line2 is not
None else None)
2013-03-21 20:20:56.850000 > File "c:\python27\lib\site-packages\twisted\inter
net\defer.py", line 1187, in unwindGenerator
2013-03-21 20:20:56.850000 > return _inlineCallbacks(None, gen, Deferred())
2013-03-21 20:20:56.850000 > File "c:\python27\lib\site-packages\twisted\inter
net\defer.py", line 1045, in _inlineCallbacks
2013-03-21 20:20:56.850000 > result = g.send(result)
2013-03-21 20:20:56.850000 > ------
2013-03-21 20:20:56.850000 > File "C:\mining\p2pool\p2pool\util\jsonrpc.py", l
ine 85, in _handle
2013-03-21 20:20:56.850000 > result = yield method_meth(*list(preargs) + lis
t(params))
2013-03-21 20:20:56.860000 > exceptions.TypeError: rpc_subscribe() takes exactly
1 argument (2 given)
M
March 21, 2013, 04:09:03 PM
This change to v2 blocks is also a good chance to upgrade to bitcoind 0.8.1 if you haven't done so already.
Note that you only need 0.7.0 or later to generate v2 blocks. Upgrading to 0.8.1 from any 0.7.x is still advisable for P2Pool miners (for efficiency reasons). 
March 21, 2013, 03:48:55 PM
Just a note for p2pool miners (and possibly a required hard fork for p2pool software versions): Version 2 blocks (height-in-coinbase) will likely hit supermajority next week which will make any attempt to submit a Version1 block be orphaned by the rest of the network. Deepbit has switched, BTC Guild has finally patched the getwork pools, and Ozcoin is closing getwork entirely. After ~1 week, the 1,000 block window used to evaluate 95% supermajority has a good chance of triggering, and once it is triggered it will never turn off.
This change to v2 blocks is also a good chance to upgrade to bitcoind 0.8.1 if you haven't done so already.
This change to v2 blocks is also a good chance to upgrade to bitcoind 0.8.1 if you haven't done so already.
Jump to: