✪✪✪ VIRTUAL COIN ✪✪✪ | P2P VIRTUAL MONEY | VC | X11 | ReLaunch: Date Feb 2017 ✪✪

[spicelord]

50

[1714751029]

1714751029

[1714751029]

1714751029

[1714751029]

1714751029

[alvarorecoba]

50

tks. just got 50 coins from solo mining but 3 minutes later, disappeared  So im out of this coin 

[exposebc]

I would sincerely appreciate any help getting my windows wallet to sync.  It has 0 connections to the network.

I have the latest wallet v0.9.1.6-g0-beta.  It runs OK but won't sync.  (note: sometimes when I start it it will seem to find 1 peer for like 10 seconds and then drops it)

After I unzip, the app's folder has 2 files:  virtualcoin9-1-6.exe and virtualcoin.CONF

Contents of virtualcoin.CONF

testnet=0
listen=1
server=1
daemon=1
gen=1
genproclimit=1
rpcuser=vcoinrpc
rpcpassword=myrandompassword
maxconnections=100
rcpallowip=127.0.0.1
rpcport=20950
port=2095

Anything else I should do?

Thanks in advance...

open the start menu and search %appdata% then click the roaming folder. In there you will find a virtualcoin folder. Open this and copy the virtualcoin.conf file that you extracted before to this location (make sure you overwrite the previous .conf file if there was one there) This did the trick for me

wow!  thanks you for the quick reply.  Sad to report though tahgt it did not work .  I also did this procedure;  https://bitcointalk.org/index.php?topic=557946.msg6259493#msg6259493. 

I just cannot seem to find any peers.

[apple_talk]

50

tks. just got 50 coins from solo mining but 3 minutes later, disappeared  So im out of this coin 

That is very odd, the dev enable high payout so user who lost coins mining pool that were unable to pay get it back or even more in short time.

I mined it & I am able to mine in 10-30 mins a block which is very good.

For solo mining, make sure you are using...
MINER: https://mega.co.nz/#!uAp12DYa!vhfp1wDb43mB1KCo_5ZfwXehYhBXeKcVYWbmkTB2ldg

Run in DOS window:-

Code:

sgminer -k darkcoin -o 127.0.0.1:20950 -u vcoinrpc -p myrandompassword -I 18 -g 4 -w 128

also look for current block in Debug Window,
then type in console ->
getblockhash <current block value>

* <current block value> is the current block # example
getblockhash 5000

Post your result here.

[apple_talk]

I would sincerely appreciate any help getting my windows wallet to sync.  It has 0 connections to the network.

I have the latest wallet v0.9.1.6-g0-beta.  It runs OK but won't sync.  (note: sometimes when I start it it will seem to find 1 peer for like 10 seconds and then drops it)

After I unzip, the app's folder has 2 files:  virtualcoin9-1-6.exe and virtualcoin.CONF

Contents of virtualcoin.CONF

testnet=0
listen=1
server=1
daemon=1
gen=1
genproclimit=1
rpcuser=vcoinrpc
rpcpassword=myrandompassword
maxconnections=100
rcpallowip=127.0.0.1
rpcport=20950
port=2095

Anything else I should do?

Thanks in advance...

open the start menu and search %appdata% then click the roaming folder. In there you will find a virtualcoin folder. Open this and copy the virtualcoin.conf file that you extracted before to this location (make sure you overwrite the previous .conf file if there was one there) This did the trick for me

wow!  thanks you for the quick reply.  Sad to report though tahgt it did not work .  I also did this procedure;  https://bitcointalk.org/index.php?topic=557946.msg6259493#msg6259493. 

I just cannot seem to find any peers.

ok Try this simple, follow line by line don't miss anything out.

1) Delete old exe file.

2) Go to virtualcoin folder (see below for location)

Code:

C:\Documents and Settings\[b]YourUserName[/b]\Application data\VirtualCoin (in XP)

C:\Users\[b]YourUserName[/b]\Appdata\Roaming\VirtualCoin (in Windows Vista and Windows 7)

3) Delete all files in that folder except wallet.dat

4) Download 9.1.6 version:
https://mega.co.nz/#!TUYTXIhC!bCvaTAlYKY9PTA751lF2rlPFSfiL8Zs6SDUFQviwKyI

5) Copy "virtualcoin.conf" to VirtualCoin folder (see 2 above).

6) Save virtualcoin9-1-6.exe to Desktop.

7) Run it.

When getting prompt by Firewall, check both options.
Example:-


9) Wait for it to sync. (my test shows takes 1-3 mins)

10) If it does not sync in 30 mins, your firewall in blocking port 2095. It may not work from office as they block all ports except 80/443.


Follow these 10 steps line by line, do not miss any steps.

We should make this sticky so users having issues can follow these directions.

[spicelord]

Apple do you know how I can solo mine from my rig to a wallet on another computer on the LAN? can't seem to get it

[v.coinz]

Apple do you know how I can solo mine from my rig to a wallet on another computer on the LAN? can't seem to get it

I can help you with that.

create shortcut of VirtualCoin exe on your desktop.

click on that shortcut & then properties.
In target type...
...(whatever the original location)\virtualcoin9-1-6.exe -server -port=2095 -rpcport=20950 -rpcallowip=192.168.0.*

change 192.168.0.* to IP address of your home PC. Example it could be 10.20.30.5, then it would be 10.20.30.*
just change last digit after dot to *

