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

[novaexchange]

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

choose a shitnode and sync to it in closed mode:

connect=shitnode
listen=0

this last fork is insignificant and will soon resolve, vast majority of nodes on the same chain,
but several bloody nodes produce orphans and it's no good, the same killed AMS

connect=node03.novaexchange.com:8057
listen=0

:-)

[logocreator]

getblockhash 39266 - 906e7469a524da203ff361be0774c75865ffa87ce6c814b9448a6db8d8ebb304

"blocks" : 39267,
"currentblocksize" : 1229,
version" : "v1.3.0.0-Alpha
"moneysupply" : 1843923

Next Network Blockat suprnova   39,269    (Current: 39,268)
Explorer also ok

[bumbacoin]

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

choose a shitnode and sync to it in closed mode:

connect=shitnode
listen=0

yeh. that's the only way i can get it to stay on taht chain :p
i'm wondering what they're connecting to, each other probably lol

[3worlduser]

getblockhash 39266 - 906e7469a524da203ff361be0774c75865ffa87ce6c814b9448a6db8d8ebb304

"blocks" : 39267,
"currentblocksize" : 1229,
version" : "v1.3.0.0-Alpha
"moneysupply" : 1843923

Next Network Blockat suprnova   39,269    (Current: 39,268)
Explorer also ok

Great my personal wallet have the same chain that the explorer and i can confirm a successful deposit on NOVA

[Nightz]

Forked again it seems

My wallet reports back as it should and so too does the block explorer , Have you tried just closing the wallet then re-opening mate.

[Amph]

the wallet for me does not close in a regular way it remain there hanging for no reason

also i'm received block from pos, which are in another fork, i did already synched all the chain again

[Nightz]

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

[3worlduser]

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Dude can you check the links to the wallets on the webpage I upload the files with the links updated but it still show the old ones, I even delete the webpage file on the server and it is still showing the page.
maybe my ISP is using some kind of proxy

[novaexchange]

Hey guys,

Do a clean sync using Novaexchange as a connect node.

connect=node03.novaexchange.com:8057
listen=0

Once syncted, remove those lines and restart client. Or keep novaexchange as an addnode.

It is configured with maxconnections=200 and has 1gbit, go sync!

Cheers.
--
Edit, spelling..

[Nightz]

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Nightz, check debug.log, you'll see that bloody orphans disaster beginning.
if you don't beat it in near future, it'll bury the coin as it did with other clones.
maybe more strict rules to mark nodes as misbehaving cd help idk

That is a good point mate and I can certainly look into the Banning of bad nodes through misbehaviour .

I also lowered the amount of orphans to be kept in the memory too from 750 to 200.

[Amph]

wallet not synching again, i need the novaexchange node

[bumbacoin]

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Nightz, check debug.log, you'll see that bloody orphans disaster beginning.
if you don't beat it in near future, it'll bury the coin as it did with other clones.
maybe more strict rules to mark nodes as misbehaving cd help idk

That is a good point mate and I can certainly look into the Banning of bad nodes through misbehaviour .

I also lowered the amount of orphans to be kept in the memory too from 750 to 200.

lowering to 200 just made it less resource hungry but doesn't beat anything, look here:

https://gist.github.com/ax66/5856bf5a875167b254a46bdb1b3022d3

and it's rolling and rolling more of'em

it may sound strange but there wasn't such flood in v1.2, it's only now in v1.3
maybe some good code change turned bad in practice

maybe the change to weight has caused it. possibly it will calm down when the age /difficulty relationship settles ??

before the change weight did not seem to be playing a major part of staking, i checked a variety of sizes vs age and there seemed really no consistency.
but since then i got a string of similar sized stakes all together in one clump

also what about ye olde centralised checkpointing that ppc heritage comes with

https://github.com/LGLoco/Loco/blob/master/src/checkpoints.cpp#L321

ofc that would mean another update

[Nightz]

wallet not synching again, i need the novaexchange node

Here this should sort you mate

https://mega.nz/#!HphwSbJR!iOJbOmN5F3HrX-zQGlr3r-6C6mP9CxLgZPf9buwP5PY

It contains

Peers.dat
Blk0001.dat
txleveldb folder

[Nightz]

the wallet for me does not close in a regular way it remin there hanging for no reason

also i'm received block from pos, which are i another fork, i did already synched all the chain again

I will add into the code a lil bit for it to detect shutdown and then it should close correctly, I will also create a bootstrap or upload blk0001.dat for easier syncing on the correct chain.

Nightz, check debug.log, you'll see that bloody orphans disaster beginning.
if you don't beat it in near future, it'll bury the coin as it did with other clones.
maybe more strict rules to mark nodes as misbehaving cd help idk

That is a good point mate and I can certainly look into the Banning of bad nodes through misbehaviour .

I also lowered the amount of orphans to be kept in the memory too from 750 to 200.

lowering to 200 just made it less resource hungry but doesn't beat anything, look here:

https://gist.github.com/ax66/5856bf5a875167b254a46bdb1b3022d3

and it's rolling and rolling more of'em

it may sound strange but there wasn't such flood in v1.2, it's only now in v1.3
maybe some good code change turned bad in practice

WOW  does your debug.log look different to mine I have nowhere near that amount of orphans reported back on my debug.log But again I will look into it today

[novaexchange]

WOW  does your debug.log look different to mine I have nowhere near that amount of orphans reported back on my debug.log But again I will look into it today

My log is orphan free (so far), maybe one or two historically.

[Nightz]

