CapnBDL
|
|
April 08, 2016, 08:59:31 PM |
|
Umm..I did this update but the wallet says it is 2.1.0. and not 2.2.0...was this just a 'finger-typing' error? CapnBDL
|
|
|
|
CryptoMan2014
|
|
April 08, 2016, 09:37:46 PM |
|
Dev, could it be preparation for something bigger? Whahaha, he's a "dev", not a Dev. He needs a team to bring something bigger. Make Amsterdam proud "Kees"
|
|
|
|
keesdewit (OP)
|
|
April 09, 2016, 12:19:26 PM |
|
Umm..I did this update but the wallet says it is 2.1.0. and not 2.2.0...was this just a 'finger-typing' error? CapnBDL Your right. It should be version 2.1.0
|
|
|
|
Dusterious
Newbie
Offline
Activity: 28
Merit: 0
|
|
April 09, 2016, 08:16:10 PM |
|
After the wintersleep of bear "Kees" we are very happy to see some movement. Although its just a small bit
|
|
|
|
alexxynn
|
|
April 12, 2016, 04:22:04 AM |
|
bloody hell, wallet syncing slower than hbn, virtually unusable
plz share some addnodes
77.110.151.17 213.108.119.84 75.130.163.51 24.160.59.242 85.214.152.3 46.188.4.74 74.77.15.47 68.71.58.226 184.6.147.2 178.158.146.102
|
|
|
|
metamorphin
Legendary
Offline
Activity: 1106
Merit: 1004
No risk, no fun!
|
|
April 12, 2016, 06:46:39 PM |
|
bloody hell, wallet syncing slower than hbn, virtually unusable
plz share some addnodes
77.110.151.17 213.108.119.84 75.130.163.51 24.160.59.242 85.214.152.3 46.188.4.74 74.77.15.47 68.71.58.226 184.6.147.2 178.158.146.102 Please be more precise: 1. Most of these nodes means, that you still have 1 or 2 connections? 2. Orphans often created, because the ppl unlocked their wallets during the syncing-phase. NEVER unlock ur wallet, if u r not ready with syncing! greetz Steve thanks, but didn't help, most of those nodes don't connect, and log shows wallet is processing enormous amount of orphans, dev or an expert, wtf is that ?
|
|
|
|
metamorphin
Legendary
Offline
Activity: 1106
Merit: 1004
No risk, no fun!
|
|
April 12, 2016, 07:51:43 PM |
|
Please be more precise:
1. Most of these nodes means, that you still have 1 or 2 connections?
2. Orphans often created, because the ppl unlocked their wallets during the syncing-phase. NEVER unlock ur wallet, if u r not ready with syncing!
greetz Steve
precisely: 1) no matter what nodes i add, i always have 3 and only these 3 connected: "addr" : "184.6.147.2:61510", "addr" : "213.108.119.84:61510", "addr" : "68.71.58.226:61510", 2) i'm syncing empty wallet from block zero, as far as 17 weeks ago it becomes unbelievably laggy with tons of that shit in log: ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 660, prev=5935c9d5b92d86b7487510becb0ec200ecd30481889db76844c8bd3348ce9bfc SetBestChain: new best=13a3c169c9b81b0154c8cfb25c5a08a77a8a8f9cae293f5da20e2c29f1246b1b height=104800 trust=12138951290491403604 blocktrust=722784681960337 date=12/13/15 06:45:52 ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 661, prev=f9a23df16fa50358258aa62c5c25427c2880b8c6aa36c0f0cdb3093da05505aa SetBestChain: new best=c16df724b4b0ab1d8097d58fe27ad24b4e37869da75dde43c531211686798426 height=104801 trust=12138951314583802354 blocktrust=24092398750 date=12/13/15 06:46:20 ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 662, prev=b26535d1028a3e7685bd8c3cd230847df4e5eeef50c288815a823dd7e8461935 SetBestChain: new best=b71cf80091e369dbb81706cbddd05eec5e1f7006ee99dc2e6968cbf2c582f510 height=104802 trust=12139834718189139337 blocktrust=883403605336983 date=12/13/15 06:47:12 and as far as 15 weeks ago it practically stops syncing eating up to 100% cpu Great input, now dev can work on it and have a look... Greetz Steve
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 10:44:18 AM |
|
Please be more precise:
1. Most of these nodes means, that you still have 1 or 2 connections?
2. Orphans often created, because the ppl unlocked their wallets during the syncing-phase. NEVER unlock ur wallet, if u r not ready with syncing!
greetz Steve
precisely: 1) no matter what nodes i add, i always have 3 and only these 3 connected: "addr" : "184.6.147.2:61510", "addr" : "213.108.119.84:61510", "addr" : "68.71.58.226:61510", 2) i'm syncing empty wallet from block zero, as far as 17 weeks ago it becomes unbelievably laggy with tons of that shit in log: ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 660, prev=5935c9d5b92d86b7487510becb0ec200ecd30481889db76844c8bd3348ce9bfc SetBestChain: new best=13a3c169c9b81b0154c8cfb25c5a08a77a8a8f9cae293f5da20e2c29f1246b1b height=104800 trust=12138951290491403604 blocktrust=722784681960337 date=12/13/15 06:45:52 ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 661, prev=f9a23df16fa50358258aa62c5c25427c2880b8c6aa36c0f0cdb3093da05505aa SetBestChain: new best=c16df724b4b0ab1d8097d58fe27ad24b4e37869da75dde43c531211686798426 height=104801 trust=12138951314583802354 blocktrust=24092398750 date=12/13/15 06:46:20 ProcessBlock: ACCEPTED ProcessBlock: ORPHAN BLOCK 662, prev=b26535d1028a3e7685bd8c3cd230847df4e5eeef50c288815a823dd7e8461935 SetBestChain: new best=b71cf80091e369dbb81706cbddd05eec5e1f7006ee99dc2e6968cbf2c582f510 height=104802 trust=12139834718189139337 blocktrust=883403605336983 date=12/13/15 06:47:12 and as far as 15 weeks ago it practically stops syncing eating up to 100% cpu Great input, now dev can work on it and have a look... Greetz Steve Nothing out of the ordinary in that debug log. I did notice that the sync process is very slow. Still looking for the cause. It seems like theres an error in the peer to peer distribution.
|
|
|
|
SlowGrowth
|
|
April 13, 2016, 03:04:45 PM |
|
any bootstrap? cant sync for 3 days now
|
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 08:26:54 PM |
|
Nothing out of the ordinary in that debug log. I did notice that the sync process is very slow. Still looking for the cause. It seems like theres an error in the peer to peer distribution.
dev you are a miracle. importing blocks from bootstrap goes not any faster than p2p, with the same orphan shit Well, bootstrap and p2p are 2 whole different things.
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 08:32:49 PM |
|
Nothing out of the ordinary in that debug log. I did notice that the sync process is very slow. Still looking for the cause. It seems like theres an error in the peer to peer distribution.
dev you are a miracle. importing blocks from bootstrap goes not any faster than p2p, with the same orphan shit Well, bootstrap and p2p are 2 whole different things. and ? You compare them. Its like comparing apples with bananas. Both are fruit though. Btw I don't like your tone. I hope you have better social features in real life.
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 08:38:34 PM |
|
Nothing out of the ordinary in that debug log. I did notice that the sync process is very slow. Still looking for the cause. It seems like theres an error in the peer to peer distribution.
dev you are a miracle. importing blocks from bootstrap goes not any faster than p2p, with the same orphan shit Well, bootstrap and p2p are 2 whole different things. and ? You compare them. Its like comparing apples with bananas. Both are fruit though. Btw I don't like your tone. I hope you have better social features in real life. i don't compare anything, all i want is sync that shit. and i see that no matter what source is - it's extremeley slow due to enormous amount of orphan processing, and ldb in the process is bloated to 400m+ over 140m blk0001.dat which looks not right as well So whats your solution? I've been breaking my head about this for some time, so if you have a better cause than p2p please let me know.
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 08:48:05 PM |
|
Nothing out of the ordinary in that debug log. I did notice that the sync process is very slow. Still looking for the cause. It seems like theres an error in the peer to peer distribution.
dev you are a miracle. importing blocks from bootstrap goes not any faster than p2p, with the same orphan shit Well, bootstrap and p2p are 2 whole different things. and ? You compare them. Its like comparing apples with bananas. Both are fruit though. Btw I don't like your tone. I hope you have better social features in real life. i don't compare anything, all i want is sync that shit. and i see that no matter what source is - it's extremeley slow due to enormous amount of orphan processing, and ldb in the process is bloated to 400m+ over 140m blk0001.dat which looks not right as well So whats your solution? solution to my task is coming in a few hours, i'll sync, take stuck coins, sell, and forget. it was all about mining some amount to local addy, sorry if my tone is not what you'r used to, i'm purely practical Thanks for your extensive help on this! Guess I have to keep looking by myself.
|
|
|
|
cryptonit
Legendary
Offline
Activity: 3052
Merit: 1053
bit.diamonds | uNiq.diamonds
|
|
April 13, 2016, 09:05:39 PM |
|
suggest u look where the orphan blocks come from and solve that and u will sync nice...... old not updated wallets?
release wallet that blocks old wallet version
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 09:08:19 PM |
|
suggest u look where the orphan blocks come from and solve that and u will sync nice...... old not updated wallets?
release wallet that blocks old wallet version
Thanks for the advice. I will look into this.
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 09:20:18 PM |
|
dev, if any codebase may seem near to ams i guess it would be bloodcoin. you may find it useful to compare, if issue is in the code and not some screwed node, or pos-related bod is cheap and not well-known, but it's running perfectly well
I will do some comparing. AMS is a transfercoin clone so I will compare that as well. Many thanks! Maybe this will bring me a bit further.
|
|
|
|
keesdewit (OP)
|
|
April 13, 2016, 09:27:52 PM |
|
dev, if any codebase may seem near to ams i guess it would be bloodcoin. you may find it useful to compare, if issue is in the code and not some screwed node, or pos-related bod is cheap and not well-known, but it's running perfectly well
I will do some comparing. AMS is a transfercoin clone so I will compare that as well. Many thanks! Maybe this will bring me a bit further. and if you wanna know what we do with flawed dutch coins check lftc coin thread, amuse yourself, and prepare for the worst The difference is that AMS is not a scam coin. I dont make a penny here. This costs me time and money instead.
|
|
|
|
keesdewit (OP)
|
|
April 14, 2016, 10:43:23 AM |
|
dev, sync revealed that the rate of orphans production is somehow proportional to amount of blocks or more likely tx's. that's why it was unnoticable during early growth. check POS code the rate will only grow until complete *&#*@(&#
Thanks, will check.
|
|
|
|
midnight_miner
|
|
April 15, 2016, 12:48:15 AM |
|
{ "addr" : "68.71.58.226", "addrlocal" : "68.235.184.68:51806", "services" : "00000001", "lastsend" : 1460680961, "lastrecv" : 1460680963, "bytessent" : 1305, "bytesrecv" : 18852, "conntime" : 1460680961, "pingtime" : 0.19231000, "version" : 61401, "subver" : "/Inferno:2.1.0/", "inbound" : false, "startingheight" : 416594, "banscore" : 0, "syncnode" : true }, { "addr" : "68.71.58.229", "addrlocal" : "68.235.184.68:51816", "services" : "00000001", "lastsend" : 1460680969, "lastrecv" : 1460680969, "bytessent" : 284, "bytesrecv" : 765, "conntime" : 1460680968, "pingtime" : 0.17139100, "version" : 61401, "subver" : "/Inferno:2.1.0/", "inbound" : false, "startingheight" : 416594, "banscore" : 0, "syncnode" : false }
Permanent nodes are updated to latest wallet. addnode=ams1.midnightminer.net addnode=ams2.midnightminer.net
|
|
|
|
|