Pages:
Author

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

hero member
Activity: 1302
Merit: 504
the fork won't resolve that way, codebase is tolerant,
there are 2 different chains running the same v1.4.5.0,
right now 304070 and 304862 blocks each,
they don't orphan each other

The dev must checkpoint the correct chain in the wallet and people on the "wrong" chain must re-sync with the new wallet.

of course, but "the dev" is main problem here Smiley
i could still orphan other chain on this hybrid "undocumented way" but it needs enourmous hash solo

The dev ie me will not be an issue now. I will be online properly in around 4hours and will catch up with what has been going on. I have been quite but that does not mean i have not been working on the code.
legendary
Activity: 1778
Merit: 1000
is this coin being taken over?

I am resyncing my wallet from scratch.
sr. member
Activity: 299
Merit: 250
we need more nodes with 1.4.5 core and lastest chain!
Members! Please post yours IP if your version 1.4.5 and Lastest right blockchain ex.(
08:27:21

getblockhash 310989 fbf286caf22b2bc13f14498ddbfe1e716a30e4f505da98f7680664f76ca02c4d
 
legendary
Activity: 1638
Merit: 1013
Getblockhash 310860 for the Yobit chain is 8bd09bc8d80ca5158011c2447dc136ee6c65c3cddf12d8a62516127f048b6ed5

Successfully sent coins to Yobit with this chain

addnode=5.189.189.51:35575
legendary
Activity: 1421
Merit: 1001
download lastest wallet 1.4.5
save your wallet.dat from old wallets, and copy wallet.dat to %appdata%\%username%\Loco
of couse download lastest chain
https://bitcointalksearch.org/topic/annlocupdate-v145-out-locoquarkpowposhiposmasternodestorlocann-1438233
in loco.conf use this nodes:
maxconnections=100
rpcuser=zzz
rpcpassword=xxx
server=1
daemon=1
listen=1
rpcallowip=*
gen=0
staking=1
connect=88.215.150.2:51522
connect=88.215.150.2:52988
# if this nodes not working, uncommit this strings ()
#addnode=175.192.238.15:35575
#addnode=68.36.216.167:35575
#addnode=176.14.89.191:35575
#addnode=198.74.56.141:43240
#addnode=176.65.127.117:43392
#addnode=108.61.199.252:37839
#addnode=148.251.8.18:39170
#addnode=88.206.186.58:48289
#addnode=85.175.216.200:52788
#addnode=85.175.216.200:53050
#addnode=45.32.41.132:43374
#addnode=88.215.150.2:51522
#addnode=88.215.150.2:52988
#addnode=5.44.172.146:5606
#addnode=95.23.136.43:49711
#addnode=197.82.212.106:48522


Thanks, i will try
sr. member
Activity: 299
Merit: 250
download lastest wallet 1.4.5
save your wallet.dat from old wallets, and copy wallet.dat to %appdata%\%username%\Loco
of couse download lastest chain
https://bitcointalksearch.org/topic/annlocupdate-v145-out-locoquarkpowposhiposmasternodestorlocann-1438233
in loco.conf use this nodes:
maxconnections=100
rpcuser=zzz
rpcpassword=xxx
server=1
daemon=1
listen=1
rpcallowip=*
gen=0
staking=1
connect=88.215.150.2:51522
connect=88.215.150.2:52988
# if this nodes not working, uncommit this strings ()
#addnode=175.192.238.15:35575
#addnode=68.36.216.167:35575
#addnode=176.14.89.191:35575
#addnode=198.74.56.141:43240
#addnode=176.65.127.117:43392
#addnode=108.61.199.252:37839
#addnode=148.251.8.18:39170
#addnode=88.206.186.58:48289
#addnode=85.175.216.200:52788
#addnode=85.175.216.200:53050
#addnode=45.32.41.132:43374
#addnode=88.215.150.2:51522
#addnode=88.215.150.2:52988
#addnode=5.44.172.146:5606
#addnode=95.23.136.43:49711
#addnode=197.82.212.106:48522
legendary
Activity: 1421
Merit: 1001
Hello, i didn't open my wallet since a moment now, it's better to wait a sign of life from the dev?
legendary
Activity: 1638
Merit: 1013
the fork won't resolve that way, codebase is tolerant,
there are 2 different chains running the same v1.4.5.0,
right now 304070 and 304862 blocks each,
they don't orphan each other

The dev must checkpoint the correct chain in the wallet and people on the "wrong" chain must re-sync with the new wallet.
sr. member
Activity: 299
Merit: 250
sr. member
Activity: 299
Merit: 250
several hours ago i'd silenced forked aikapool by standard means,
to help more populated but shorter chain outgrow the rival.
now job is done, the longer chain is ours.

getblockhash 303812
5c4711ad4c51a0af23c0d470486be2270cfcdc867843dc3d00610e78a58a8d68

addnode=198.74.56.141:43240
addnode=176.65.127.117:43392
addnode=108.61.199.252:37839
addnode=148.251.8.18:39170
addnode=88.206.186.58:48289
addnode=85.175.216.200:52788
addnode=85.175.216.200:53050
addnode=45.32.41.132:43374
addnode=88.215.150.2:51522
addnode=88.215.150.2:52988
addnode=5.44.172.146:5606
addnode=95.23.136.43:49711
addnode=197.82.212.106:48522

if anyone still needs a bootstrap or chain image, feel free to ask
yes, please share lastest bootstrap
sr. member
Activity: 299
Merit: 250
this nodes use lastest 1.4.5 alpha client :
connect=175.192.238.15:35575
connect=68.36.216.167:35575
connect=176.14.89.191:35575
hey man! we need detect client with lastest 1.4.5 core!
open debug console and type:
getpeerinfo
my list:
{
"addr" : "175.192.238.15:35575",
"addrlocal" : "88.215.150.2:51518",
"services" : "00000001",
"lastsend" : 1471950327,
"lastrecv" : 1471950327,
"bytessent" : 463,
"bytesrecv" : 1769,
"conntime" : 1471950202,
"pingtime" : 0.32201900,
"version" : 70013,
"subver" : "/Go2:1.4.5/",
"inbound" : false,
"startingheight" : 303632,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "68.36.216.167:35575",
"addrlocal" : "88.215.150.2:51521",
"services" : "00000001",
"lastsend" : 1471950327,
"lastrecv" : 1471950327,
"bytessent" : 463,
"bytesrecv" : 1189,
"conntime" : 1471950202,
"pingtime" : 0.22601300,
"version" : 70013,
"subver" : "/Go2:1.4.5/",
"inbound" : false,
"startingheight" : 303632,
"banscore" : 0,
"syncnode" : false
},
{
"addr" : "176.14.89.191:35575",
"addrlocal" : "88.215.150.2:51522",
"services" : "00000001",
"lastsend" : 1471950266,
"lastrecv" : 1471950330,
"bytessent" : 19383,
"bytesrecv" : 256574,
"conntime" : 1471950202,
"pingtime" : 0.07000400,
"pingwait" : 75.93134300,
"version" : 70013,
"subver" : "/Go2:1.4.5/",
"inbound" : false,
"startingheight" : 303758,
"banscore" : 0,
"syncnode" : true
}
]
This nodes with correct blockchain and core version!

