|
joblessminer
|
 |
April 22, 2014, 08:38:48 PM |
|
Nice to see so much development going into this coin, instead of those pump & dump or IPO coins where dev disappear after cashing in.
SlientBit & Coindgr, did those steps helped with sync. I also ran, it took me less than 25 secs to sync from block 0. I am also using 9.1.6 version on Windows 7 64bit.
|
|
|
|
|
|
|
|
|
exposebc
Newbie
 Offline
Activity: 41
Merit: 0
|
|
April 22, 2014, 10:49:44 PM
Last edit: April 22, 2014, 11:12:49 PM by exposebc |
|
Hey, v. coinz The new wallet doesn't sync at all, it can't find any nodes  from debug log:
2014-04-22 17:31:10 9 addresses found from DNS seeds
2014-04-22 17:31:10 dnsseed thread exit
2014-04-22 17:32:11 Added 8 addresses from 127.0.0.1: 0 tried, 8 new
2014-04-22 17:32:11 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:32:16 connection timeout
2014-04-22 17:32:16 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:32:21 connection timeout
2014-04-22 17:32:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:27 connection timeout
2014-04-22 17:32:27 trying connection 32.124.193.54:2095 lastseen=195.0hrs
2014-04-22 17:32:32 connection timeout
2014-04-22 17:32:33 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:38 connection timeout
2014-04-22 17:32:38 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:43 connection timeout
2014-04-22 17:32:44 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:49 connection timeout
2014-04-22 17:32:49 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:54 connection timeout
2014-04-22 17:32:55 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:00 connection timeout
2014-04-22 17:33:00 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:05 connection timeout
2014-04-22 17:33:06 trying connection 72.71.155.107:2095 lastseen=264.5hrs
2014-04-22 17:33:11 connection timeout
2014-04-22 17:33:11 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:16 connection timeout
2014-04-22 17:33:17 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:22 connection timeout
2014-04-22 17:33:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:27 connection timeout
2014-04-22 17:33:28 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:33 connection timeout
2014-04-22 17:33:33 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:38 connection timeout
2014-04-22 17:33:39 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:33:44 connection timeout
2014-04-22 17:33:44 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:49 connection timeout
2014-04-22 17:33:50 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:55 connection timeout
(...)Any suggestions? Pretty sure the firewall is not blocking the wallet Ok, had one of my friend from outside downloaded & tested, it sync fine. Lets try this. backup your wallet.dat file. delete virtualcoin folder. delete old shortcuts & old exe file. download new exe (9.1.6) Launch it & then close it after 10 secs. copy the included virtualcoin.conf file in the "virtualcoin" folder. Launch again, based on my test, it should sync in few mins. Once it is sync. Close the application. overwrite your backup wallet.dat file back into virtualcoin folder. Start again & enjoy. TIP: To speedup the sync process you can add... addnode=virtualcoin.hopto.org addnode=178.249.125.94 in your virtualcoin.conf file. Once sync, you MUST remove both these entries from the file. I followed and refollowed the directions but no go. Finally, though, I got my windows wallet to sync ONLY after adding: addnode=virtualcoin.hopto.org addnode=178.249.125.94 to my virtualcoin.conf maybe there are just not enough wallets out there yet? |
|
|
|
|
|
v.coinz (OP)
|
|
April 22, 2014, 11:13:16 PM |
|
To make life easier, it is better not add nodes manually, as nodes are managed using DNS seeds. Which are updated regularly.
Glad your client is now sync. Make sure to delete those 2 nodes. As it leads to forking possibility in the future. Just check got around 92 nodes connected, but most are using non standard port (other than 2095), so that was the reason why you not able to connect, as your client from logs seems to try to connect on 2095. Once it connects to one node, rest of the nodes information gets downloaded into your PC as well.
hope this makes sense.
|
|
|
|
|
|
v.coinz (OP)
|
|
April 22, 2014, 11:18:19 PM |
|
Hey, v. coinz The new wallet doesn't sync at all, it can't find any nodes from debug log:
2014-04-22 17:31:10 9 addresses found from DNS seeds
2014-04-22 17:31:10 dnsseed thread exit
2014-04-22 17:32:11 Added 8 addresses from 127.0.0.1: 0 tried, 8 new
2014-04-22 17:32:11 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:32:16 connection timeout
2014-04-22 17:32:16 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:32:21 connection timeout
2014-04-22 17:32:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:27 connection timeout
2014-04-22 17:32:27 trying connection 32.124.193.54:2095 lastseen=195.0hrs
2014-04-22 17:32:32 connection timeout
2014-04-22 17:32:33 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:38 connection timeout
2014-04-22 17:32:38 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:43 connection timeout
2014-04-22 17:32:44 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:49 connection timeout
2014-04-22 17:32:49 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:54 connection timeout
2014-04-22 17:32:55 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:00 connection timeout
2014-04-22 17:33:00 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:05 connection timeout
2014-04-22 17:33:06 trying connection 72.71.155.107:2095 lastseen=264.5hrs
2014-04-22 17:33:11 connection timeout
2014-04-22 17:33:11 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:16 connection timeout
2014-04-22 17:33:17 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:22 connection timeout
2014-04-22 17:33:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:27 connection timeout
2014-04-22 17:33:28 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:33 connection timeout
2014-04-22 17:33:33 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:38 connection timeout
2014-04-22 17:33:39 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:33:44 connection timeout
2014-04-22 17:33:44 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:49 connection timeout
2014-04-22 17:33:50 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:55 connection timeout
(...)Any suggestions? Pretty sure the firewall is not blocking the wallet Ok, had one of my friend from outside downloaded & tested, it sync fine. Lets try this. backup your wallet.dat file. delete virtualcoin folder. delete old shortcuts & old exe file. download new exe (9.1.6) Launch it & then close it after 10 secs. copy the included virtualcoin.conf file in the "virtualcoin" folder. Launch again, based on my test, it should sync in few mins. Once it is sync. Close the application. overwrite your backup wallet.dat file back into virtualcoin folder. Start again & enjoy. TIP: To speedup the sync process you can add... addnode=virtualcoin.hopto.org addnode=178.249.125.94 in your virtualcoin.conf file. Once sync, you MUST remove both these entries from the file. I followed and refollowed the directions but no go. Finally, though, I got my windows wallet to sync ONLY after adding: addnode=virtualcoin.hopto.org addnode=178.249.125.94 to my virtualcoin.conf If anyone have issue sync the 1st time... add following nodes to your virtualcoin.conf file. addnode=virtualcoin.hopto.org
addnode=178.249.125.94
addnode=75.135.131.236
addnode=108.0.22.51 : Once sync & connected, delete the above nodes from the virtualcoin.conf file. Let your client choose the best node available. |
|
|
|
|
exposebc
Newbie
Offline
Activity: 41
Merit: 0
|
|
April 22, 2014, 11:32:40 PM |
|
Hey, v. coinz The new wallet doesn't sync at all, it can't find any nodes from debug log:
2014-04-22 17:31:10 9 addresses found from DNS seeds
2014-04-22 17:31:10 dnsseed thread exit
2014-04-22 17:32:11 Added 8 addresses from 127.0.0.1: 0 tried, 8 new
2014-04-22 17:32:11 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:32:16 connection timeout
2014-04-22 17:32:16 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:32:21 connection timeout
2014-04-22 17:32:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:27 connection timeout
2014-04-22 17:32:27 trying connection 32.124.193.54:2095 lastseen=195.0hrs
2014-04-22 17:32:32 connection timeout
2014-04-22 17:32:33 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:38 connection timeout
2014-04-22 17:32:38 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:43 connection timeout
2014-04-22 17:32:44 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:49 connection timeout
2014-04-22 17:32:49 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:54 connection timeout
2014-04-22 17:32:55 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:00 connection timeout
2014-04-22 17:33:00 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:05 connection timeout
2014-04-22 17:33:06 trying connection 72.71.155.107:2095 lastseen=264.5hrs
2014-04-22 17:33:11 connection timeout
2014-04-22 17:33:11 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:16 connection timeout
2014-04-22 17:33:17 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:22 connection timeout
2014-04-22 17:33:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:27 connection timeout
2014-04-22 17:33:28 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:33 connection timeout
2014-04-22 17:33:33 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:38 connection timeout
2014-04-22 17:33:39 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:33:44 connection timeout
2014-04-22 17:33:44 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:49 connection timeout
2014-04-22 17:33:50 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:55 connection timeout
(...)Any suggestions? Pretty sure the firewall is not blocking the wallet Ok, had one of my friend from outside downloaded & tested, it sync fine. Lets try this. backup your wallet.dat file. delete virtualcoin folder. delete old shortcuts & old exe file. download new exe (9.1.6) Launch it & then close it after 10 secs. copy the included virtualcoin.conf file in the "virtualcoin" folder. Launch again, based on my test, it should sync in few mins. Once it is sync. Close the application. overwrite your backup wallet.dat file back into virtualcoin folder. Start again & enjoy. TIP: To speedup the sync process you can add... addnode=virtualcoin.hopto.org addnode=178.249.125.94 in your virtualcoin.conf file. Once sync, you MUST remove both these entries from the file. I followed and refollowed the directions but no go. Finally, though, I got my windows wallet to sync ONLY after adding: addnode=virtualcoin.hopto.org addnode=178.249.125.94 to my virtualcoin.conf If anyone have issue sync the 1st time... add following nodes to your virtualcoin.conf file. addnode=virtualcoin.hopto.org
addnode=178.249.125.94
addnode=75.135.131.236
addnode=108.0.22.51 : Once sync & connected, delete the above nodes from the virtualcoin.conf file. Let your client choose the best node available. done... ...and restarted all good - found 6 nodes right away! 2 questions more please: 1) why would the wallet crank my processor utilization to 100%? 2) suppose my 2645.3 VC at minep.it are likly to show up? |
|
|
|
|
trademark
Legendary
Offline
Activity: 1932
Merit: 1003
|
|
April 23, 2014, 12:10:35 AM |
|
Hi Dev,
I noticed the 2x block reward has been reduced from block 40,000 to 6,000. Is this correct? If so, great move.
|
|
|
|
|
|
spicelord
|
|
April 23, 2014, 02:06:32 AM |
|
Tales is back on the right chain? Yes?
|
|
|
|
|
spicelord
|
|
April 23, 2014, 02:09:26 AM |
|
done...
...and restarted all good - found 6 nodes right away!
2 questions more please:
1) why would the wallet crank my processor utilization to 100%?
2) suppose my 2645.3 VC at minep.it are likly to show up?
Go to help debug console then type in setgenerate false 0 |
|
|
|
|
v.coinz (OP)
|
|
April 23, 2014, 02:15:09 AM |
|
Hey, v. coinz The new wallet doesn't sync at all, it can't find any nodes from debug log:
2014-04-22 17:31:10 9 addresses found from DNS seeds
2014-04-22 17:31:10 dnsseed thread exit
2014-04-22 17:32:11 Added 8 addresses from 127.0.0.1: 0 tried, 8 new
2014-04-22 17:32:11 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:32:16 connection timeout
2014-04-22 17:32:16 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:32:21 connection timeout
2014-04-22 17:32:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:27 connection timeout
2014-04-22 17:32:27 trying connection 32.124.193.54:2095 lastseen=195.0hrs
2014-04-22 17:32:32 connection timeout
2014-04-22 17:32:33 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:38 connection timeout
2014-04-22 17:32:38 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:43 connection timeout
2014-04-22 17:32:44 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:32:49 connection timeout
2014-04-22 17:32:49 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:32:54 connection timeout
2014-04-22 17:32:55 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:00 connection timeout
2014-04-22 17:33:00 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:05 connection timeout
2014-04-22 17:33:06 trying connection 72.71.155.107:2095 lastseen=264.5hrs
2014-04-22 17:33:11 connection timeout
2014-04-22 17:33:11 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:16 connection timeout
2014-04-22 17:33:17 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:22 connection timeout
2014-04-22 17:33:22 trying connection 175.39.141.62:2095 lastseen=237.7hrs
2014-04-22 17:33:27 connection timeout
2014-04-22 17:33:28 trying connection 123.116.19.50:2095 lastseen=328.6hrs
2014-04-22 17:33:33 connection timeout
2014-04-22 17:33:33 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:38 connection timeout
2014-04-22 17:33:39 trying connection 102.206.16.50:2095 lastseen=174.6hrs
2014-04-22 17:33:44 connection timeout
2014-04-22 17:33:44 trying connection 166.32.99.192:2095 lastseen=263.9hrs
2014-04-22 17:33:49 connection timeout
2014-04-22 17:33:50 trying connection 44.83.252.162:2095 lastseen=272.5hrs
2014-04-22 17:33:55 connection timeout
(...)Any suggestions? Pretty sure the firewall is not blocking the wallet Ok, had one of my friend from outside downloaded & tested, it sync fine. Lets try this. backup your wallet.dat file. delete virtualcoin folder. delete old shortcuts & old exe file. download new exe (9.1.6) Launch it & then close it after 10 secs. copy the included virtualcoin.conf file in the "virtualcoin" folder. Launch again, based on my test, it should sync in few mins. Once it is sync. Close the application. overwrite your backup wallet.dat file back into virtualcoin folder. Start again & enjoy. TIP: To speedup the sync process you can add... addnode=virtualcoin.hopto.org addnode=178.249.125.94 in your virtualcoin.conf file. Once sync, you MUST remove both these entries from the file. I followed and refollowed the directions but no go. Finally, though, I got my windows wallet to sync ONLY after adding: addnode=virtualcoin.hopto.org addnode=178.249.125.94 to my virtualcoin.conf If anyone have issue sync the 1st time... add following nodes to your virtualcoin.conf file. addnode=virtualcoin.hopto.org
addnode=178.249.125.94
addnode=75.135.131.236
addnode=108.0.22.51 : Once sync & connected, delete the above nodes from the virtualcoin.conf file. Let your client choose the best node available. done... ...and restarted all good - found 6 nodes right away! 2 questions more please: 1) why would the wallet crank my processor utilization to 100%? 2) suppose my 2645.3 VC at minep.it are likly to show up? What kind of CPU are you using? 2nd, change genproclimit=1 (in conf file) or remove this line altogether. Their is no other option that I know you can do, once this version is stable will release 64bit native version also. |
|
|
|
|
|
v.coinz (OP)
|
|
April 23, 2014, 02:16:21 AM |
|
Hi Dev,
I noticed the 2x block reward has been reduced from block 40,000 to 6,000. Is this correct? If so, great move.
yes, it was needed or it would kill the coin & it's exchange rate. |
|
|
|
|
exposebc
Newbie
Offline
Activity: 41
Merit: 0
|
|
April 23, 2014, 02:19:39 AM |
|
done...
...and restarted all good - found 6 nodes right away!
2 questions more please:
1) why would the wallet crank my processor utilization to 100%?
2) suppose my 2645.3 VC at minep.it are likly to show up?
Go to help debug console then type in setgenerate false 0 yep fixed the 100% issue -- thank u! |
|
|
|
|
|
spicelord
|
|
April 23, 2014, 02:19:55 AM |
|
I think tales is on wrong chain still. minep.it has same hashrate as the wallet shows so looks good to mine there.
|
|
|
|
|
spicelord
|
|
April 23, 2014, 02:20:46 AM |
|
What kind of CPU are you using?
2nd, change
genproclimit=1 (in conf file)
or remove this line altogether.
Their is no other option that I know you can do, once this version is stable will release 64bit native version also.
His wallet was cpu mining in the background. Happens sometimes with wallets. They autostart cpu mining |
|
|
|
exposebc
Newbie
Offline
Activity: 41
Merit: 0
|
|
April 23, 2014, 02:30:02 AM |
|
I think tales is on wrong chain still. minep.it has same hashrate as the wallet shows so looks good to mine there.
they are both on block 5414 -current block isnt that unlikely if either is on a wrong chain? |
|
|
|
|
|
spicelord
|
|
April 23, 2014, 03:09:15 AM |
|
You are right. They both appear to be on same block but neither is generating new blocks in the pool. I find this odd because I am mining at over 4 mhash which is supposedly 1/6 of the total net hash on minep.it and there has not been any new blocks. I've been mining for over a half hour.
|
|
|
|
|
v.coinz (OP)
|
|
April 23, 2014, 03:19:59 AM |
|
I think tales is on wrong chain still. minep.it has same hashrate as the wallet shows so looks good to mine there.
they are both on block 5414 -current block isnt that unlikely if either is on a wrong chain? I think the only way to confirm is if they provide hash of example 5400 block. Otherwise it looks likely that it is running on same chain if block # change same time & it is on same block. Please use caution, I as a dev does not have any control over the pools. |
|
|
|
|
apple_talk
Sr. Member
Offline
Activity: 473
Merit: 250
"Proof-of-Asset Protocol"
|
|
April 23, 2014, 03:22:09 AM |
|
|
|
|
|
apple_talk
Sr. Member
Offline
Activity: 473
Merit: 250
"Proof-of-Asset Protocol"
|
|
April 23, 2014, 03:27:54 AM |
|
I think tales is on wrong chain still. minep.it has same hashrate as the wallet shows so looks good to mine there.
they are both on block 5414 -current block isnt that unlikely if either is on a wrong chain? I think the only way to confirm is if they provide hash of example 5400 block. Otherwise it looks likely that it is running on same chain if block # change same time & it is on same block. Please use caution, I as a dev does not have any control over the pools.
|
|
|
|
|
Poll