WOW   does your debug.log look different to mine I have nowhere near that amount of orphans reported back on my debug.log But again I will look into it today

of course it may look different if you were synced already.
that flood goes when wallet comes into network at an earlier block,
and instead of syncing quietly it gets this punishment,
the higher the block the more dense is this shit

I purposely deleted the chain yesterday as I'm messing with the code for syncing to get it synchronized faster and I had to resync the whole chain again and it still does not report back all of those like yours does

[3worlduser]

Dude can you check the links to the wallets on the webpage I upload the files with the links updated but it still show the old ones, I even delete the webpage file on the server and it is still showing the page.
maybe my ISP is using some kind of proxy

links ok on my side.

explorer shows txid again instead of blockhash  
e.g.
"hash" : "1ff084a8c8c1b4e568f76d437139127ff6428046ba58f5bd9e2a6392feda5d8d",
explorer
"txid" : "f64d2458720ffd055ba2a7fc4168df9067606a207d4ba03fe172a0ea3e0edc8c"

Code:

getblockbynumber 39290 true

{
"hash" : "1ff084a8c8c1b4e568f76d437139127ff6428046ba58f5bd9e2a6392feda5d8d",
"confirmations" : 2,
"size" : 402,
"height" : 39290,
"version" : 7,
"merkleroot" : "0afd304f315a081e7b8299a31c9884d3727b86e3468f0be7b622925887105366",
"mint" : 6.63942585,
"time" : 1462176736,
"nonce" : 0,
"bits" : "1c009535",
"difficulty" : 439.22192842,
"blocktrust" : "1b73a8787a1",
"chaintrust" : "3875d9eb3d9ebc3e",
"previousblockhash" : "c8bc010cef4b6445f712a6bc3de9006b7f8d7b31ae2ceb55bf8326121bb97131",
"nextblockhash" : "57da28aa4aceeb442df29b86e4e20834ca0db171fa8469d9662c1c3f9db1b9b8",
"flags" : "proof-of-stake stake-modifier",
"proofhash" : "013055901f55127976b956348d76f50efa7a6f33993bac61d22bc0d517cbe8dd",
"entropybit" : 1,
"modifier" : "11625794c6785499",
"modifierv2" : "f1e6e51c96b6549d9ef150c0c63ada051b3126ca35202bedd01e411501678db7",
"tx" : [
{
"txid" : "a6d30198df46d1858c64e8e9e068a3e49fda8c571974047da8f38504258f600e",
"txid" : "a6d30198df46d1858c64e8e9e068a3e49fda8c571974047da8f38504258f600e",
"version" : 1,
"time" : 1462176736,
"locktime" : 0,
"vin" : [
{
"coinbase" : "037a9900",
"sequence" : 4294967295
}],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : "",
"type" : "nonstandard"
}}]},
{
"txid" : "f64d2458720ffd055ba2a7fc4168df9067606a207d4ba03fe172a0ea3e0edc8c",
"txid" : "f64d2458720ffd055ba2a7fc4168df9067606a207d4ba03fe172a0ea3e0edc8c",
"version" : 1,
"time" : 1462176736,
"locktime" : 0,
"vin" : [
{
"txid" : "9bba458cf206796c2fc494ce165dd3b14f3001b7d4ae1ac7917230d0baab7a41",
"vout" : 2,
"scriptSig" : {
"asm" : "3045022100c154e69363aaf8eb08c77aa636677819bb231b083d2ee88a30abcd6d15dbfb4d022029f84a40a5cb72580feab9e4eb7da547d6308e116226df782a5d46654aa5446001",
"hex" : "483045022100c154e69363aaf8eb08c77aa636677819bb231b083d2ee88a30abcd6d15dbfb4d022029f84a40a5cb72580feab9e4eb7da547d6308e116226df782a5d46654aa5446001"
},
"sequence" : 4294967295
}
],
"vout" : [
{
"value" : 0.00000000,
"n" : 0,
"scriptPubKey" : {
"asm" : "",
"hex" : "",
"type" : "nonstandard"
}},
{
"value" : 265.01414995,
"n" : 1,
"scriptPubKey" : {
"asm" : "034575d7c3569539977cc0f71e9b865c56847d444b0487205de30c0c61a69c73fd OP_CHECKSIG",
"hex" : "21034575d7c3569539977cc0f71e9b865c56847d444b0487205de30c0c61a69c73fdac",
"reqSigs" : 1,
"type" : "pubkey",
"addresses" : [
"6A6h5gpVB4J5v5AeXbBxiBeYBPWaHV6DVX"
]}}]}],
"signature" : "3045022100c4e601d2540b72f5c5749ef3a9410f1ae2f4ef58b16fb8c7f477fb8b580f42d10220725d195c7b78fa4a00c0804976a255fae25f7c63f0efe5d3f4c714f9c217dd62"
}

Thanks for checking the links
about the hashes I don't know how to fix that, I have been searching and have found nothing regarding this (or maybe I found and I couldn't understand it), So tomorrow I'll set up the explorer on my local net and try to find a solution.

BTW my daemon found like 30 orphan for every valid block the screen was full of orphans

[Nightz]

Opened the port on my router too guys you should connect a lot easier and stay synced.

My wallet has 19 connections now so far

[shimlbit]

locod getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560


thats what i got after resync

[3worlduser]

locod getblockhash 39327
f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560


thats what i got after resync

same here and in the explorer

04:38:55

getblockhash 39327


04:38:55

f1b18e6d3369b17009295d73c3c64edd2c4f9c0b76c404993e8e8ba8561fc560