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

[3worlduser]

i think it has to do with the wallet, because even with your peer data i'm minting orphan, i'm trying now a trick, i'll synch with a fresh new wallet and then put mine back, let's see if it work

if the stakes were generated on another chain they will always show as orfans my wallet also is full of "orphans" due to the same problem

LoL I did the same "trick" when I saw the orphans LoL

[Nightz]

12:31:57

getblockhash 40680


12:31:57

a1967db4474804a29ff89213a11839496ce2796090df69b40bda699dba75661a

[Nightz]

I am counting the Chain me & the block ex are on as the main chain as I did a resync from scratch and the chains still match

so if block 40684 reports


12:36:12

getblockhash 40684


12:36:12

110bdb54341ac5743477e0e190b8354972fe8ec96c9873341bf82db0a8d7e8a8


You are on the main chain

[Nightz]

I seriously hope that we are not all on the main chain as what I've been working on well it will not be needed anymore. However saying that if we are all on the main chain then a fix will be a lot easier than performing a swap

Can everybody please post there getblockhash 40691


12:41:12

getblockhash 40691


12:41:12

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[3worlduser]

I am counting the Chain me & the block ex are on as the main chain as I did a resync from scratch and the chains still match

so if block 40684 reports


12:36:12

getblockhash 40684


12:36:12

110bdb54341ac5743477e0e190b8354972fe8ec96c9873341bf82db0a8d7e8a8


You are on the main chain

GREAT Aika pool is open for mining Loco and they are also on the explorer chain

[Nightz]

I seriously hope that we are not all on the main chain as what I've been working on well it will not be needed anymore. However saying that if we are all on the main chain then a fix will be a lot easier than performing a swap

Can everybody please post there getblockhash 40691


12:41:12

getblockhash 40691


12:41:12

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[USScrypto]

On the right chain here as well:

14:49:24

getblockhash 40691


14:49:24

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[bumbacoin]

woot
loco getblockhash 40691
acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

i was wondering if half the problem isn't the profligate use of
connect=x.x.x.x
where the wrong chain is held because the clients aren't listening

[Nightz]

woot
loco getblockhash 40691
acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

i was wondering if half the problem isn't the profligate use of
connect=x.x.x.x
where the wrong chain is held because the clients aren't listening

I too am beginning to wonder what is happening aswell, as it seems that most if not all are on the same chain as us, If that is the case then it is a lot easier to sort out the orphans than re doing the whole thing meaning no hassle with swaps and people sending coins here and there.

[GREEDYJOHN]

12:59:41

getblockhash 40691


12:59:41

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[ROBERTO]

14:01:38

getblockhash 40691


14:01:38

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[Nightz]

GOD DAMN IT it's looking like we are all on the same chain, so the fix would be to Ban those nodes/connections that are making people think we have forked

A SWAP MAY NOT BE NEEDED AFTER ALL

[bbr]

13:09:23

getblockhash 40691


13:09:23

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[Nightz]

ok so if everybody keeps reporting back the same hash as most have posted THE SWAP WILL BE CANCELLED and I will begin work on fixing the orphans mess

[bumbacoin]

getpeerinfo startingheight is annoying not quite useful enough.

it would be handy to be able to display peers bestblock as it is right now,
i seem to recall bitcoin had it way back but removed it for some reason ..


wow, i just did a quick restart and got loads of peers back very quickly

