Show Posts
Have the message start bits been changed from 1.8.0 to 1.8.5?
I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.
Ever since I upgraded to 1.8.5 I have not been able to connect.
I've just tried upgrading TreasureQuarry's P2Pool to 1.8.5 and have had the same problem...failure to connect between p2pool and Infinitecoind on 127.0.0.1:9321 I can't get P2Pool to connect to the P2P port of the client and this typically happens when the "magic bits" aren't correct.
Ever since I upgraded to 1.8.5 I have not been able to connect.
After some downtiime whilst the pool reloaded the blockchain for 1.8.5, I've had to put the pool back to version 1.8 now.
My best guess was that part of the new code is refusing connections from anything that it doesn't recognise as another version of Infinitecoin 1.8.5 . I see the following new code in main.cpp ...
Code:
// A check to make sure only the most recent versions of infinitecoin can connect
// this is a temporary hack for the time being and will be corrected in the next version
if( pfrom->strSubVer.find( "Satoshi:1.8" ) == std::string::npos )
{
printf("peer %s not using Infinitecoin, Client: %s Protocol %i; disconnecting\n", pfrom->addr.ToString().c_str(), pfrom->strSubVer.c_str(), pfrom->nVersion);
pfrom->Misbehaving(100);
pfrom->fDisconnect = true;
return false;
}
However, on reading through that code I'm not sure whether this has anything to do with it or not?
TECSHARE/uRrndUsr, could this be looked into, otherwise we may not be able to have any p2pools for IFC in future versions.
Sorry about this, I did not think about P2Pool when making this change. Either way it was needed to clear out non IFC clients.
I have you tried looking at the P2Pool code?
https://github.com/forrestv/p2pool/blob/master/p2pool/bitcoin/p2p.py#L35
https://github.com/forrestv/p2pool/blob/master/p2pool/p2p.py#L61
You could try forcing it to Satoshi:1.8.5, I am unsure if this would break p2pool in anyway tho.
