hmm.... can you provide last 100 lines of debug.log please?
When I get home yes I will 
Topic: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue - page 11. (Read 24776 times)
hmm.... can you provide last 100 lines of debug.log please?
Ok looks like its on the git, anyone able to compile it for windows too?
what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck I've fixed that
./Noirbitsd getinfo
{
"version" : 2020300,
"protocolversion" : 60002,
"walletversion" : 60000,
"balance" : 0.00000000,
"blocks" : 29069,
"connections" : 1,
"proxy" : "",
"difficulty" : 1.48791009,
"testnet" : false,
"keypoololdest" : 1376244053,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
Ok looks like its on the git, anyone able to compile it for windows too?
what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck I've fixed that
Ok looks like its on the git, anyone able to compile it for windows too?
what do you mean on the git want me to try this again i didn't have a problem with the compile i had the problem with the chain getting stuck 
Ok looks like its on the git, anyone able to compile it for windows too?
a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.
The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.
competition? testnet for testing new ideas? huh?
a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.
The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.
Not sure what this peer is doing - looks like it could be causing issues though
{
"addr" : "72.78.100.7:55884",
"services" : "00000001",
"lastsend" : 1376409243,
"lastrecv" : 1376409243,
"conntime" : 1376407441,
"version" : 60001,
"subver" : "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
Quote
{
"addr" : "72.78.100.7:55884",
"services" : "00000001",
"lastsend" : 1376409243,
"lastrecv" : 1376409243,
"conntime" : 1376407441,
"version" : 60001,
"subver" : "\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000",
"inbound" : false,
"releasetime" : 0,
"startingheight" : -1,
"banscore" : 0
}
Lol, pay me and ill fix it or at least have a look and tell you what's wrong
500 NRB if you find the issue before I do. Winner will be settled by pull request time on Noirbits repository (or commit time of fix).
Lets hardcode that code as accepted and move into the fun parts.
a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.
The issue has nothing to do with a rogue node. Even when syncing with known, proper nodes, the issue arises.
a temporary fix, would be to limit the client to a few, only the good nodes until an update that completely cuts them off is pushed.
Noirbits has just added the only new feature to QT I have seen in a while on any alt so lets just give him some time to correct it, this is already getting innovative.
I'm giving it time but there has to be good nodes people are using if only a couple of people are having this issue correct?Yes, nodes who have the full blockchain don't have the issue. It seems to occur when redownloading it, which means it's probably been here for a while, but went unnoticed until the forks that required to redownload the blockchain.
Noirbits has just added the only new feature to QT I have seen in a while on any alt so lets just give him some time to correct it, this is already getting innovative.
I'm giving it time but there has to be good nodes people are using if only a couple of people are having this issue correct?
Noirbits has just added the only new feature to QT I have seen in a while on any alt so lets just give him some time to correct it, this is already getting innovative.
Lol, pay me and ill fix it or at least have a look and tell you what's wrong
Can't you just look 
there is a rouge peer somewhere that is causing the issue. I'll look into it. But i'm sure stbgefltc already has an idea.
Ok if that's the case can you give me a node that's on the right chain, that way I can connect to that node only and see if it works?
there is a rouge peer somewhere that is causing the issue. I'll look into it. But i'm sure stbgefltc already has an idea.
here ill do it for free, noirbits has gone, sell me all your coins at 0.00000000001 ltc
Jump to: