[ANN] Noirbits TAKEOVER ! Update v2.2.5.0 - fixes sync issue

[stbgefltc]

Pushed new version 2.2.1.0.

This is a mandatory update for all users, get it ASAP (before height 33333).

This new version also makes refunds from UI : just right click on a transaction you received, you should have a "Return transaction" option available. The feature is only available for transactions you have received, and whose coins have not been spent yet. It is also available as an RPC call, you can get more details with the following command :

Code:

Noirbitsd help refundtransaction

[kalgecin]

Nice work mate  really appreciate the refunds  kinda needed them on more than one occasion 

[jasinlee]

That should help with keeping track of tx in the wallet.

[John122]

The block explorer just went offline. Let's hope it's upgrading to the latest version!

[feeleep]

mnrb.coinmine.pl - updated to latest version

[stbgefltc]

mnrb.coinmine.pl - updated to latest version

Great ! This should be the last mandatory update for a while... thanks for your reactivity.

The block explorer just went offline. Let's hope it's upgrading to the latest version!

Hopefully. I need to see what diatonic plans on doing... The block explorer has actually been offline for a few hours now...

[jasinlee]

Tested out refunds it works awesome!

[stbgefltc]

Updated first post with link to binaries for version 2.2.2.0.

This is a minor update that restores QR Code support for Windows binaries.

[MobGod]

been going crazy trying to get this chain it keep stopping at 25k not sure why
/Noirbitsd getinfo
{
    "version" : 2020100,
    "protocolversion" : 60002,
    "walletversion" : 60000,
    "balance" : 0.00000000,
    "blocks" : 25019,
    "connections" : 2,
    "proxy" : "",
    "difficulty" : 0.15711984,
    "testnet" : false,
    "keypoololdest" : 1376244053,
    "keypoolsize" : 101,
    "paytxfee" : 0.00000000,
    "mininput" : 0.00010000,
    "errors" : ""
}

[stbgefltc]

Investigating...

[jasinlee]

The previous version is fine until he gets the new one fixed. Or at least its synced up now.

[MobGod]

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

[jasinlee]

One of the nodes is submitting a bad block I guess.

[MobGod]

One of the nodes is submitting a bad block I guess.

Ok what node is that or maybe provide a node list to use?

[jasinlee]

Trying to isolate it now.

[oatmo]

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

[MobGod]

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
    },

[oatmo]

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

[barwizi]

maybe it's another case of sabotage,  if we can identify the rouge nodes, we can isolate and ban them.

[oatmo]

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" : ""
}