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

[Nightz]

Hi,

We've added LOCO to the miners multipool: www.zpool.ca

http://www.zpool.ca/site/gomining?algo=quark

Cheers!

Thanks for that.

Update is near enough ready to publish just sorting few things with the graphics for the new logo then we should be good to go and get the whole Network Updated.

Thanks
Nightz

[Nightz]

I have messaged Yobit and spoken to Dom Now just awaiting response off Admins there.

Will keep all updated tho

Thanks

[GREEDYJOHN]

I have messaged Yobit and spoken to Dom Now just awaiting response off Admins there.

Will keep all updated tho

Thanks

Yobit takes forever. Your best option is to compress all the relevant updates into ONE BIG UPDATE, then do it with us, before contacting YOBIT.

[Anatoliyb50]

Wallet stopped at 381386 unit on October 8 th!!!???

[GREEDYJOHN]

Wallet stopped at 381386 unit on October 8 th!!!???

We are waiting for Nightz to get back into action.

[Velgelm]

Correct chain

getblockhash 384183

a690ae3e8b7a2074f626930b2a32e53e76ba6ce2e0a285409b405503304e34d1

[Mikelius]

     

  What is the latest version of Wallet?
       and link down?
       Thank you

[Coin_trader]

this might be an old thread but i guess this thread needs to be translated into some other languages for the benefit of those non-english investors and traders, if in case you need a translator, i can do the Filipino translation.

[Mikelius]

     

  What is the latest version of Wallet?
       and link down?
       Thank you

everything is in the OP, and links are ok

-----------------------------------------
which it is OP ??
I do not understand.
You can place the Like, please.
Thank you so much.
(Translated with google)

[Anatoliyb50]

Wallet stopped at 381386 unit on October 8 th!!!???

nope, check forking:
getblockhash 381386
ef517f583d0af2337a75b41f262ec1b0e39321d57dfffbe28d30f11c47005c3d

healthy nodes right now:
addnode=45.32.41.132
addnode=64.62.174.105
addnode=68.36.216.167
addnode=76.106.178.142
addnode=84.234.52.190
addnode=86.151.218.108
addnode=88.206.186.58
addnode=115.76.195.234
addnode=188.82.35.166
addnode=198.27.81.25
addnode=199.188.236.41
addnode=212.112.150.250

these report outdated versions, should be excluded:
# addnode=5.189.189.51
# addnode=95.84.130.70

I can not check (getblockhash)- do not get a response wallet and wallet hangs.

[jc12345]

Wallet stopped at 381386 unit on October 8 th!!!???

nope, check forking:
getblockhash 381386
ef517f583d0af2337a75b41f262ec1b0e39321d57dfffbe28d30f11c47005c3d

healthy nodes right now:
addnode=45.32.41.132
addnode=64.62.174.105
addnode=68.36.216.167
addnode=76.106.178.142
addnode=84.234.52.190
addnode=86.151.218.108
addnode=88.206.186.58
addnode=115.76.195.234
addnode=188.82.35.166
addnode=198.27.81.25
addnode=199.188.236.41
addnode=212.112.150.250

these report outdated versions, should be excluded:
# addnode=5.189.189.51
# addnode=95.84.130.70

I can not check (getblockhash)- do not get a response wallet and wallet hangs.

Maybe re-sync your wallet.

Getblockhash 396523 c7b5e8e5c62c98188eebaeb9a29ac9f46ded91937a8f84f5e9f18b518e57ad39

[Anatoliyb50]

I can not check (getblockhash)- do not get a response wallet and wallet hangs.

it's pretty heavy on system resources when syncing, check its cpu and memory usage,
maybe your system is unable to run it at all.
if there's still hope just leave it alone, it will sync eventually

Thank you for the answer. Now wallet processor will ship up to 90% and it freezes. Prior to that he worked without deadlocks, but very slowly passed synchronization. Let's wait for the new wallet from Dev.

[jc12345]

Maybe just a point of interest. I notice that some people stake with small input blocks and the rewards are very small - in the region of 0.0006-0.006. This will cause those stakers to have very large transaction fees once they want to move or consolidate their coins. It is very easy for all those small rewards to cause a transaction fee more than the actual value of the combined transaction. Eg. 1000 blocks of such small amounts will have a smaller value than the transaction fee to process 1000 transactions due to the size of those transactions causing an insufficient funds scenario. To manually combine such small blocks will take ages as a few larger reward blocks will have to be selected together with a bunch of dust transactions in order for there to be enough value in the combination to cover the transaction fees.

In essence, staking such small input blocks is a waste of time. If it was a fixed reward it is another matter but this is percentage based rewards.

I would recommend that stakers combine their coins once in a wile to have larger rewards and smaller transaction fees.

[jc12345]

Maybe just a point of interest. I notice that some people stake with small input blocks and the rewards are very small - in the region of 0.0006-0.006. This will cause those stakers to have very large transaction fees once they want to move or consolidate their coins. It is very easy for all those small rewards to cause a transaction fee more than the actual value of the combined transaction. Eg. 1000 blocks of such small amounts will have a smaller value than the transaction fee to process 1000 transactions due to the size of those transactions causing an insufficient funds scenario. To manually combine such small blocks will take ages as a few larger reward blocks will have to be selected together with a bunch of dust transactions in order for there to be enough value in the combination to cover the transaction fees.

I would recommend that stakers combine their coins once in a wile to have larger rewards and smaller transaction fees.

those small blocks are simply POW blocks (5 coins),
nope, tx fee doesn't go thru the roof,
i always manually combined them, but in fact all these things are boring

No there are actually people that are staking such small amounts:

2016/16/10 - 0.00068447 LOC which was an actual staking reward.

Such a transaction has approximately the same overhead than a single transaction of 10000 LOC. Now imaging adding 1000 of those small ones and having to pay 1.5+ LOC for the transaction fee. The tx fee will be more than the value of the tx. You will never be able to send the coins unless you add an input block to the mix of about 1.5 LOC so that you at least have a positive dust value for the tx.

[GREEDYJOHN]

https://bitcointalk.org/index.php?action=profile;u=353358

Name:  Nightz
Posts:  805
Activity: 560
Position:  Hero Member
Date Registered:  July 08, 2014, 01:05:25 PM
Last Active:  October 14, 2016, 08:16:03 PM



We hope that he stays around this time     

[jc12345]

https://bitcointalk.org/index.php?action=profile;u=353358

Name:  Nightz
Posts:  805
Activity: 560
Position:  Hero Member
Date Registered:  July 08, 2014, 01:05:25 PM
Last Active:  October 14, 2016, 08:16:03 PM



We hope that he stays around this time     

Life is too short to worry about these things. Sit back, relax, have a drink. If nothing happens in the next month then sit back, relax and have a drink. 

[jc12345]

No there are actually people that are staking such small amounts:

2016/16/10 - 0.00068447 LOC which was an actual staking reward.

Such a transaction has approximately the same overhead than a single transaction of 10000 LOC. Now imaging adding 1000 of those small ones and having to pay 1.5+ LOC for the transaction fee. The tx fee will be more than the value of the tx. You will never be able to send the coins unless you add an input block to the mix of about 1.5 LOC so that you at least have a positive dust value for the tx.

txid please,
that reward is pretty much the same that i have for POW blocks (0.00068448)
here's example
do you realize that each tx value is 5.00068448 ?

Code:

02:24:56

Welcome to the Loco RPC console.
Use up and down arrows to navigate history, and Ctrl-L to clear screen.
Type help for an overview of available commands.


03:00:14

gettransaction 5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4


03:00:15

