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

[Velgelm]

my lastest block 42010

[USScrypto]

My 1.3 wallet is offline and waiting for 1.4 to get up to date with the blockchain...

[zdeni82]

mine is too

[EasyTrade]

another way to use nightz copy of the blockchain,

is to only use blk0001.dat, rename it to bootstrap.dat, place it in the datadir and start the qt.

if done correctly, the wallet will import the data from the bootstrap much quicker than downloading from the network.

Holy Batman.. it works.. seems to be..

I deleted everything from data directory except wallet.dat, peer.dat(knightz) and bootstrat.dat.

It begun reading bootstrap right away..  didnt even had to importprivkey.

haven't finished yet but will check if aforementioned knights block number matches.  Old chain didn't match.

Thanks a bunch!~!!

[bumbacoin]

another way to use nightz copy of the blockchain,

is to only use blk0001.dat, rename it to bootstrap.dat, place it in the datadir and start the qt.

if done correctly, the wallet will import the data from the bootstrap much quicker than downloading from the network.

Holy Batman.. it works.. seems to be..

I deleted everything from data directory except wallet.dat, peer.dat(knightz) and bootstrat.dat.

It begun reading bootstrap right away..  didnt even had to importprivkey.

haven't finished yet but will check if aforementioned knights block number matches.  Old chain didn't match.

Thanks a bunch!~!!

if using nightz files as he directed, it would have been quicker as the entire chain was pre-loaded, then it would have been a matter of importing yr priv key.

personally i generally use it as a bootstrap. i think i've had too many experiences of importing priv key failures :p


--


i was wondering if there is any relationship between crazy weight figures and so many forks.
perhaps the variances in difficulty between pow and pos are problematic.

    "netmhashps" : 50.57132355,
    "netstakeweight" : 1472530330345.55712891,

[bumbacoin]

woot another fork
i am currently on block 42930

loco getpeerinfo | grep height
        "startingheight" : 41137,
        "startingheight" : 31237,
        "startingheight" : 41301,
        "startingheight" : 35478,
        "startingheight" : 41306,
        "startingheight" : 41306,
        "startingheight" : 42898,
        "startingheight" : 42898,
        "startingheight" : 25409,
        "startingheight" : 39886,
        "startingheight" : 42138,
        "startingheight" : 42911,
        "startingheight" : 41818,
        "startingheight" : 42911,
        "startingheight" : 41303,
        "startingheight" : 18603,
        "startingheight" : 42911,
        "startingheight" : 41137,
        "startingheight" : 42913,
        "startingheight" : 41809,

[bumbacoin]

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.

[alexcrownjr]

Hi. pool down ?

Code:

[2016-05-04 09:45:46] ...retry after 10 seconds
[2016-05-04 09:46:26] stratum_subscribe timed out
[2016-05-04 09:46:26] ...retry after 10 seconds
[2016-05-04 09:47:07] stratum_subscribe timed out
[2016-05-04 09:47:07] ...retry after 10 seconds
[2016-05-04 09:47:47] stratum_subscribe timed out
[2016-05-04 09:47:47] ...retry after 10 seconds
[2016-05-04 09:48:27] stratum_subscribe timed out
[2016-05-04 09:48:27] ...retry after 10 seconds
[2016-05-04 09:49:07] stratum_subscribe timed out
[2016-05-04 09:49:07] ...retry after 10 seconds

[ocminer]

Hi. pool down ?

Code:

[2016-05-04 09:45:46] ...retry after 10 seconds
[2016-05-04 09:46:26] stratum_subscribe timed out
[2016-05-04 09:46:26] ...retry after 10 seconds
[2016-05-04 09:47:07] stratum_subscribe timed out
[2016-05-04 09:47:07] ...retry after 10 seconds
[2016-05-04 09:47:47] stratum_subscribe timed out
[2016-05-04 09:47:47] ...retry after 10 seconds
[2016-05-04 09:48:27] stratum_subscribe timed out
[2016-05-04 09:48:27] ...retry after 10 seconds
[2016-05-04 09:49:07] stratum_subscribe timed out
[2016-05-04 09:49:07] ...retry after 10 seconds

Too much forking and Problems

[Nightz]

UPDATE YOUR CLIENTS PLEASE

[Nightz]

Hopefully now we get back on track

[USScrypto]

Updated, but it cannot find peers now...

[zdeni82]

Updated, but it cannot find peers now...

me too...

[logocreator]

well, i manage to full sync with this node:

addnode=92.233.105.50:35575

Code:

"version" : "v1.4.0.0-Alpha",
"protocolversion" : 70013,
"walletversion" : 60000,
"balance" : 19.20000000,
"blocks" : 41200,
"moneysupply" : 1890936.79037110,

[Nightz]

well, i manage to full sync with this node:

addnode=92.233.105.50:35575

Code:

"version" : "v1.4.0.0-Alpha",
"protocolversion" : 70013,
"walletversion" : 60000,
"balance" : 19.20000000,
"blocks" : 41200,
"moneysupply" : 1890936.79037110,

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

[Nightz]

Updated, but it cannot find peers now...

me too...

Port numbers have been changed from

port=34575
rpcport=34574

to

port=35575
rpcport=35574

[logocreator]

Solo mining works perfect, i just found a block

[shimlbit]

locod getblockhash 41304
0525ad327852ff6696960397cc52e458ad88d0eed107490f8c2a410be6c2265b

[Nightz]

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

[Nightz]

locod getblockhash 41304
0525ad327852ff6696960397cc52e458ad88d0eed107490f8c2a410be6c2265b

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