[ANN] Velocitycoin- Client Update 1.2.0- Important Update Immediately

[peterlustig]

Nodes:

Code:

19:05:24

getpeerinfo


19:05:24

[
{
"addr" : "62.61.44.66:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339330,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 445,
"banscore" : 0
},
{
"addr" : "24.189.239.125:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339352,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 458,
"banscore" : 0
},
{
"addr" : "46.229.50.42:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339368,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 460,
"banscore" : 0
},
{
"addr" : "49.73.212.216:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340317,
"conntime" : 1388339374,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 460,
"banscore" : 0
},
{
"addr" : "206.72.193.8:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340319,
"conntime" : 1388339422,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 468,
"banscore" : 0
},
{
"addr" : "46.55.152.33:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339427,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 471,
"banscore" : 0
},
{
"addr" : "70.118.129.149:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340317,
"conntime" : 1388339433,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 471,
"banscore" : 0
},
{
"addr" : "84.54.172.244:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339533,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 491,
"banscore" : 0
}
]

[VelocityCoin]

addnode=77.247.181.162
addnode=91.77.102.87
addnode=91.154.202.96
addnode=78.205.83.28
addnode=87.219.35.151
addnode=121.221.31.187

Updated in op. The windows client in UPNP enabled.

[dr_yan_yan]

so... "addnode" is not a legitimate command and the author is providing no nodes for mining.  Looks like the first couple people might have got a connection and now everybody else is SOL.  Can we consider this coin trash already?

Wow you girls whinge a lot.

[OrkneyCoiner]

addnode=77.247.181.162
addnode=91.77.102.87
addnode=91.154.202.96
addnode=78.205.83.28
addnode=87.219.35.151
addnode=121.221.31.187

Updated in op. The windows client in UPNP enabled.

thx!

[peterlustig]

@ those who will cry QQcoin clone for sure:
N-Factor seems to what be QQCoin has now, getting 3.3MH/s with Velcoin when I got 5MH/s with QQ aat the start. Also diff adjustment is way more radical, no orphans!

[OrkneyCoiner]

Nodes:

Code:

19:05:24

getpeerinfo


19:05:24

[
{
"addr" : "62.61.44.66:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339330,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 445,
"banscore" : 0
},
{
"addr" : "24.189.239.125:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339352,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 458,
"banscore" : 0
},
{
"addr" : "46.229.50.42:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339368,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 460,
"banscore" : 0
},
{
"addr" : "49.73.212.216:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340317,
"conntime" : 1388339374,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 460,
"banscore" : 0
},
{
"addr" : "206.72.193.8:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340319,
"conntime" : 1388339422,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 468,
"banscore" : 0
},
{
"addr" : "46.55.152.33:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339427,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 471,
"banscore" : 0
},
{
"addr" : "70.118.129.149:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340317,
"conntime" : 1388339433,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 471,
"banscore" : 0
},
{
"addr" : "84.54.172.244:21333",
"services" : "00000001",
"lastsend" : 1388340324,
"lastrecv" : 1388340324,
"conntime" : 1388339533,
"version" : 90002,
"subver" : "/Velocitycoin:0.7.2/",
"inbound" : false,
"releasetime" : 0,
"startingheight" : 491,
"banscore" : 0
}
]

used IP from this info, but got rejects...

[peterlustig]

used IP from this info, but got rejects...

It's called stale, probably your miner scantime is set to 30 not 1, which is what I'd recommend with a new coin.

Miner reports 86K diff, when QQcoin yesterday was below 0.1 for an hour or so and climbed only very slowly.

[FreePls]

why i only get 60 kh/s ? on scrypt i normaly have 280~

[dr_yan_yan]

@ those who will cry QQcoin clone for sure:
N-Factor seems to what be QQCoin has now, getting 3.3MH/s with Velcoin when I got 5MH/s with QQ aat the start. Also diff adjustment is way more radical, no stales!

Inside knowledge tells me... the clone coin is not always the 2nd to be released...
as with any team... conflicts in direction and priorities etc.


I quizzed them on twitter and the reply was something like - used the same  Nfactor/ StartT so that if anyone does do a POOL CPU MINER, then it can be used for a couple of coins, rather than always having to get new one made.

[noedelx]

mining with 670kh's how long shud it take till i get a block?

no suitable long-poll is normal right?

I've got 1 real block so far on a rig with 1.4MH/s, a few orphans, but expected

awell any other coin atm is high diff so might aswel give this a shot while i eat dinner ^^

well one single block and its rejected =D

[koob152]

A mining pool would be great! Is there anyone that can set it up? Note that it is scrypt-jane so cgminer won't work, it has to be ybcminer.

[atp1916]

This miner sucks.

Did hit a block and did get coins... so.

[opnoskatt]

so... "addnode" is not a legitimate command and the author is providing no nodes for mining.  Looks like the first couple people might have got a connection and now everybody else is SOL.  Can we consider this coin trash already?

Wow you girls whinge a lot.

I guess you're one of the lucky ones who connected on first try.  Too bad you'll probably never find a block now that people with actual rigs are on-board.  

[morrisminer]

ok - got 3 Accepts but coins appear momentarily and then gone! Why would that be? This is my velocitycoin.conf when third accept occurred:

rpcuser=user
rpcpassword=pass
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
gen=0
port=21333
rpcport=21334
addnode=206.72.193.8
addnode=77.247.181.162
addnode=91.77.102.87
addnode=91.154.202.96
addnode=78.205.83.28
addnode=87.219.35.151
addnode=121.221.31.187


cl is:

velocitycoinminer -o 127.0.0.1:21334 -u user -p pass --scrypt --Nfmin 4 --Nfmax 30 --StartT 1387769316 --scan-time 1 -I 15

[peterlustig]

why i only get 60 kh/s ? on scrypt i normaly have 280~

This is scrypt-jane. Search for ybcminer or yacminer and you should find some good settings. Mine (280x) are:
--scrypt --Nfmin 4 --Nfmax 30 --StartT 1387769316 --lookup-gap 4 --thread-concurrency 16384 -I 13 -w 256 -g 2 -s 0

[OrkneyCoiner]

used IP from this info, but got rejects...

It's called stale, probably your miner scantime is set to 30 not 1, which is what I'd recommend with a new coin.

Miner reports 86K diff, when QQcoin yesterday was below 0.1 for an hour or so and climbed only very slowly.

thx!

[illodin]

why i only get 60 kh/s ? on scrypt i normaly have 280~

Did you set the intensity? Another thing that happens to me often when I stop and start miners is that he hashrates drop 90% or so even though GPU usage is 99%. What I have to do is either reboot the PC, or disable/enable the display adapter(s) in the device manager and start the miner again.

[dr_yan_yan]

ok - got 3 Accepts but coins appear momentarily and then gone! Why would that be? This is my velocitycoin.conf when third accept occurred:

rpcuser=user
rpcpassword=pass
rpcallowip=127.0.0.1
daemon=1
server=1
listen=1
gen=0
port=21333
rpcport=21334
addnode=206.72.193.8
addnode=77.247.181.162
addnode=91.77.102.87
addnode=91.154.202.96
addnode=78.205.83.28
addnode=87.219.35.151
addnode=121.221.31.187


cl is:

velocitycoinminer -o 127.0.0.1:21334 -u user -p pass --scrypt --Nfmin 4 --Nfmax 30 --StartT 1387769316 --scan-time 1 -I 15

thems be orphans my friend.

[pmm123]

Sorry im noob who mine solo from gpu with windows?

[dr_yan_yan]

I will be looking to buy quite a few of these Lovelies in the next week or so.