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

[v.coinz]

I am seeing lot of positive interest in the X11 based Virtual Coin, but we do need coders & developer to review the code before we could launch. Any volunteer willing to provide feedback/input before the launch. At present it will not be before 2015...2016 a ASIC miner comes out, so future is bright. Users will needs to use SPH-MINER to mine the coin.
 

You can download current source code from

Code:

https://mega.co.nz/#!zVQwwIbK!IvE-Has6Izr1pTTOCDv_7CRFBdy-U9Nf0YrbvISdI_k

It is a re-launch fresh with all new modded code based on X11.

To be open & fair, source code is provided upfront even before the launch, so you guys can review & provide any input to further improve it
Once code is stable in next few days, Launch date will be posted at least 2 days in advance.

The current code is designed to be fair to everyone & allows CPU/GPU miners only.

yes, we do need github, if someone with experience would like to volunteer & upload this code, please contact me.

I am with you, this is the right approach, once ASIC Scrypt miner is out do you think scrypt coins like Litecoin will survive? their won't be any difference left between mining bitcoin or litecoin. I see most if not all coins never disclose source before launch so they can privately mine it. At least you are honest, we all can see the source code. I will 100% mine it. I hope more developers join you & further improve the code.

To all user making bad comments, don't just speculate stuff, maybe go through the code & then point out. I know some guys like "vann" have interest in a specific coin, so it is in their interest to bash all other coins. I suggest you stop spreading these rumors. You review the code & then point of issues based on it.

[NamoCoin]

NaMo Coin launch was cancelled due to poor support, I have requested users of my coin to support X11 based coin like yours which happens to be No Premine.

I wish you & your Coin team good luck.

[vrm86]

http://vc.crypto-hamsters.com/index.php?page=statistics&action=blocks

Is this beta testing, or....

[v.coinz]

http://vc.crypto-hamsters.com/index.php?page=statistics&action=blocks

Is this beta testing, or....

It is not launched yet, above is based on older scrypt version which is no longer supported. Just before launch blocks will be reset to 0. Please feel free to download source code & test it.

[v.coinz]

 

Reward Announcement

One user will be randomly selected for 100 Coin bonus (anyone who will be posting reply after this post), I will pitch in coins for the prize. Post must be based on feedback, suggestion or any useful contribution to Virtual Coin.

[e1ghtSpace]

Looks great, i'm glad you chose X11. I was supporting this coin from the start and had 70000 coins in the old wallet. Too bad they are all worthless.
It looks like this version has more support than the old one so good luck!

By the way, when we are mining with sph-miner, do we act as if the wallet was darkcoin? like this:

Code:

sgminer -k darkcoin -o <host>:<port> -u <user> -p <password>

Thanks,

e1ghtSpace

[joblessminer]

Virtual Coin will be the future not Litecoin, they are stubborn to adopt o new Scrypt-N.

Virtual Coin = Fair Coin

Lets all give this Coin fair chance to succeed, so far I don't find anything negative about it.

[apple_talk]

Notice issue in main.cpp

