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 |
|
|
|
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. |
|
|
|
|
@ 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!
|
|
|
|
Nodes: 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
}
]
|
|
|
|
Wow the diff is rising very fast.  |
|
|
|
yes please for the windows version  Sorry I fail, it's so annoying and complicated on Windows to compile stuff! Someone else will have to do it. |
|
|
|
Dunno, my wallet says stake: 0QQC so POS may be implemented.  |
|
|
|
|
Your opinion has been noted.
|
|
|
|
yes please for the windows version Will take time as I have to get the build environment and stuff. If someone has MSYS already installed he could do it in no time.  |
|
|
|
A CPU Miner for pools would be great! Defi here: Linux binary coming soon but you should compile it yourself for maximum performance. Feel free to donate: QUtKcZEGFDqdsAkevEk9sjk5yggCu5BJJM  |
|
|
|
Actually yes there will be. PM me please mate. Here's the changed source: http://www11.zippyshare.com/v/50216255/file.htmlNo time to compile sry, someone else will have to do that or me in a few hours. Very easy on linux and win64 bit harder on win32. Look at the readme. |
|
|
|
survival of the fittest |
|
|
|
WTB 500k QQC for 1BTC (0.000002 each)
I doubt anyone has that many coins. I got 6150 mining the last ~16 hours with a 280x. Difficulty is rising very fast and it's getting hard to solo. This reminds me pretty much of Applecoin with 75% mined in a few days, which is why I gonna hold. |
|
|
|
I went back to the vanilla solo-mine.bat but it didn't improve my hashes, unfortunately. Mine was at 2.8mh/s while you guys were getting 5mh/s and now it's at 2.45mh/s while the others have fallen to around 3.3mh/s.
Is Scrypt Jane more system RAM intensive than regular Scrypt? I have 4gb for 3x7950. They run beautifully on plain Scrypt.
Those of you who reached 5mh/s, how much system RAM are you running and what GPU driver?
I don't believe it uses much if any more system ram than normal scrypt, thread concurrency being the same. Currently, I'm using 2.6 gb out of 16 with 4 GPUs mining (9 gb of total GPU memory), along with the standard windows background process usage and about 10 tabs open. I would think 4gb of system ram should be just fine. Currently running 13.11 (whql iirc), forgot I was going to upgrade to 13.12 today, oops. Had 5MH and now 3.3, running 13.12. The key to a high hashrate is the lookup-gap command, currently using --lookup-gap 4 --thread-concurrency 16384 . |
|
|
|
|
I think the nFactor change happened at 20000 blocks btw (at 20089 right now), so every 20000 blocks I guess.
|
|
|
|
|
I think there was an nFactor change, my hashrate fell from 5 to 3.3MH/s.
|
|
|
|
I only get 2MH  But I have 13.9 drivers installed, downloading 13.12 to test. @trid: Are you really using the yac2miner, not ybc2? |
|
|
|
Do you guys also have strange hashrate? I have 6 Mh/s instead of 620 kh/s on my HD7970? And my R9 290 has a lower hashrate of 4.9Mh/s...
yep, my 280x have 6Mh/s too, so it's normal settings plz |
|
|
|
|
Show Posts
