Pages:
Author

Topic: [ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue - page 12. (Read 24776 times)

legendary
Activity: 1008
Merit: 1022
Lol, pay me and ill fix it or at least have a look and tell you what's wrong
member
Activity: 85
Merit: 10
not sure if helpful but there is a faucet here  http://www.coinsforall.com/Freecoinfaucets/noirbitsfaucets.htm

I will also add the details for the coin to the site
hero member
Activity: 532
Merit: 500
Yup, sorry, was a bit tired yesterday, had a long day. The patch did not work out, so I need to investigate more on that specific, to see why it's getting rejected like that. Unfortunately, having a day job does not allow me to work on it all day long.
Does anyone have the chain working?
full member
Activity: 154
Merit: 100
Yup, sorry, was a bit tired yesterday, had a long day. The patch did not work out, so I need to investigate more on that specific, to see why it's getting rejected like that. Unfortunately, having a day job does not allow me to work on it all day long.
hero member
Activity: 532
Merit: 500
Just checking in to see if everything is ok
hero member
Activity: 532
Merit: 500
The issue might lie within the ComputeMinWork method. I've setup a patched test node, I am unfortunately away for the day, so I'll check out the results tonight. If it works out, I'll push the patch and recompiled binaries ASAP.
any luck ??

I'll be home in a couple hours (9pm cest), so can't tell you yet.
ok thanks
full member
Activity: 154
Merit: 100
The issue might lie within the ComputeMinWork method. I've setup a patched test node, I am unfortunately away for the day, so I'll check out the results tonight. If it works out, I'll push the patch and recompiled binaries ASAP.
any luck ??

I'll be home in a couple hours (9pm cest), so can't tell you yet.
hero member
Activity: 532
Merit: 500
The issue might lie within the ComputeMinWork method. I've setup a patched test node, I am unfortunately away for the day, so I'll check out the results tonight. If it works out, I'll push the patch and recompiled binaries ASAP.
any luck ??
full member
Activity: 154
Merit: 100
The issue might lie within the ComputeMinWork method. I've setup a patched test node, I am unfortunately away for the day, so I'll check out the results tonight. If it works out, I'll push the patch and recompiled binaries ASAP.
hero member
Activity: 532
Merit: 500
I deleted the block database, and now I'm stuck in the same place..

{
"version" : 2020100,
"protocolversion" : 60002,
"walletversion" : 60000,
"balance" : 7657.69043275,
"blocks" : 25019,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.15711984,
"testnet" : false,
"keypoololdest" : 1371618202,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}

This is crazy maybe they are working on a fix, I hope
member
Activity: 104
Merit: 10
I deleted the block database, and now I'm stuck in the same place..

{
"version" : 2020100,
"protocolversion" : 60002,
"walletversion" : 60000,
"balance" : 7657.69043275,
"blocks" : 25019,
"connections" : 2,
"proxy" : "",
"difficulty" : 0.15711984,
"testnet" : false,
"keypoololdest" : 1371618202,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00010000,
"errors" : ""
}
legendary
Activity: 882
Merit: 1000
maybe it's another case of sabotage,  if we can identify the rouge nodes, we can isolate and ban them.
member
Activity: 104
Merit: 10
This don't seem right to me either

"addr" : "72.78.100.7:55884",
        "services" : "00000001",
        "lastsend" : 1376272686,
        "lastrecv" : 1376272686,
        "conntime" : 1376272686,
        "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
    },

I'm stuck on the same..
hero member
Activity: 532
Merit: 500
This don't seem right to me either

"addr" : "72.78.100.7:55884",
        "services" : "00000001",
        "lastsend" : 1376272686,
        "lastrecv" : 1376272686,
        "conntime" : 1376272686,
        "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
    },
member
Activity: 104
Merit: 10
Sorry, was on the other thread. Just read up.

I'm in with stbgfltc. He's been doing the coding. Most of the rest of us have just been giving advice, so I'm happy to see the support. I don't think this is a big problem. I'm sorry that I'm not contributing more, but I have too many current projects.. hopefully in a month or two, I can support the coin more.

I'm stuck on block 30105 with the new client. Where are there directions on how to setup the config file with the addnode command so that I can hopefully get started again?

Posted in the other thread about the retarget algorithm. I'll repost that here is a few minutes.

Oatmo
hero member
Activity: 742
Merit: 500
Its as easy as 0, 1, 1, 2, 3
Trying to isolate it now.
hero member
Activity: 532
Merit: 500
One of the nodes is submitting a bad block I guess.
Ok what node is that or maybe provide a node list to use?
hero member
Activity: 742
Merit: 500
Its as easy as 0, 1, 1, 2, 3
One of the nodes is submitting a bad block I guess.
hero member
Activity: 532
Merit: 500
The previous version is fine until he gets the new one fixed. Or at least its synced up now.
I've tried both githubs same thing
hero member
Activity: 742
Merit: 500
Its as easy as 0, 1, 1, 2, 3
The previous version is fine until he gets the new one fixed. Or at least its synced up now.
Pages:
Jump to: