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

[cabin]

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,

[1714201304]

1714201304

[1714201304]

1714201304

[1714201304]

1714201304

[1714201304]

1714201304

[1714201304]

1714201304

[Tittiez]

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,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

[wachtwoord]

You can also specify a bitcoin address which is not part of the wallet of the bitcoind (or bitcoin-qt) which is currently running. I set it up this way after I got advise in the IRC channel that this is more secure (which I agree with).

[cabin]

Well actually each p2p block has hundreds of payout addresses, but you're right it is solo mining. My concern was if one funny payout address could drastically slow down confirmation of a found block and therefore result in a p2pool block being orphaned. For example if only 5% of the network supported P2SH addresses, and the p2pool payout list includes a P2SH-style address, then p2pool blocks would be very slow to transmit through the network.

I suspect it is nothing to worry about and that I'm missing something.. but I just wanted to bring up the possibility in case it is a potential bug/problem.

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,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

[kano]

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,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

Ummmm? Eh?
It goes to all the N addresses listed in the share chain - the coinbase txn lists all those addresses.


Aside ... so as mentioned above ... could someone stop every block from being accepted by putting crap addresses in the share chain?
Hope that problem doesn't exist or has been already dealt with if it did exist.

[Tittiez]

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,

Your solo mining, remember that. Therefor there is no payout address, but instead it goes directly into bitcoind.

Ummmm? Eh?
It goes to all the N addresses listed in the share chain - the coinbase txn lists all those addresses.


Aside ... so as mentioned above ... could someone stop every block from being accepted by putting crap addresses in the share chain?
Hope that problem doesn't exist or has been already dealt with if it did exist.

I meant at least in our prospective. My payouts show as "Mined" in the bitcoin client.

[twmz]

I meant at least in our prospective. My payouts show as "Mined" in the bitcoin client.

Yes, but that is just a "bug" in the bitcoin client.  The actual generation transaction does include your address.  The client just doesn't show it to you.

[thirdlight]

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.

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...

[Red Emerald]

So I have p2pool running on an ubuntu server with python 2.7.

I wanted to setup a backup pool and so I installed everything on a debian server.  If I specify all of the command line options, it starts fine.  But "--help" gives an error.

Code:

[user@p2pool p2pool]$ ./run_p2pool.py --help
Install SciPy for more accurate confidence intervals!
/home/user/src/p2pool/p2pool/util/pack.py:191: DeprecationWarning: object.__new__() takes no parameters
  return Type.__new__(cls, bits, endianness)
Traceback (most recent call last):
  File "./run_p2pool.py", line 5, in <module>
    main.run()
  File "/home/user/src/p2pool/p2pool/main.py", line 1041, in run
    args = parser.parse_args()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1698, in parse_args
    args, argv = self.parse_known_args(args, namespace)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1730, in parse_known_args
    return self._parse_known_args(args, namespace)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1932, in _parse_known_args
    start_index = consume_optional(start_index)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1872, in consume_optional
    take_action(action, args, option_string)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1800, in take_action
    action(self, namespace, argument_values, option_string)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 1023, in __call__
    parser.print_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 2319, in print_help
    self._print_message(self.format_help(), file)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 2293, in format_help
    return formatter.format_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 314, in format_help
    help = self._root_section.format_help()
  File "/usr/lib/pymodules/python2.6/argparse.py", line 244, in format_help
    func(*args)
  File "/usr/lib/pymodules/python2.6/argparse.py", line 365, in _format_usage
    assert ' '.join(opt_parts) == opt_usage
AssertionError
[user@p2pool p2pool]$ python -V
Python 2.6.6
[user@p2pool p2pool]$ lsb_release -a
No LSB modules are available.
Distributor ID: Debian
Description:    Debian GNU/Linux 6.0.4 (squeeze)
Release:        6.0.4
Codename:       squeeze

[forrestv]

I wanted to setup a backup pool and so I installed everything on a debian server.  If I specify all of the command line options, it starts fine.  But "--help" gives an error.

Fixed, thanks for pointing that out.

[jothan]

Yay, I found my first block ever, just now, while participating in P2Pool. It took over 2 months at ~1710 Mhash/s.

Glad to see my mining rig can actually mine a full block

https://blockchain.info/block-index/867562/0000000000000943404156a9980c3c6e49b0f3c712a4c4673a6e8890edf9c13c

[Ente]

It gets more and more strange..

Rig "Miner04" uses forrestv-p2pool-0.8.4-1-gadba786
Rig "Miner03" uses forrestv-p2pool-release-0.8.1-0-gc7feb00

Rig "Miner04" uses Guiminer v2011-06-14
Rig "Miner03" uses Guiminer v2011-06-14

Guiminer "Miner03" --> p2pool "Miner03": finds "minerblocks" and "shareblocks"
Guiminer "Miner04" --> p2pool "Miner04": drops "unexpected error:" in guiminer
Guiminer "Miner03" --> p2pool "Miner04": finds "minerblocks" with 100% in (), finds "shareblocks"
Guiminer "Miner04" --> p2pool "Miner03": finds "minerblocks" with 50% in (), finds no "shareblocks"

So obviously its some problem on Guiminer's (or poclbm) side on "Miner04".

In Guiminer you see for example:

Accepted: 471 (256)
Stale: 0 (0)

I didnt find out what the number in () means, yet.

All other rigs are like "Miner03" and behave well.

Bah, I'm losing my patience with this windows stuff..

Ente

edits underlined

Ok, its quite clear now that its a problem on the Guiminer (or poclbm) side.
Will try to solve that and update all p2pool instances to the "forrestv-p2pool-0.8.4-1-gadba786" version too.

Thank you for your help!

Ente

[wachtwoord]

Thanks, nice work.

But  how do you know you found it?

[jothan]

Thanks, nice work.

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)

[wachtwoord]

So you regularly control+f through your entire log? 

[jothan]

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.

[nelisky]

just did a grep -E "BLOCK|SHARE" and...

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

[twmz]

just did a grep -E "BLOCK|SHARE" and...

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

[forrestv]

just did a grep -E "BLOCK|SHARE" and...

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.

[nelisky]

Right, the FROM MINER came before the SHARE, so my human grep capabilities have been proven to be lacking:

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?