[ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN]

[Nightz]

WOW   does your debug.log look different to mine I have nowhere near that amount of orphans reported back on my debug.log But again I will look into it today

of course it may look different if you were synced already.
that flood goes when wallet comes into network at an earlier block,
and instead of syncing quietly it gets this punishment,
the higher the block the more dense is this shit

I purposely deleted the chain yesterday as I'm messing with the code for syncing to get it synchronized faster and I had to resync the whole chain again and it still does not report back all of those like yours does

resync when exactly ? yesterday it was ok

P.S.
if you wanna see that bloody shit in action vividly
dl AMS wallet and try to sync it up to block say 50k

I will not waste my time on AMS and I will delete the chain right now and sync again if needed mate. I get nowhere near the amount you do.

[novaexchange]

locod getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560


thats what i got after resync

That is the same chain as Novaexchange,

loco@ws03:~$ coind getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

----

Everyone else, remove your chain and sync your wallet to this so far untainted wallet. It is in sync with the explorer and most of the other clients.

connect=node03.novaexchange.com:8057
listen=0

If you are in sync already use Novaexchange to stay in sync. The more nodes we get together the stronger the chain, I am allowing 250 connections.

addnode=node03.novaexchange.com:8057

[Nightz]

Wallet has 27 Connections

[novaexchange]

Wallet has 27 Connections

@Nightz,
Give me your IP, will add it to the nodes to be connected to when starting.

[3worlduser]

locod getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560


thats what i got after resync

That is the same chain as Novaexchange,

loco@ws03:~$ coind getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

----

Everyone else, remove your chain and sync your wallet to this so far untainted wallet. It is in sync with the explorer and most of the other clients.

connect=node03.novaexchange.com:8057
listen=0

If you are in sync already use Novaexchange to stay in sync. The more nodes we get together the stronger the chain, I am allowing 250 connections.

addnode=node03.novaexchange.com:8057

Code:

connect=node03.novaexchange.com:8057
listen=0

didn't worked for me but

Code:

connect=198.50.229.39
listen=0

did the trick, is the ip of the block explorer as it seem we both have the same chain because when I resync I used only the nodes on you page 

[novaexchange]

Code:

connect=node03.novaexchange.com:8057
listen=0

didn't worked for me but

Code:

connect=198.50.229.39
listen=0

did the trick, is the ip of the block explorer as it seem we both have the same chain because when I resync I used only the nodes on you page 

I have 122 connections to the wallet right now. ;-)

[3worlduser]

Code:

connect=node03.novaexchange.com:8057
listen=0

didn't worked for me but

Code:

connect=198.50.229.39
listen=0

did the trick, is the ip of the block explorer as it seem we both have the same chain because when I resync I used only the nodes on you page 

I have 122 connections to the wallet right now. ;-)

why I couln't connect  , i want to have your blockchain I'll try again later

[novaexchange]

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

[novaexchange]

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

interesting, you have suprnova faulty on default port
37.59.18.108:34575 failed after select
and i have suprnova clean and healthy on another
37.59.18.108:41160

Those lines is not what is intresting, thats probably because his connection pool is full. Though those partner messages are the intresting ones, the log is full of those.

[3worlduser]

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this 

[pineapples]

I had a bunch of stakes, they were all lost in another fork being reorganised, seems I lost about 302 blocks in that particular lot.

Novaexchange, perhaps you should set confirmations to 500

[Nightz]

A lot of people is still running old wallet,.

Code:

2016-05-02 08:56:17 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:21 partner 101.175.180.227:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:21 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:21 connect() to 46.226.186.70:34575 failed after select(): No route to host
2016-05-02 08:56:28 partner 176.193.213.25:52496 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 95 bytes) FAILED
2016-05-02 08:56:28 partner 75.85.20.118:34575 using obsolete version 61401; disconnecting
2016-05-02 08:56:28 ProcessMessage(version, 96 bytes) FAILED
2016-05-02 08:56:28 connect() to 37.59.18.108:34575 failed after select(): Connection refused
2016-05-02 08:56:31 partner 79.235.235.133:52173 using obsolete version 61401; disconnecting
2016-05-02 08:56:31 ProcessMessage(version, 95 bytes) FAILED

interesting, you have suprnova faulty on default port
37.59.18.108:34575 failed after select
and i have suprnova clean and healthy on another
37.59.18.108:41160

Those lines is not what is intresting, thats probably because his connection pool is full. Though those partner messages are the intresting ones, the log is full of those.

The partner messages are telling you that people are trying to connect etc to you but they are no longer able to due to them not updating as they should of

[Nightz]

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this 

Try this, It's my chain the correct one too https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

[Nightz]

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this  

yeah, that's how it makes orphans, and other wallets the same way,
and it will make tons of them until chain gets completely overloaded.
it's all over again, nothing new.
perhaps side effect of limiting orphans mempool to 200 speeds up the process,
otherwise you would notice it much later

Mate if you wish to leave that is your choice but I can say with Certainty all will be sorted and bettered. Take that how you will

Thanks

[Nightz]

Mate if you wish to leave that is your choice but I can say with Certainty all will be sorted and bettered. Take that how you will

Thanks

already done, will delete completely in 30 min, sorry i'm certain you won't

LMAO do not under estimate me  Will be a not very wise move mate 

[novaexchange]

I have temporarely increased confirmations needed to 800 on Novaexchange (just to be sure), this will be lowered down again to 10 once this has been sorted out.

However, I have not received even one orphan just yet. It seems like my client is very stable together with the explorers, i am keeping a sharp eye to events around loco at this point.

[bbr]

I'm confused...which is now the correct chain?

When I look at block 39327 I get b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08 (which matches the explorer).

This is after downloading Nightz chain but when I look at previous posts they are stating that the correct hash for this block is f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

[3worlduser]

mmm and now my wallet travels trough time stake a block get confirmed even in de blockexplorer and then my wallet say I'm 2 hours behind
resync in 3 second and everything is back to my wallet before the stake with a nice stake block with 200 confirmation that the next minute becomes "in conflict" i wait five minutes and the stake begins again. now it goes for the 9 cycle doing this 

Try this, It's my chain the correct one too https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

Contains
peers.dat
blk0001.dat
txleveldb folder

LoL why don't we did this in the update

Code:

connect=Nightz_wallet
listen=0

would have save a lot of problems, in fact I'm gona need to do that because the chain in the explorer is a little "weird"
I'll be playing with these thing now

[GREEDYJOHN]

12:04:24

getinfo


12:04:24

{
"version" : "v1.3.0.0-Alpha",
"protocolversion" : 70002,
"walletversion" : 60000,
"balance" : xxxxxxxx,
"newmint" : 0.00000000,
"stake" : xxxxxxxx,
"blocks" : 39569,
"timeoffset" : 2,
"moneysupply" : 1850311.73066100,
"connections" : 22,
"proxy" : "",
"ip" : "0.0.0.0",
"difficulty" : {
"proof-of-work" : xxxxxxx
"proof-of-stake" : xxxxxxx
},
"testnet" : false,
"keypoololdest" : 1460750870,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"mininput" : 0.00000000,
"unlocked_until" : 0,
"errors" : ""
}

[Nightz]

I'm confused...which is now the correct chain?

When I look at block 39327 I get b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08 (which matches the explorer).

This is after downloading Nightz chain but when I look at previous posts they are stating that the correct hash for this block is f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560

If you downloaded my chain mate it also reports back

b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08


12:24:17

getblockhash 39327


12:24:17

b4b5eb074c20b1b483d7620ad22519497027c32ca34c7639f4329f4ecf771f08