Code:

  if (true && block.GetHash() != hashGenesisBlock)
            {
                  printf("Searching for genesis block...\n");
                  // This will figure out a valid hash and Nonce if you're
                  // creating a different genesis block:
                  uint256 hashTarget = CBigNum().SetCompact(block.nBits).getuint256();
                  uint256 thash;
                  char scratchpad[SCRYPT_SCRATCHPAD_SIZE];

                  loop
                  {
      #if defined(USE_SSE2)
                      // Detection would work, but in cases where we KNOW it always has SSE2,
                      // it is faster to use directly than to use a function pointer or conditional.
      #if defined(_M_X64) || defined(__x86_64__) || defined(_M_AMD64) || (defined(MAC_OSX) && defined(__i386__))
                      // Always SSE2: x86_64 or Intel MacOS X
                      scrypt_1024_1_1_256_sp_sse2(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #else
                      // Detect SSE2: 32bit x86 Linux or Windows
                      scrypt_1024_1_1_256_sp(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #endif
      #else
                      // Generic scrypt
                      scrypt_1024_1_1_256_sp_generic(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #endif
                      if (thash <= hashTarget)
                          break;
                      if ((block.nNonce & 0xFFF) == 0)
                      {
                          printf("nonce %08X: hash = %s (target = %s)\n", block.nNonce, thash.ToString().c_str(), hashTarget.ToString().c_str());
                      }
                      ++block.nNonce;
                      if (block.nNonce == 0)
                      {
                          printf("NONCE WRAPPED, incrementing time\n");
                          ++block.nTime;
                      }
                  }

            printf("block.nTime = %u \n", block.nTime);
            printf("block.nNonce = %u \n", block.nNonce);
            printf("block.GetHash = %s\n", block.GetHash().ToString().c_str());


               }

May be someone familiar with C++ code can clarify?

[v.coinz]

Notice issue in main.cpp

Code:

  if (true && block.GetHash() != hashGenesisBlock)
            {
                  printf("Searching for genesis block...\n");
                  // This will figure out a valid hash and Nonce if you're
                  // creating a different genesis block:
                  uint256 hashTarget = CBigNum().SetCompact(block.nBits).getuint256();
                  uint256 thash;
                  char scratchpad[SCRYPT_SCRATCHPAD_SIZE];

                  loop
                  {
      #if defined(USE_SSE2)
                      // Detection would work, but in cases where we KNOW it always has SSE2,
                      // it is faster to use directly than to use a function pointer or conditional.
      #if defined(_M_X64) || defined(__x86_64__) || defined(_M_AMD64) || (defined(MAC_OSX) && defined(__i386__))
                      // Always SSE2: x86_64 or Intel MacOS X
                      scrypt_1024_1_1_256_sp_sse2(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #else
                      // Detect SSE2: 32bit x86 Linux or Windows
                      scrypt_1024_1_1_256_sp(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #endif
      #else
                      // Generic scrypt
                      scrypt_1024_1_1_256_sp_generic(BEGIN(block.nVersion), BEGIN(thash), scratchpad);
      #endif
                      if (thash <= hashTarget)
                          break;
                      if ((block.nNonce & 0xFFF) == 0)
                      {
                          printf("nonce %08X: hash = %s (target = %s)\n", block.nNonce, thash.ToString().c_str(), hashTarget.ToString().c_str());
                      }
                      ++block.nNonce;
                      if (block.nNonce == 0)
                      {
                          printf("NONCE WRAPPED, incrementing time\n");
                          ++block.nTime;
                      }
                  }

            printf("block.nTime = %u \n", block.nTime);
            printf("block.nNonce = %u \n", block.nNonce);
            printf("block.GetHash = %s\n", block.GetHash().ToString().c_str());


               }

May be someone familiar with C++ code can clarify?

Appreciate your feedback. I will review the code. That was the reason why it was in beta testing to iron out any issues.

[trademark]

Nice, X11 coin. Looking forward to the launch. Please try to release it on a weekend if possible. Thank you.

[e1ghtSpace]

Nice, X11 coin. Looking forward to the launch. Please try to release it on a weekend if possible. Thank you.

And at a time where people in Austraila are awake. (It's 7:00am now)

[bestsponsor]

"Target Difficulty: KGW (Gravity Well)" -it`s not good. DGW is better.

[Eastwind]

Darkcoin is discussing airdrop at the moment to mitigate the effect of instant mining.

In order to reduce the instant mining, I would suggest proportional block reward according to difficulty in the first few, say 5000 blocks. For example, set the starting difficulty to be 0.01, but the block reward is 1, when the difficulty is increased to 1, the reward is 10. The relationship between block reward and difficulty does not have to be linear.

This will give time to the miners and pools to set up their wallets and mining software. They are not much disadvantaged by coming to the mining just a little bit late.

[e1ghtSpace]

Darkcoin is discussing airdrop at the moment to mitigate the effect of instant mining.

In order to reduce the instant mining, I would suggest proportional block reward according to difficulty in the first few, say 5000 blocks. For example, set the starting difficulty to be 0.01, but the block reward is 1, when the difficulty is increased to 1, the reward is 10. The relationship between block reward and difficulty does not have to be linear.

This will give time to the miners and pools to set up their wallets and mining software. They are not much disadvantaged by coming to the mining just a little bit late.

But then it will disadvantage little solo miners. Like me.

[Eastwind]

Darkcoin is discussing airdrop at the moment to mitigate the effect of instant mining.

In order to reduce the instant mining, I would suggest proportional block reward according to difficulty in the first few, say 5000 blocks. For example, set the starting difficulty to be 0.01, but the block reward is 1, when the difficulty is increased to 1, the reward is 10. The relationship between block reward and difficulty does not have to be linear.

This will give time to the miners and pools to set up their wallets and mining software. They are not much disadvantaged by coming to the mining just a little bit late.

But then it will disadvantage little solo miners. Like me.

KimoCoin has a increasing reward system initially giving people days to adjust. There is no complaint about that.

https://bitcointalk.org/index.php?topic=524216.0

[MineP.it]

Keep the MinePit pool in the list - we will relaunch wallet etc when the new code is ready to be released.

Thanks

P.S. You can use the new URL: https://www.minep.it/pool/vc/

[Eastwind]

Is the 30 mins block target time too long? 10 mins would be alright.

[scam_exposer]

How about you just cancel the launch of this coin.  It's not needed and will be just another one of many crap coins that currently exist.

[mpalenciac]

How about you just cancel the launch of this coin.  It's not needed and will be just another one of many crap coins that currently exist.

How about you just shoot yourself? Stupid cunt troll

[e1ghtSpace]

Is the 30 mins block target time too long? 10 mins would be alright.

I have to agree. 30 minutes is a long time. 3 minutes would be good. 10 max. 30 is just way too long.