Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 785. (Read 2591971 times)
February 11, 2012, 09:35:36 PM
Can I just do git pull and restart to update?
February 11, 2012, 09:12:20 PM
Are we having another split? ...
The only way to tell whether you're on a split is if the displayed pool hashrate is significantly less than what it actually is, which is currently ~200GH/s. ......
Code:
2012-02-12 02:59:38.372000 P2Pool: 17350 shares in chain (8969 verified/17354 total) Peers: 30 (0 incoming)
If P2Pool's data directory was removed, it has to redownload the sharechain, and it can only verify half of them then. You have to wait a day for them all to be verified. If another sharechain is coexisting with the main one, your client will download both and might display about a quarter as unverified... But that's not the problem here.
This instance of p2pool had an empty data directory, so your explanation makes sense. Thanks again forestv!
February 11, 2012, 09:03:55 PM
Are we having another split? My p2pool is verifying only half of the total shares in the chain at the moment, and estimated current payout is about half of what it usually is.
I'm running p2pool tag 0.8.5.
I'm running p2pool tag 0.8.5.
The only way to tell whether you're on a split is if the displayed pool hashrate is significantly less than what it actually is, which is currently ~200GH/s. Your estimated payout can decrease if your payout address changes, which can happen automatically if you restart Bitcoin.
Thank you for the answer forestv. I'm getting ~200GH/s so I guess I'm still on the main pool.
By the way, can you think of a reason why only half of the shares in the chain would be reported as verified? This happened to me only once before and it was during a split, which is why I thought it could be happening again.
Code:
2012-02-12 02:59:38.372000 P2Pool: 17350 shares in chain (8969 verified/17354 total) Peers: 30 (0 incoming)
If P2Pool's data directory was removed, it has to redownload the sharechain, and it can only verify half of them then. You have to wait a day for them all to be verified. If another sharechain is coexisting with the main one, your client will download both and might display about a quarter as unverified... But that's not the problem here.
February 11, 2012, 09:01:16 PM
Are we having another split? My p2pool is verifying only half of the total shares in the chain at the moment, and estimated current payout is about half of what it usually is.
I'm running p2pool tag 0.8.5.
I'm running p2pool tag 0.8.5.
The only way to tell whether you're on a split is if the displayed pool hashrate is significantly less than what it actually is, which is currently ~200GH/s. Your estimated payout can decrease if your payout address changes, which can happen automatically if you restart Bitcoin.
Thank you for the answer forestv. I'm getting ~200GH/s so I guess I'm still on the main pool.
By the way, can you think of a reason why only half of the shares in the chain would be reported as verified? This happened to me only once before and it was during a split, which is why I thought it could be happening again.
Code:
2012-02-12 02:59:38.372000 P2Pool: 17350 shares in chain (8969 verified/17354 total) Peers: 30 (0 incoming)
February 11, 2012, 08:52:08 PM
Are we having another split? My p2pool is verifying only half of the total shares in the chain at the moment, and estimated current payout is about half of what it usually is.
I'm running p2pool tag 0.8.5.
I'm running p2pool tag 0.8.5.
The only way to tell whether you're on a split is if the displayed pool hashrate is significantly less than what it actually is, which is currently ~200GH/s. Your estimated payout can decrease if your payout address changes, which can happen automatically if you restart Bitcoin.
February 11, 2012, 08:44:45 PM
What caused the huge ass spike in LTC? Pool is at 3614kHash/s!
February 11, 2012, 08:30:34 PM
Are we having another split? My p2pool is verifying only half of the total shares in the chain at the moment, and estimated current payout is about half of what it usually is.
I'm running p2pool tag 0.8.5.
I'm running p2pool tag 0.8.5.
February 11, 2012, 07:42:30 PM
P2Pool release 0.8.5 - tag: 0.8.5 - UPDATE REQUIRED BEFORE FEB 20
Windows py2exe binary: http://u.forre.st/u/bqdrizaq/p2pool_win32_5250df6.zip
Source tarball: https://github.com/forrestv/p2pool/tarball/0.8.5
Changes:
* Compatibility with Bitcoin's protocol change on Feb 20 - see http://bitcoin.stackexchange.com/questions/2788/what-are-the-february-20-changes-to-the-bitcoin-protocol
* Some possible bugs in sharechain ranking have been fixed, so forks may be prevented
* Directory for storing P2Pool data can now be specified with --datadir
* Better local hash rate estimation
Note: I would recommend switching to Bitcoin 0.6.0 RC 1, which includes the RPC getblock call. The getblock call lets P2Pool keep track of block heights more robustly, and so might protect you from sharechain forks. Download it from https://bitcointalksearch.org/topic/version-06-release-candidate-1-63165
Windows py2exe binary: http://u.forre.st/u/bqdrizaq/p2pool_win32_5250df6.zip
Source tarball: https://github.com/forrestv/p2pool/tarball/0.8.5
Changes:
* Compatibility with Bitcoin's protocol change on Feb 20 - see http://bitcoin.stackexchange.com/questions/2788/what-are-the-february-20-changes-to-the-bitcoin-protocol
* Some possible bugs in sharechain ranking have been fixed, so forks may be prevented
* Directory for storing P2Pool data can now be specified with --datadir
* Better local hash rate estimation
Note: I would recommend switching to Bitcoin 0.6.0 RC 1, which includes the RPC getblock call. The getblock call lets P2Pool keep track of block heights more robustly, and so might protect you from sharechain forks. Download it from https://bitcointalksearch.org/topic/version-06-release-candidate-1-63165
February 11, 2012, 07:34:05 PM
'GOT BLOCK FROM MINER' means you found a block.
Cool. Just checked my logs and I found a block yesterday. Woot! February 11, 2012, 07:28:30 PM
I see this line under current payouts.. is it anything to be worried about or is it someone just using a weird payout address?
"Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,
I see this at the bottom of the table on this page."Unknown. Script: 202986d5879cfd55f909e272989e1bcc3861dbb8c0a8f4ecb4cf904bcecb5f2c90": 0,
I thought it was someone who had specified a bad address with the "-a" option. But that was just a guess. Smart people will help...
That output is just a quirk of P2Pool - It creates a fake transaction output that is used to make work unique while giving miners complete control over the coinbase script's contents. It's scheduled to be removed soon, though, by putting the data back into the coinbase script.
February 11, 2012, 05:57:21 PM
Wait, aren't you the creator of that "P2POOL vs. Pooled Mining - something stinks here" thread...? You really are clueless.
February 11, 2012, 05:53:29 PM
P2Pool operates only in server mode. Forget you every read that post.
February 11, 2012, 05:01:41 PM
February 11, 2012, 04:11:34 PM
Right, the FROM MINER came before the SHARE, so my human grep capabilities have been proven to be lacking:
Still, I did match the share with the block, so maybe I get extra cookie points for that?
Code:
2012-02-09 17:27:28.021783 GOT BLOCK FROM MINER! Passing to bitcoind! bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
2012-02-09 17:27:28.024363 GOT SHARE! c fd031bab prev af58e024 age 5.44s
2012-02-09 17:27:28.035106 GOT BLOCK FROM PEER! Passing to bitcoind! fd031bab bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
Still, I did match the share with the block, so maybe I get extra cookie points for that?
February 11, 2012, 04:03:00 PM
just did a grep -E "BLOCK|SHARE" and...
I've been on this for a little less than a week at ~2GHs
Code:
2012-02-09 17:27:28.024363 GOT SHARE! c fd031bab prev af58e024 age 5.44s
2012-02-09 17:27:28.035106 GOT BLOCK FROM PEER! Passing to bitcoind! fd031bab bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
I've been on this for a little less than a week at ~2GHs
'GOT BLOCK FROM PEER' means someone else found a block and they are just telling your node about it.
'GOT BLOCK FROM MINER' means you found a block.
No, the fact that he got the matching share right before it would indicate that he solved it. P2Pool should have displayed "GOT BLOCK FROM MINER" right before the "GOT SHARE" line.. not sure why he didn't quote that.
February 11, 2012, 02:58:43 PM
just did a grep -E "BLOCK|SHARE" and...
I've been on this for a little less than a week at ~2GHs
Code:
2012-02-09 17:27:28.024363 GOT SHARE! c fd031bab prev af58e024 age 5.44s
2012-02-09 17:27:28.035106 GOT BLOCK FROM PEER! Passing to bitcoind! fd031bab bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
I've been on this for a little less than a week at ~2GHs
'GOT BLOCK FROM MINER' means you found a block.
'GOT BLOCK FROM PEER' by itself (without seeing the message above) means someone else found a block and they are just telling your node about it.
Edit: fixed
February 11, 2012, 02:50:33 PM
just did a grep -E "BLOCK|SHARE" and...
I've been on this for a little less than a week at ~2GHs
Code:
2012-02-09 17:27:28.024363 GOT SHARE! c fd031bab prev af58e024 age 5.44s
2012-02-09 17:27:28.035106 GOT BLOCK FROM PEER! Passing to bitcoind! fd031bab bitcoin: 6bdb99d5aab93a5cc5b36c427eb07657011f7354e92d81b47b1
I've been on this for a little less than a week at ~2GHs
February 11, 2012, 02:31:49 PM
So you regularly control+f through your entire log? 
I do a grep on the log once in a while FOR TEXT CONTAINING "BLOCK" IN CAPS.
I must also admit I am having a bit of a boring day and obsessing over Bitcoin has become a hobby on those days.
February 11, 2012, 02:24:55 PM
So you regularly control+f through your entire log?
February 11, 2012, 02:02:34 PM
Thanks, nice work.
But how do you know you found it?
But how do you know you found it?
Like this:
Code:
2012-02-11 13:30:33.492571 Pool: 218GH/s Stale rate: 8.9% Expected time to block: 7.5 hours
2012-02-11 13:30:33.869549
2012-02-11 13:30:33.869644 GOT BLOCK FROM MINER! Passing to bitcoind! bitcoin: 943404156a9980c3c6e49b0f3c712a4
c4673a6e8890edf9c13c
2012-02-11 13:30:33.869669
2012-02-11 13:30:33.870611 GOT SHARE! mafalda 603b0047 prev f6c85eff age 1.55s
2012-02-11 13:30:33.879298
2012-02-11 13:30:33.879354 GOT BLOCK FROM PEER! Passing to bitcoind! 603b0047 bitcoin: 943404156a9980c3c6e49b0
f3c712a4c4673a6e8890edf9c13c
2012-02-11 13:30:33.879378
2012-02-11 13:30:33.972340 New work for worker! Difficulty: 1.975760 Share difficulty: 468.473137 Total block
value: 50.044600 BTC including 90 transactions
2012-02-11 13:30:36.504443 P2Pool: 17447 shares in chain (17065 verified/17451 total) Peers: 13 (3 incoming)
Jump to: