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

Anything Else people would like me to look into ?

Can certainly look into that there mate

Hmm..
It seems virustotal.com is busy.


"Your file is now queued for scanning, please wait until the analysis starts.
SHA256:    a16cbe76b23ad06c8a9c4f73b8e9f4343a35fb36ab6ac2e0bd3f2c3c68184308
File name:    Loco-Qt.exe"

Is there a link to analyzed version1.4?

Edit:
scan result at Meta defender:
https://www.metadefender.com/#!/results/file/820c1177b5a54d29b9a946f26e25ef39/regular

No need to give it out mate. I have put it into chainparamsseeds

Update V1.4.1.0 is Building now then I will need somebody with coins that are matured to see if it reports back correctly

if suprnova is back ,that would be nice

remember Nightz's node is   addnode=92.233.105.50:35575

solo mining, was working right, now no more blocks despite the fact that i have almost all the nethash

mmh probably has to do with pos block that are mixed in between....

No need for that now mate, I am the main node and all is good here.

But just to attest yes that hash is correct

Next little fix will be V1.4.1.0 for the stake weight to display correct Once that is done Will be moving onto v1.5

locod getblockhash 41304
0525ad327852ff6696960397cc52e458ad88d0eed107490f8c2a410be6c2265b

Solo mining works perfect, i just found a block

Port numbers have been changed from

port=34575
rpcport=34574

to

port=35575
rpcport=35574

Yes that is my node mate, It now has 6 connections at the moment

well, i manage to full sync with this node:

addnode=92.233.105.50:35575

me too...

Updated, but it cannot find peers now...

Hopefully now we get back on track

UPDATE YOUR CLIENTS PLEASE

Too much forking and Problems

Hi. pool down ?

in my transaction history, there is a number of bunches of PoS blocks all registering in the same minute.

is it plausible that the weight/difficulty is so broked that it causes similar weight inputs to stake almost simultaneously?

it would be interesting to compare chains around the forks and see if there is such a string of immediate blocks



-

another thing i noticed is that my Qt is receiving current blocks (42960) while syncing to earlier blocks  (40469).
these current blocks register as orphans
(both blocks are valid on the chain my daemon is on)


8c4eb1d37b72091275a487a95890e8935fe2379092163c442db8fb2ab75cb998
ERROR: ProcessBlock() : already have block 40464 b3ad8fe415b9fa1003defd01e38caf44782305e0e8f897b3bbfeef83da99a320
ERROR: ProcessBlock() : already have block 40465 34585821e887e6fedd946cd94e0077c98f61353a13e323bc99b9a14451278fbd
SetBestChain: new best=03e96065257ea4bb4aa7068da4c12b27f4ac9aaf30e098befb70524a366c498d  height=40466  trust=4133145183542959785  blocktrust=27541291718550  date=05/03/16 05:46:08
ProcessBlock: ACCEPTED
SetBestChain: new best=2471886cbc49d2ac19a42738e2b8b30671a6cf379dde213ad7d20b79df3ccd6a  height=40467  trust=4133176227222266083  blocktrust=31043679306298  date=05/03/16 05:46:24
ProcessBlock: ACCEPTED
SetBestChain: new best=6184ed72977b8f78bf90e58111c620034dc7db1f335e7f9ff926cc190867d2a6  height=40468  trust=4133211218712946099  blocktrust=34991490680016  date=05/03/16 05:46:24
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 57, prev=00c7e9aa8faa74a1e57e5b9262a67b24e4af7393a88d16c6af6fb2f7aa0cc5b4
SetBestChain: new best=8080c3c3885650a3e0719aa6dbd6a90c85fd0c0260b700977b3517294f2d82ae  height=40469  trust=4133252572357021641  blocktrust=41353644075542  date=05/03/16 05:46:56
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 58, prev=c75ab2afd2e432e24208015329ae0d8937c4303e6369896bf0cf9ede732fb7ca
SetBestChain: new best=8322e51aaaba5e27abb24c9fc78c360f197415fc072a5ad3568cd9331e45dfb2  height=40470  trust=4133297124651987452  blocktrust=44552294965811  date=05/03/16 05:46:56
ProcessBlock: ACCEPTED
ProcessBlock: ORPHAN BLOCK 59, prev=b0db7a75e96e219a069549209507405adf6806bc2010ffb3ae18551dc22c9972
SetBestChain: new best=1d2c0fcbf3a607183606cd3d984fd864ed6ed0f0e79df7b37a56d75353b715b1  height=40471  trust=4133349777433583154  blocktrust=52652781595702  date=05/03/16 05:57:20
ProcessBlock: ACCEPTED

etc

also. note blocks 40469 and 40470 both share the same block time of 1462254416
and belong to the same address.