Quote from: fronti on May 16, 2013, 08:48:07 AM

not sure if this is normal, as I'm not that familar with p2pool right now:

Code:

utgoing connection to peer 91.235.254.37:9355 established. p2pool version: 1100 'b2de428-dirty'
2013-05-16 10:45:21.310680 Sending 1 shares to 91.235.254.37:9355
2013-05-16 10:45:21.364218 Peer sent entire transaction d569d639cecd98d005c22dc854f2eea8be35ab5c7c6c66dae82338cf136c0afe that was already received
2013-05-16 10:45:21.375079 Lost peer 91.235.254.37:9355 - Connection was closed cleanly.
2013-05-16 10:45:21.375517 > in handle_share_hashes:
2013-05-16 10:45:21.375557 > Traceback (most recent call last):
2013-05-16 10:45:21.375591 > Failure: twisted.internet.error.ConnectionDone: Connection was closed cleanly.

this comes around every 5 seconds..

and another question:
if I run on a windwos host a miner minerd_scrypt_jane_x64 i got this:

Code:

Worker a submitted share with hash > target:
2013-05-16 10:47:14.835635 Hash: 3cdb25c5746ad9ff4a5002b135160be5a0351dc07b9c62bbe853364b20b4f9e8
2013-05-16 10:47:14.835676 Target: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

is this OK?

NO, it's a bug.
The lastest protocol conflicts with the former one, that's why I changed the server to the new version, and changed back again.
We must use a new port and a new protocol prefix. I have update the source on github a moment ago. Please download the newest one.
https://github.com/cctvsmg/yacoin-p2pool

the newest version use a port 8338 like:
http://pool.bitcn.org:8338