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

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: 3worlduser on May 03, 2016, 07:42:11 AM

Nigthz I want to get out of your proyect Undecided

what do you want me to do withe explorer,faucet, etc.

Close em mate that simple and whatever funds you have donate to somebody Wink

I can get a block ex up etc

3worlduser

sr. member

Activity: 306

Merit: 250

Nigthz I want to get out of your proyect Undecided

what do you want me to do withe explorer,faucet, etc.

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: ?? on ??

Quote from: bumbacoin on May 03, 2016, 07:21:30 AM

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 Cheesy

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

a hint.
once suprnova or another pool kicks in and have most of pow in one client,
those pos blocks will start to get orphaned again, new forks, and new problems

you get orphans on all coins mate especially pow/pos hybrid ones it is to be expected.

hint.
I thought you was done with Loco yet your still here Roll Eyes

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: bbr on May 03, 2016, 07:36:08 AM

Quote from: Nightz on May 02, 2016, 02:08:29 AM

Quote from: Amph on May 02, 2016, 02:05:45 AM

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Please could you also fix this issue?

will do, I have change the noblks version, peer version and port numbers along with the orphans to be kept in memory Wink

Should get us back on track

bbr

sr. member

Activity: 290

Merit: 250

Quote from: Nightz on May 02, 2016, 02:08:29 AM

Quote from: Amph on May 02, 2016, 02:05:45 AM

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Please could you also fix this issue?

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: bumbacoin on May 03, 2016, 07:21:30 AM

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 Cheesy

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

Will do mate Wink

and already on it.

the reorganise bit could be bad but thankfully Loco is still in it's early stages so by the time I hope to have more people using it that should not become a factor anymore

bumbacoin

legendary

Activity: 1638

Merit: 1036

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 Cheesy

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

Nightz

hero member

Activity: 1316

Merit: 504

SWAP IS CANCELLED

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

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: 3worlduser on May 03, 2016, 07:14:52 AM

Quote from: Nightz on May 03, 2016, 07:03:13 AM

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

shimlbit

legendary

Activity: 1302

Merit: 1001

locod getblockhash 40691
acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

3worlduser

sr. member

Activity: 306

Merit: 250

Quote from: Nightz on May 03, 2016, 07:03:13 AM

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

bumbacoin

legendary

Activity: 1638

Merit: 1036

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,

Nightz

hero member

Activity: 1316

Merit: 504

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 Wink

bbr

sr. member

Activity: 290

Merit: 250

13:09:23

getblockhash 40691

13:09:23

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

Nightz

hero member

Activity: 1316

Merit: 504

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

ROBERTO

legendary

Activity: 1421

Merit: 1001

14:01:38

getblockhash 40691

14:01:38

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

GREEDYJOHN

legendary

Activity: 1778

Merit: 1000

12:59:41

getblockhash 40691

12:59:41

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

Nightz

hero member

Activity: 1316

Merit: 504

Quote from: bumbacoin on May 03, 2016, 06:52:50 AM

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.

bumbacoin

legendary

Activity: 1638

Merit: 1036

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

USScrypto

hero member

Activity: 602

Merit: 500

On the right chain here as well:

14:49:24

getblockhash 40691

14:49:24

acf0ef70f1fa42eb7d5177b23aa28a911e346921a05ba3db8424a35e24e7ab7b

Topic: [ANN][LOC]UPDATE V1.4.5 OUT!! LOCO|Quark|PoW/PoS|HiPos|Masternodes|Tor[LOC][ANN] - page 38. (Read 88723 times)