loco getpeerinfo | egrep "addr|starting"
        "addr" : "203.91.244.188:48528",
        "startingheight" : 34948,

        "addr" : "[2a01:e35:2423:7280:a0f9:6e66:89b5:acda]:64487",
        "startingheight" : 40744,

        "addr" : "87.159.253.23:62487",
        "startingheight" : 40744,

        "addr" : "93.86.119.180:49750",
        "startingheight" : 40744,

        "addr" : "82.199.107.147:39066",
        "startingheight" : 22984,

        "addr" : "198.50.229.39:34575",
        "startingheight" : 40744,

        "addr" : "82.66.55.40:64488",
        "startingheight" : 40744,

        "addr" : "84.234.52.190:35488",
        "startingheight" : 40744,

        "addr" : "176.131.119.177:52758",
        "startingheight" : 40744,

        "addr" : "94.34.193.212:56221",
        "startingheight" : 12945,

        "addr" : "109.172.53.97:52718",
        "startingheight" : 40744,

        "addr" : "[2003:7f:6e01:b900:2cfa:42a8:2fea:18c7]:62492",
        "startingheight" : 40744,

        "addr" : "213.202.214.140:51723",
        "startingheight" : 40744,

        "addr" : "[2607:5300:60:5e6e::3c5:64b2]:42017",
        "startingheight" : 40744,

        "addr" : "46.37.194.32:58593",
        "startingheight" : 39930,

        "addr" : "77.251.63.42:52830",
        "startingheight" : 32430,

        "addr" : "87.254.75.54:56042",
        "startingheight" : 40744,

        "addr" : "46.236.161.66:64134",
        "startingheight" : 40821,

        "addr" : "218.156.98.243:34575",
        "startingheight" : 40319,

        "addr" : "180.216.74.93:49697",
        "startingheight" : 40744,

        "addr" : "46.233.42.249:65121",
        "startingheight" : 40744,

        "addr" : "190.44.37.242:49875",
        "startingheight" : 40744,

        "addr" : "151.77.195.64:34575",
        "startingheight" : 40822,

        "addr" : "190.44.37.242:49879",
        "startingheight" : 40744,

        "addr" : "92.233.105.50:51610",
        "startingheight" : 40744,

        "addr" : "190.44.37.242:49882",
        "startingheight" : 40744,

        "addr" : "79.69.39.40:64173",
        "startingheight" : 40744,

        "addr" : "[2001:41d0:8:656c::]:34575",
        "startingheight" : 40744,

        "addr" : "88.215.150.2:54925",
        "startingheight" : 40744,

        "addr" : "95.25.210.103:34575",
        "startingheight" : 40744,

[3worlduser]

GOD DAMN IT it's looking like we are all on the same chain, so the fix would be to Ban those nodes/connections that are making people think we have forked

A SWAP MAY NOT BE NEEDED AFTER ALL

I spent the hole night looking the console I couldn't convince that the chain that we prepared yesterday was so fuck up + my daemon got attacked as I woke up it was down and I have never see that not even on VM with low resources

I set up like ten different wallet configurations and none of them connect to the "other" chain
the only way was with connect=x.x.x.x.
soy I took nigthz peer and reindex the block wallet and in other pc began to solo mine just 20 block after the chain begun to move normally
and the difficult went from 0.04 to 2.5 thats when Aika jump in i guess

now I have the head full of conspiracy theories

ooo
an tell this guys to update their wallets LoL

Code:

partner 81.0.115.32:52534 using obsolete version 61401; disconnecting
partner 222.94.209.98:34575 using obsolete version 61401; disconnecting
partner 101.175.180.227:64045 using obsolete version 61401; disconnecting
partner 78.61.222.172:53365 using obsolete version 61401; disconnecting
partner 222.94.209.98:54740 using obsolete version 61401; disconnecting
partner 176.195.13.159:65217 using obsolete version 61401; disconnecting
partner 78.61.222.172:53743 using obsolete version 61401; disconnecting
partner 79.235.245.225:56588 using obsolete version 61401; disconnecting

[shimlbit]

locod getblockhash 40691
acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

[Nightz]

GOD DAMN IT it's looking like we are all on the same chain, so the fix would be to Ban those nodes/connections that are making people think we have forked

A SWAP MAY NOT BE NEEDED AFTER ALL

I spent the hole night looking the console I couldn't convince that the chain that we prepared yesterday was so fuck up + my daemon got attacked as I woke up it was down and I have never see that not even on VM with low resources

I set up like ten different wallet configurations and none of them connect to the "other" chain
the only way was with connect=x.x.x.x.
soy I took nigthz peer and reindex the block wallet and in other pc began to solo mine just 20 block after the chain begun to move normally
and the difficult went from 0.04 to 2.5 thats when Aika jump in i guess

now I have the head full of conspiracy theories

ooo
an tell this guys to update their wallets LoL

Code:

partner 81.0.115.32:52534 using obsolete version 61401; disconnecting
partner 222.94.209.98:34575 using obsolete version 61401; disconnecting
partner 101.175.180.227:64045 using obsolete version 61401; disconnecting
partner 78.61.222.172:53365 using obsolete version 61401; disconnecting
partner 222.94.209.98:54740 using obsolete version 61401; disconnecting
partner 176.195.13.159:65217 using obsolete version 61401; disconnecting
partner 78.61.222.172:53743 using obsolete version 61401; disconnecting
partner 79.235.245.225:56588 using obsolete version 61401; disconnecting

No need I will change the noblks version and raise the peer proto version upwards as well as change the port number that way they have no choice to update

[Nightz]

SWAP IS CANCELLED

I will begin work on Changing noblks version, peer proto version, and the ports

[bumbacoin]

i think the code seems resilient enough to sort these forks out eventually (so far anyway).

it does not seem optimal for use though.
losing 700 or so blocks in a reorganise is problematic for any real use.

i'd say sort any code changes you want out, then see how the "current" chain is working out

or .. don't put the cart before the horse