sr. member
Activity: 299
Merit: 250
Can someone upload lastest blockchain ?
my wallet again stuck in block 200260
legendary
Activity: 1638
Merit: 1013
this coin has been forked for quite some time now:

these nodes
addnode=5.189.189.51:35575
addnode=85.175.216.200:40020
addnode=88.206.186.58:19274
addnode=79.101.82.32:62237
addnode=45.63.1.27:50187
addnode=45.32.41.132:58228

and aikapool.com are on different chains,
both look consistent and healthy
which one's correct might be dev's concern.
pool chain is a bit longer but lower pow diff

As time goes on this wallet becomes more and more difficult to run. It is extremely resource intensive. The dev needs to fix the issue if he wants any hope of longevity of LOC.
legendary
Activity: 1778
Merit: 1000
KEEP ON TRUSTING A DEV THAT MAY NEVER COME BACK!!!!  Angry   Angry   Angry   Angry
newbie
Activity: 4
Merit: 0
hey wallet transactions off?

Sorry guy working normality nice work Cheesy

Nice protection for high power Cheesy coin is a low power Cheesy

keep trusting in your coin...
newbie
Activity: 4
Merit: 0
sr. member
Activity: 445
Merit: 250
Could someone upload a snapshot instead of the bootstrap ?
Causes crashes and is still very slow.
Thanks !

I'm sure we can get one of those for ya
Great !
I think you would make more ppl very happy with one.
BIG time savers.
hero member
Activity: 1302
Merit: 504
Could someone upload a snapshot instead of the bootstrap ?
Causes crashes and is still very slow.
Thanks !

I'm sure we can get one of those for ya
hero member
Activity: 1302
Merit: 504

Im having big issues synching.

Tried jumping 9 days back.. still problems.

Are there multiple forks going on or wtf is up?

it's generic shit of the coinbase, wallet processing tons of orphans, and it's progressing....
so it takes too much resources, and may hang itself or even brake the system.

my wallet still can make it thru, and always gets synced, with lags and load spikes,
but already not very good at solo mining, folks with more powerful machines
may have trouble much later, but they will for sure,
just a matter of time (and number of staking blocks on the network)

This type of wallet does tend to become very slow and difficult to manage over time. I hope nightz would be able to fix the code so that performance improves.

Woa.. i noticed now that it consumes more cpu than the 6 other wallets running.

Ok.. hope for update, meanwhile ill just move it to something more powerful.

The update to be released addresses a couple of things incl the amount of ram n cpu it uses as i too notic3d it on my system but all will be sorted for you guys
newbie
Activity: 2
Merit: 0
These children enter the pool with very powerful machines are to destroy pools : S

Sorrry about that, i was just testing nicehash orders Grin Grin
Pages:
Jump to: