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

[3worlduser]

bumbacoin, then the explorer is in the right chain?

[bumbacoin]

bumbacoin, then the explorer is in the right chain?

i dont' think so.
it doesnt match the hashes other people posted.

(my problem above is i was on the apparently incorrect fork, and the source i am compiling from has incorrect checkpoints so won't sync past block 27494)



apparently correct
getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2


explorer
  "hash": "080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4",
  "confirmations": 409,
  "size": 400,
  "height": 38431,

[3worlduser]

bumbacoin, then the explorer is in the right chain?

i dont' think so.
it doesnt match the hashes other people posted.

(my problem above is the source i am compiling from has incorrect checkpoints so won't sync past block 27494)



apparently correct
getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2


explorer
  "hash": "080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4",
  "confirmations": 409,
  "size": 400,
  "height": 38431,

My windows wallet

Code:

22:06:36

getblockhash 38431


22:06:36

080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

these are wallets Go2:1.3.0 and the block explorer daemon was compiled just after the release of the update.
mmmmm how to know the right chain then

[bumbacoin]

well it seems that the explorer does not match the earlier info from nightz

Code:

  // ensure links on API page are valid
  "api": {
    "blockindex": 38289,
    "blockhash": "768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5",
    "txhash": "31d1d24f3efd2a610e26f39a15daf787b091d6d56bb785160474ce3c42e458d9",
    "address": "68dmHTnpsrhCRACZ6MUFMymSho9G9PWjqU"

vs explorer with

  "hash": "6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7",
  "confirmations": 615,
  "size": 444,
  "height": 38289,


so i assume that suggests the other blockhash posted is more correct.
i'm not even up to that block yet ,

when i do i will post to confirm

currently i'm syncing using
connect
to the longer peers

EDIT
hang on, i just re-read, that's not the correct hash that i've crossed out  is it

lol
haha oh well i'll worry about it when i sync more

[bumbacoin]

FURTHER TO THE ABOVE POST

ok. that hash actually looks correct.
i've just passed that block and share the same hashes

loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2

[3worlduser]

well it seems that the explorer does not match the earlier info from nightz


  // ensure links on API page are valid
  "api": {
    "blockindex": 38289,
    "blockhash": "768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5",
    "txhash": "31d1d24f3efd2a610e26f39a15daf787b091d6d56bb785160474ce3c42e458d9",
    "address": "68dmHTnpsrhCRACZ6MUFMymSho9G9PWjqU"



vs explorer with

  "hash": "6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7",
  "confirmations": 615,
  "size": 444,
  "height": 38289,


so i assume that suggests the other blockhash posted is more correct.
i'm not even up to that block yet ,

when i do i will post to confirm

currently i'm syncing using
connect
to the longer peers

EDIT
hang on, i just re-read, that's not the correct hash that i've crossed out  is it

lol
haha oh well i'll worry about it when i sync more

those numbers where posted by me Nightz was teaching me how to get them

look

locod getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2

updated...is this the right chain?

wallet

 "subver" : "/Go2:1.3.0/",

16:20:44

getblockhash 38431


16:20:44

056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2


It seems we are in the correct chain

and now in the same windows wallet

Code:

22:41:34

getblockhash 38431


22:41:34

080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

[3worlduser]

FURTHER TO THE ABOVE POST

ok. that hash actually looks correct.
i've just passed that block and share the same hashes

loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2

Code:

22:44:31

getblockhash 38289


22:44:31

6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7


22:48:21

getblockhash 38431


22:48:21

080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

it seems like my wallets forked

[bumbacoin]

FURTHER TO THE ABOVE POST

ok. that hash actually looks correct.
i've just passed that block and share the same hashes

loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2

omg and stuff

those above, i used
connect=212.85.91.20

then i removed that restarted. and looks like the wallet "fixed itself"

now i get..

root@vps:~/.loco# loco getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7
root@vps:~/.loco# loco getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

lmao

[3worlduser]

FURTHER TO THE ABOVE POST

ok. that hash actually looks correct.
i've just passed that block and share the same hashes

loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2

omg and stuff

those above, i used
connect=212.85.91.20

then i removed that restarted. and looks like the wallet "fixed itself"

now i get..

root@vps:~/.loco# loco getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7
root@vps:~/.loco# loco getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

lmao

So we can say that we are on the right chain?

[bumbacoin]

looks like it forked at #38166

REORGANIZE: Disconnect 720 blocks; 648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720..eec3e771a5646 1990eeac9df4d179f68ccd98126aefedf581271c$
REORGANIZE: Connect 160 blocks; 648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720..15295e0c39511 c7acb2250aa2c0fb4bdee55b4e201a0c77a4c6dc319$

http://198.50.229.39:3001/block/648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720



-- the right chain ??

i give up
no idea.

it does seem that nightz posted the different hash for..
edit (ok. maybe he just agreed with the hash.. it's not entirely clear tbh)

ensure links on API page are valid
  "api": {
    "blockindex": 38289,
    "blockhash": "768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5",
    "txhash": "31d1d24f3efd2a610e26f39a15daf787b091d6d56bb785160474ce3c42e458d9",
    "address": "68dmHTnpsrhCRACZ6MUFMymSho9G9PWjqU"


i've got other stuff to do so i'll come back later and see what other thoughts are.

[3worlduser]

looks like it forked at #38166

REORGANIZE: Disconnect 720 blocks; 648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720..eec3e771a5646 1990eeac9df4d179f68ccd98126aefedf581271c$
REORGANIZE: Connect 160 blocks; 648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720..15295e0c39511 c7acb2250aa2c0fb4bdee55b4e201a0c77a4c6dc319$

http://198.50.229.39:3001/block/648d9ec26a94cd40bda5ab76e99fed40370a637da978ffbae0240c0526361720



-- the right chain ??

i give up
no idea.

it does seem that nightz posted the different hash for..

ensure links on API page are valid
  "api": {
    "blockindex": 38289,
    "blockhash": "768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5",
    "txhash": "31d1d24f3efd2a610e26f39a15daf787b091d6d56bb785160474ce3c42e458d9",
    "address": "68dmHTnpsrhCRACZ6MUFMymSho9G9PWjqU"


i've got other stuff to do so i'll come back later and see what other thoughts are.

maybe we will go multichain, LoL anyway those number were posted by me, I will recalculate and resync later maybe there are more ideas here by then

[bumbacoin]

        "addr" : "188.33.82.204:57424",
        "startingheight" : 2123,
        "addr" : "104.207.133.150:44170",
        "startingheight" : 39060,
       "addr" : "196.210.72.59:55389",
        "startingheight" : 38897,
        "addr" : "151.77.195.64:61885",
        "startingheight" : 39060,
        "addr" : "93.86.119.180:50418",
        "startingheight" : 38746,
        "addr" : "46.233.42.249:34575",
        "startingheight" : 39060,
        "addr" : "176.36.240.68:34575",
        "startingheight" : 27159,
        "addr" : "198.50.229.39:34575",
        "startingheight" : 39060,
        "addr" : "77.28.58.168:53447",
        "startingheight" : 39060,
        "addr" : "[2001:41d0:8:656c::]:46556",
        "startingheight" : 39060,
       "addr" : "212.85.91.20:34575",
        "startingheight" : 38897,
        "addr" : "46.236.161.66:34575",
        "startingheight" : 10968,
        "addr" : "88.206.187.247:33767",
        "startingheight" : 39061,
        "addr" : "46.37.194.32:49782",
        "startingheight" : 39061,
        "addr" : "197.89.176.121:59469",
        "startingheight" : 39061,
        "addr" : "68.185.188.91:62738",
        "startingheight" : 20109,
        "addr" : "[2601:47:4202:5d50:753a:cea3:69f7:3695]:65050",
        "startingheight" : 39061,
        "addr" : "37.59.18.108:40030",
        "startingheight" : 39061,
        "addr" : "45.63.1.27:55274",
        "startingheight" : 39061,
        "addr" : "50.191.30.64:65056",
        "startingheight" : 39061,
        "addr" : "92.233.105.50:56414",
        "startingheight" : 39061,
        "addr" : "77.251.63.42:34575",
        "startingheight" : 7319,
        "addr" : "[2001:19f0:0:208c:7090:b8d0:7489:1b67]:57344",
        "startingheight" : 39061,
        "addr" : "213.202.214.140:34575",
        "startingheight" : 39061,
        "addr" : "[2a01:e35:2423:7280:a0f9:6e66:89b5:acda]:50235",
        "startingheight" : 39063,
        "addr" : "84.234.52.190:45476",
        "startingheight" : 39064,
       "addr" : "79.69.39.40:63872",
        "startingheight" : 38897,
        "addr" : "[2607:5300:60:5e6e::3c5:64b2]:34575",
        "startingheight" : 39066,
        "addr" : "[2002:b024:f044::b024:f044]:54265",
        "startingheight" : 27318,
       "addr" : "81.162.199.253:2257",
        "startingheight" : 38897,
        "addr" : "180.216.71.145:49775",
        "startingheight" : 39074,
        "addr" : "203.91.244.188:52552",
        "startingheight" : 39077,
        "addr" : "190.44.37.242:6099",
        "startingheight" : 23459,
        "addr" : "82.66.55.40:50588",
        "startingheight" : 39082,


it certainly seems that the vast majority of my peers are in agreeance with the xplorer.

root@vps:~/.loco# loco getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7
root@vps:~/.loco# loco getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4


only 4 or so seem on the fork featuring the hashes as featured by other users featured in bold


loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2


--
i have synced twice to the other chain, and both times it's re-organised.
i'm curious as to who was on the other chain and has also reorganised

[bumbacoin]

also here is the correct mac qt compile Loco-Qt-OSX-v1300-Go2
i will pm nightz with it so he can change any necessary links


https://drive.google.com/file/d/0B5j8d4FSc7drUUltVVVJdzFwbWc/view?usp=sharing

https://drive.google.com/uc?export=download&id=0B5j8d4FSc7drUUltVVVJdzFwbWc

[3worlduser]

        "addr" : "188.33.82.204:57424",
        "startingheight" : 2123,
        "addr" : "104.207.133.150:44170",
        "startingheight" : 39060,
        "addr" : "196.210.72.59:55389",
        "startingheight" : 38897,
        "addr" : "151.77.195.64:61885",
        "startingheight" : 39060,
        "addr" : "93.86.119.180:50418",
        "startingheight" : 38746,
        "addr" : "46.233.42.249:34575",
        "startingheight" : 39060,
        "addr" : "176.36.240.68:34575",
        "startingheight" : 27159,
        "addr" : "198.50.229.39:34575",
        "startingheight" : 39060,
        "addr" : "77.28.58.168:53447",
        "startingheight" : 39060,
        "addr" : "[2001:41d0:8:656c::]:46556",
        "startingheight" : 39060,
        "addr" : "212.85.91.20:34575",
        "startingheight" : 38897,
        "addr" : "46.236.161.66:34575",
        "startingheight" : 10968,
        "addr" : "88.206.187.247:33767",
        "startingheight" : 39061,
        "addr" : "46.37.194.32:49782",
        "startingheight" : 39061,
        "addr" : "197.89.176.121:59469",
        "startingheight" : 39061,
        "addr" : "68.185.188.91:62738",
        "startingheight" : 20109,
        "addr" : "[2601:47:4202:5d50:753a:cea3:69f7:3695]:65050",
        "startingheight" : 39061,
        "addr" : "37.59.18.108:40030",
        "startingheight" : 39061,
        "addr" : "45.63.1.27:55274",
        "startingheight" : 39061,
        "addr" : "50.191.30.64:65056",
        "startingheight" : 39061,
        "addr" : "92.233.105.50:56414",
        "startingheight" : 39061,
        "addr" : "77.251.63.42:34575",
        "startingheight" : 7319,
        "addr" : "[2001:19f0:0:208c:7090:b8d0:7489:1b67]:57344",
        "startingheight" : 39061,
        "addr" : "213.202.214.140:34575",
        "startingheight" : 39061,
        "addr" : "[2a01:e35:2423:7280:a0f9:6e66:89b5:acda]:50235",
        "startingheight" : 39063,
        "addr" : "84.234.52.190:45476",
        "startingheight" : 39064,
        "addr" : "79.69.39.40:63872",
        "startingheight" : 38897,
        "addr" : "[2607:5300:60:5e6e::3c5:64b2]:34575",
        "startingheight" : 39066,
        "addr" : "[2002:b024:f044::b024:f044]:54265",
        "startingheight" : 27318,
        "addr" : "81.162.199.253:2257",
        "startingheight" : 38897,
        "addr" : "180.216.71.145:49775",
        "startingheight" : 39074,
        "addr" : "203.91.244.188:52552",
        "startingheight" : 39077,
        "addr" : "190.44.37.242:6099",
        "startingheight" : 23459,
        "addr" : "82.66.55.40:50588",
        "startingheight" : 39082,


it certainly seems that the vast majority of my peers are in agreeance with the xplorer.

root@vps:~/.loco# loco getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7
root@vps:~/.loco# loco getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4


only 3 or so seem on the fork featuring the hashes as featured by other users


loco getblockhash 38289
768182444286b91967de161bb35cbe396651547c55341bb08065f583d3066df5

loco getblockhash 38431
056c84dd712b96c46f50c61563cc0fdea33c902e61070be7bf32b0317d3264d2


--
i have synced twice to the other chain, and both times it's re-organised.
i'm curious as to who was on the other chain and has also reorganised

but what about novaexchange I send 100 LOC to test and the transaction got rejected, also as you are in the same chain of the explorer
can you claim from the faucet?

[novaexchange]

Novaexchange has taken LOCO into maintenance mode until this is sorted out, please pm me when it is time.

loco@ws03:~$ coind getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7

loco@ws03:~$ coind getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

I guess those people that were on wrong chain once updated to 1.3 never did a clean index of the wallet with the correct peers, so the invalid fork is still ghosting around. I had my wallet offline the whole afternoon yesterday, and still picked up Bumbacoins chain.

I am at height when this is posted:
loco@ws03:~$ coind getblockcount
39216

coind getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

Please keep me posted.

[ocminer]

Novaexchange has taken LOCO into maintenance mode until this is sorted out, please pm me when it is time.

loco@ws03:~$ coind getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7

loco@ws03:~$ coind getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

I guess those people that were on wrong chain once updated to 1.3 never did a clean index of the wallet with the correct peers, so the invalid fork is still ghosting around. I had my wallet offline the whole afternoon yesterday, and still picked up Bumbacoins chain.

I am at height when this is posted:
loco@ws03:~$ coind getblockcount
39216

coind getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

Please keep me posted.

Same height and blockhash on suprnova here

[novaexchange]

Novaexchange has taken LOCO into maintenance mode until this is sorted out, please pm me when it is time.

loco@ws03:~$ coind getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7

loco@ws03:~$ coind getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

I guess those people that were on wrong chain once updated to 1.3 never did a clean index of the wallet with the correct peers, so the invalid fork is still ghosting around. I had my wallet offline the whole afternoon yesterday, and still picked up Bumbacoins chain.

I am at height when this is posted:
loco@ws03:~$ coind getblockcount
39216

coind getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

Please keep me posted.

Same height and blockhash on suprnova here

Does that mean youre on the same height and blockhash as Novaexchange aswell, or the same height as suprnova only?

Edit, had to read it twice to actually see what you wrote, ignore. :-)

[ocminer]

Novaexchange has taken LOCO into maintenance mode until this is sorted out, please pm me when it is time.

loco@ws03:~$ coind getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7

loco@ws03:~$ coind getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

I guess those people that were on wrong chain once updated to 1.3 never did a clean index of the wallet with the correct peers, so the invalid fork is still ghosting around. I had my wallet offline the whole afternoon yesterday, and still picked up Bumbacoins chain.

I am at height when this is posted:
loco@ws03:~$ coind getblockcount
39216

coind getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

Please keep me posted.

Same height and blockhash on suprnova here

Does that mean youre on the same height and blockhash as Novaexchange aswell, or the same height as suprnova only?

Loco/src/locod getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

[bumbacoin]

it certainly seems the code has decided which chain it does prefer

 loco getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8





i'm curious how you can force yr client to remain on the smaller chain at this point.

i cant get one to stick with it, keeps reorganising and joining the more popular chain
 (purely wondering for educational purposes ofc)

[3worlduser]

Novaexchange has taken LOCO into maintenance mode until this is sorted out, please pm me when it is time.

loco@ws03:~$ coind getblockhash 38289
6ea591f22faf6b84db8e52a415aa380c70a75cb491007f9cd9af926beca731b7

loco@ws03:~$ coind getblockhash 38431
080691109117a6313facc4291672a3690efd850374aa33b2f9d200dd26cc66a4

I guess those people that were on wrong chain once updated to 1.3 never did a clean index of the wallet with the correct peers, so the invalid fork is still ghosting around. I had my wallet offline the whole afternoon yesterday, and still picked up Bumbacoins chain.

I am at height when this is posted:
loco@ws03:~$ coind getblockcount
39216

coind getblockhash 39216
5b6f941effc391832e22171d646317e444ce0e3e2161bde4854ffecf26848dd8

Please keep me posted.

I have the same hashes for block 38289 - 38431 - 39216 in the block explorer and in my personal wallet but a like an hour ago I tried to send 100 loc to test nova so generate a new address in the page send the coins and the transaction got rejected, now the transaction show as aproved on the block explorer so it seem that we are in the same chain