{
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"version" : 1,
"time" : 1476442800,
"locktime" : 0,
"vin" : [
{
"txid" : "892fc1e5bbb3653eb703390d49ca8be10b20c7e9f1596c8fa7e6b746e909e394",
"vout" : 0,
"scriptSig" : {
"asm" : "3045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b01 03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d",
"hex" : "483045022100886050da7bfea591aa8c5f4adcbd182e4813a0d58691ef1fd9ef43f6fb0d667e02200646dd4d54eee325aa05ea6fa0e611cfb1c7db5cce01df8a34ce097b741d575b012103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : "",
"type" : "nonstandard"
}
},
{
"value" : 5.00068448,
"n" : 1,
"scriptPubKey" : {
"asm" : "03c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576d OP_CHECKSIG",
"hex" : "2103c76ec2cb2011457a4dcc0478afd2f4f4d325891820c3b1331547aa70be14576dac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E"
]
}
},
{
"value" : 0.00068447,
"n" : 2,
"scriptPubKey" : {
"asm" : "OP_DUP OP_HASH160 c6e899a49d0140be82e68648903e3a9b8c00b1f8 OP_EQUALVERIFY OP_CHECKSIG",
"hex" : "76a914c6e899a49d0140be82e68648903e3a9b8c00b1f888ac",
"reqSigs" : 1,
"type" : "pubkeyhash",
"addresses" : [
"69ByFdTC9RoaKKe6vryoxx1pQ5FxAPRpdA"
]
}
}
],
"amount" : -0.00068447,
"fee" : 0.00136895,
"confirmations" : 4787,
"generated" : true,
"blockhash" : "e9db9ec20feb156aadc57ab08b1955ad39ebfd125526c1e0462d6d87fa8ab5fb",
"blockindex" : 1,
"blocktime" : 1476442800,
"txid" : "5d2d2ff92155cfb5009defe8d99435f4eab208a51bc77eafc941a40ffd584bc4",
"time" : 1476442800,
"timereceived" : 1476442800,
"details" : [
{
"account" : "",
"address" : "5svExsoYQrwLdrYQdbH5szR6onxHBrzj7E",
"category" : "generate",
"amount" : 0.00136895
}
]
}

idk if there are any masternodes running,
maybe they have a bunch of tiny pieces coming from stakers

Yes you are right. It is very difficult and confusing to analyse without a proper block explorer. Maybe there will be a new one after the next version of the wallet (if there is a next version) how exactly the reward structure works and what the split is between POW and staking.

[Velgelm]

right chain


getblockhash 397454


0d98df27def1581ccb320a035dc894c720c9a60292eb57f3e8e94bda7f8198fd

on my wallet connected at 2 nodes :
 "5.189.189.51:35575",
"188.82.35.166:35575",

[Velgelm]

lococoin.conf

connect=188.82.35.166:35575
connect=86.151.218.108:35575
connect=83.179.198.98:35575
connect=88.215.150.2:35575
--------------------------------
getpeerinfo

[
{
"addr" : "188.82.35.166:35575",
"addrlocal" : "88.215.150.2:25879",
"services" : "00000001",
"lastsend" : 1476794659,
"lastrecv" : 1476794658,
"bytessent" : 2085,
"bytesrecv" : 2186,
"conntime" : 1476794641,
"pingtime" : 0.48602800,
"version" : 70013,
"subver" : "/Go2:1.4.5/",
"inbound" : false,
"startingheight" : 400702,
"banscore" : 0,
"syncnode" : true
},
{
"addr" : "86.151.218.108:35575",
"addrlocal" : "88.215.150.2:25881",
"services" : "00000001",
"lastsend" : 1476794659,
"lastrecv" : 1476794657,
"bytessent" : 1089,
"bytesrecv" : 4161,
"conntime" : 1476794641,
"pingtime" : 0.21501200,
"version" : 70013,
"subver" : "/Go2:1.4.5/",
"inbound" : false,
"startingheight" : 400702,
"banscore" : 0,
"syncnode" : false
}
]
----------------

getblockhash 400704

4366c111715d0554168be85c535905cfc1e5548f1f9c02717652d0b818856db8

[Velgelm]

lococoin.conf

connect=188.82.35.166:35575
connect=86.151.218.108:35575
connect=83.179.198.98:35575
connect=88.215.150.2:35575
--------------------------------------

getblockhash 407658

997b6874c0958b6e8dad0b099c615a3a4f16083d522d7bde0df4164b6ad72f98
------------------------------------------------------------------------------------------