Now try it from another PC (miner) & point it to IP address where virtualcoin is running.

I have tested it & it 100% works if you do it right.

[v.coinz]

Also keep in mind their is a space before every -

[spicelord]

Do i point it to just the ip address or the ip address +port?

[SlientBit]

Apple do you know how I can solo mine from my rig to a wallet on another computer on the LAN? can't seem to get it

Very simple, for any coin

Just make sure the conf file has the following entries

server=1
listen=1
deamon=1
rpcuser="the user I want to use"
rpcpassword="the password I want to use"
rpcport="the RPC port I want to use" - say, 54321, for example (note: - make sure it's not in use already, doesn't have to be the default port, can be any port from 1-65535, but you should stick to high ports from 20000-65535, for example)
rpcconnect="the IPv4 address of the computer running the wallet" - say, for example, 192.168.1.2
rpcallowip="the IP or range of IPs that should be able to contact the wallet" - say, for example, my all internal network : 192.168.1.*

here's a complete example of the ports part for a wallet running in IP 192.168.1.2 and allowing every computer in the internal network to connect and mine

rpcport=20950
rpcconnect=192.168.1.2
rpcallowip=192.168.1.*


In the miner conf you should use url = 192.168.1.2:20950 , for this example

Remember that it's paramount that the wallet is in complete sync before you start and that it syncs every block as fast as possible, or else you'll solo mine for nothing

I usually help the miner computers by adding a second pool with a good stratum for the coin. This way, as soon as the stratum detects a new block, the miner stops the current work and requests new work, even if the wallet hasn't sync'd the new block yet
It avoids having your block rejected because someone found it first and minimizes the time your miners spend on useless work

Happy (solo) mining ;P

[v.coinz]

Do i point it to just the ip address or the ip address +port?

it will be ip address + port.

sgminer -k darkcoin -o 192.168.1.200:20950 -u vcoinrpc -p myrandompassword -I 18 -g 4 -w 128

Again, 192.168.1.200 above needs to change to your ip address.

If your wallet is not sync, miner will not start.

[spicelord]

This is not working for me. . .
Here is my miner .conf
{
"pools" : [
       {
                "url" : "192.168.1.15:20950",
                "user" : "vcoinrpc",
                "pass" : "myrandompassword"
        }
],

Here is my vcoin .conf
testnet=0
listen=1
server=1
daemon=1
gen=1
genproclimit=1
rpcuser=vcoinrpc
rpcpassword=myrandompassword
maxconnections=100
rpcconnect=192.168.1.15
rcpallowip=192.168.1.*
rpcport=20950
port=2095

[v.coinz]

This is not working for me. . .
Here is my miner .conf
{
"pools" : [
       {
                "url" : "192.168.1.15:20950",
                "user" : "vcoinrpc",
                "pass" : "myrandompassword"
        }
],

Here is my vcoin .conf
testnet=0
listen=1
server=1
daemon=1
gen=1
genproclimit=1
rpcuser=vcoinrpc
rpcpassword=myrandompassword
maxconnections=100
rpcconnect=192.168.1.15
rcpallowip=192.168.1.*
rpcport=20950
port=2095

SlientBit is somewhat correct, but it may not work.


Use following updated...

Code:

{
"pools" : [
       {
                "url" : "192.168.1.15:20950",
                "user" : "vcoinrpc",
                "pass" : "myrandompassword"
        }
],
"kernel" : "dark",

Code:

Here is my vcoin .conf
testnet=0
listen=1
server=1
daemon=1
gen=1
genproclimit=1
rpcuser=vcoinrpc
rpcpassword=myrandompassword
maxconnections=100
rpcconnect=*
rcpallowip=192.168.1.*
rpcport=20950
port=2095

You MUST also run
click on that shortcut & then properties.
In target type...
...(whatever the original location)\virtualcoin9-1-6.exe -server -port=2095 -rpcport=20950 -rpcallowip=192.168.1.*

since you mentioned IP address is 192.168.1.15, so use 192.168.1.*

Once it is sync, then start miner & make sure to use
"kernel" : "dark",

[SlientBit]

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

[spicelord]

Still doesn't work. says pool is slow/down or wrong credentials.

[Coindgr]

Hey, v. coinz

The new wallet doesn't sync at all, it can't find any nodes

Code:

from debug log:
[size=8pt]
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

(...)[/size]

Any suggestions? Pretty sure the firewall is not blocking the wallet

Same here, wallet opened for more than 10 hours and nothing

[v.coinz]

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.

[v.coinz]

Hey, v. coinz

The new wallet doesn't sync at all, it can't find any nodes

Code:

from debug log:
[size=8pt]
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

(...)[/size]

Any suggestions? Pretty sure the firewall is not blocking the wallet

Same here, wallet opened for more than 10 hours and nothing

Try my above suggestion, step by step.

[v.coinz]

Virtual Coin Windows Client 9.1.6 Released

Date Released: April 22nd, 2014

* Additional checkpoints added
* Reward 2x between 3000 to 6000.
* Fix Linux related issues with some 32bit OS. (Windows versions are not affected)


This is an Mandatory Update

DOWNLOAD LOCATION:
Package:
https://mega.co.nz/#!TUYTXIhC!bCvaTAlYKY9PTA751lF2rlPFSfiL8Zs6SDUFQviwKyI

[v.coinz]

When running re-indexing, this is how it will look like for about 30 secs...