[ANN][YAC] YACoin ongoing development

[YacLives]

A public GPU miner is only going to add miners to YAC, which, in my opinion is a good thing. I have a few GPU rigs and ALL of them have the absolute worst, yet most power efficient CPU's - so, not viable for YAC mining. Now that I can point some of them at YACoin, I can get back in the game. I'm guessing it's the same for many. Also, as WM already mentioned, the performance difference isn't like any other scrypt implementations - so for those that have good CPU's, mining is also still viable for them.  

I agree with this, especially since N is at a high enough level now so that GPU miners don't have THAT much of an advantage over CPU miners. I'm still solo-mining on my i7-2700k just fine.

Agree and disagree - I know there were people who were able to do their own OpenCL implementation and get them running ahead of one being publicly released.... However, the GPU in my laptop (7850M) is running at roughly 4x the rate of the CPU (i7 3610M) - that's quite a bit of an advantage!

In comparing YAC on GPU to BTC on GPU, It's looking to me that the newer cards (7xxx) do great at this algorithm, while older cards (5870, I'm looking at you), aren't so good, even though they may crush in BTC hashrate...

7850 -> 140 KH/sec YAC, 310 MH/sec BTC
5870 -> 100 KH/sec YAC, 400 MH/sec BTC

Are you running Techinfernos Throttlestop its great for disabling the boost throttling on laptops

cause as soon as you load it up the boost gets throttled instantly down as you may well know already. But i get your point too i just had to add that in there, that program is the bomb, it really brought a m11x r2 to life that i had

[1714320273]

1714320273

[1714320273]

1714320273

[wetroof]

I can do 300kh/s for ltc and 90 kh/s for yac with Hanzac's code.

thats .5 LTC versus 27 yacoin at the current difficulty of 0.76. it's about even price-wise.

the cpu ratio is closer to 2:1 in terms of kh/s for ltc vs yac. for cpu its more profitable to mine yac and for gpu its even at current prices.

[bitdwarf]

the cpu ratio is closer to 2:1 in terms of kh/s for ltc vs yac. for cpu its more profitable to mine yac and for gpu its even at current prices.

In the long run and if everybody did the same GPU mining LTC and trading for YACs would end being more profitable, as price would rise instead of increasing the supply.

[bandjhughes]

GPU miner released, heh..
I'm not so hyped about it.. YAC isn't special anymore, right?

Well, hanzac's GPU miner doesn't perform especially well compared with mtrlt's normal scrypt+salsa kernel for mining other scrypt coins on the same hardware.  Hanzac's OpenCL kernel was already mostly released way way back in this thread, he just needed to fix a few bugs.

I tested it long enough to mine about 5 blocks of YAC then switched my GPU farm back to mining LTC.

GPU farm? You have a CPU farm too, right?
What's your job? 

Perhaps farming? 

[Eli0t]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

[feeleep]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

I was trying to modify eloipool to work with scrypt-jane but I've got segmentation fault errors and I don't know how to debug it (I am not skilled at all in python). In my opinion problem with high stale rate is because for some reason (scrypt-jane dependant calculations?) both pushpool and yacoind are very hungry for resources - CPU usage in average ~10 times higher than other coins. Even if my server is 8 core with 24 GB RAM it creates some delays internally which leads to stales...

[Joe_Bauers]

What I think we need next TBH is a proper mining program with stratum support. That way we can capitalize on the hashrate we still have left and get better feedback and less stale shares.

I looked at this very briefly a few days ago and it looks like it could be adapted to YACoin if someone has time to spend a few hours on it    https://github.com/CryptoManiac/stratum-mining

[hanzac]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

I was trying to modify eloipool to work with scrypt-jane but I've got segmentation fault errors and I don't know how to debug it (I am not skilled at all in python). In my opinion problem with high stale rate is because for some reason (scrypt-jane dependant calculations?) both pushpool and yacoind are very hungry for resources - CPU usage in average ~10 times higher than other coins. Even if my server is 8 core with 24 GB RAM it creates some delays internally which leads to stales...

I find each time it hashes, it will allocate the memory buffer (call scrypt_alloc) and scrypt_free at the end of hash. Will it impact the performance when there're so many threads processing? How about make this memory buffer becomes thread-local to reduce these memory re-allocation?

Otherwise, I can't find more difference of it between the yacoin & other scrypt coins.

[feeleep]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

I was trying to modify eloipool to work with scrypt-jane but I've got segmentation fault errors and I don't know how to debug it (I am not skilled at all in python). In my opinion problem with high stale rate is because for some reason (scrypt-jane dependant calculations?) both pushpool and yacoind are very hungry for resources - CPU usage in average ~10 times higher than other coins. Even if my server is 8 core with 24 GB RAM it creates some delays internally which leads to stales...

I find each time it hashes, it will allocate the memory buffer (call scrypt_alloc) and scrypt_free at the end of hash. Will it impact the performance when there're so many threads processing? How about make this memory buffer becomes thread-local to reduce these memory re-allocation?

Otherwise, I can't find more difference of it between the yacoin & other scrypt coins.

If you are asking me - I have no idea how to do this but I can easily test it if you can provide example.

[hanzac]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

I was trying to modify eloipool to work with scrypt-jane but I've got segmentation fault errors and I don't know how to debug it (I am not skilled at all in python). In my opinion problem with high stale rate is because for some reason (scrypt-jane dependant calculations?) both pushpool and yacoind are very hungry for resources - CPU usage in average ~10 times higher than other coins. Even if my server is 8 core with 24 GB RAM it creates some delays internally which leads to stales...

I find each time it hashes, it will allocate the memory buffer (call scrypt_alloc) and scrypt_free at the end of hash. Will it impact the performance when there're so many threads processing? How about make this memory buffer becomes thread-local to reduce these memory re-allocation?

Otherwise, I can't find more difference of it between the yacoin & other scrypt coins.

If you are asking me - I have no idea how to do this but I can easily test it if you can provide example.

I made the change of code by using boost's thread-local facility. Here is the patch against the current git: https://github.com/yacoin/yacoin
http://sourceforge.net/projects/hnindev/files/yacoin_mem_opt_patch.zip

I've locally built the client, it works no error.

[hanzac]

the cpu ratio is closer to 2:1 in terms of kh/s for ltc vs yac. for cpu its more profitable to mine yac and for gpu its even at current prices.

In the long run and if everybody did the same GPU mining LTC and trading for YACs would end being more profitable, as price would rise instead of increasing the supply.

Don't forget that YAC block reward decreases with difficulty going up. More hashrate means YAC price must go up else mining becomes unprofitable.

[BOUNTY]

Anyway, is there someone skilled enough to add coin control to YACoin client? More info here > https://bitcointalk.org/index.php?topic=144331.0
I'll pay 1 BTC for the job which must include source code and working Win32 and 64 bit binaries. Others are welcomed to add some coins to bounty.

Hah, this is attractive. I'll see if I have spare time after tomorrow. I will take it if there's no one else accept this request. ;-)

But what's used for? I don't know why it's worth for 1BTC bounty.

OK, I got it. But now I'm wondering why not put this coin control directly in the yacoin-qt client?

[feeleep]

maybe time for a YAC pool with stratum now the gpu miner is out, getting quite a few stales

I was trying to modify eloipool to work with scrypt-jane but I've got segmentation fault errors and I don't know how to debug it (I am not skilled at all in python). In my opinion problem with high stale rate is because for some reason (scrypt-jane dependant calculations?) both pushpool and yacoind are very hungry for resources - CPU usage in average ~10 times higher than other coins. Even if my server is 8 core with 24 GB RAM it creates some delays internally which leads to stales...

I find each time it hashes, it will allocate the memory buffer (call scrypt_alloc) and scrypt_free at the end of hash. Will it impact the performance when there're so many threads processing? How about make this memory buffer becomes thread-local to reduce these memory re-allocation?

Otherwise, I can't find more difference of it between the yacoin & other scrypt coins.

If you are asking me - I have no idea how to do this but I can easily test it if you can provide example.

I made the change of code by using boost's thread-local facility. Here is the patch against the current git: https://github.com/yacoin/yacoin
http://sourceforge.net/projects/hnindev/files/yacoin_mem_opt_patch.zip

I've locally built the client, it works no error.

tested it but it works even slower - there must be also a different issue: I suspect few users on my pool are using botnets to mine yacs, which lead to lot of requests to pushpool...

I set up another pushpool instance on port 8888 - can anyone point a miner to this port and check accepted/rejected ratio?

[WindMaster]

I merged a large set of changes from Joe_Bauers to upgrade to a more recent version of the scrypt-jane library (hopefully easing some of the Windows QT client build problems).  I also added a checkpoint at block height 90000.

Everyone upgrade somewhat cautiously since there were quite a lot of changes to the code, and report if they broke anything.  A Linux build seems to be performing correctly for me after the changes, but I'm more unsure about whether anything broke on the Windows side.

Joe - I left out the RPC port change from 8332 to 8108 for now.  Main concern is that anyone that didn't explicitly specify rpcport= in their config file might have things broken by changing the RPC port (and worse, might not know that it broke).  I think if anyone is running the Novacoin client on the same box, then for now, they may need to manually set rpcport= in the config file.

[WindMaster]

Something is not right, there are 2 blockchains now and YAC explorer is on longer one, which is incompatibile with shorter one.

Checking vs. an old version of the client to see whether the scrypt-jane library upgrade merged from Joe_Bauers broke something with the block hash checks.  Everyone hold on upgrading until we know for sure what's up.

[digger]

what's wrong with YAC, one hour blocks in my pool become to orphan.

and new find block
for example

http://yacexplorer.tk//tx/2bd44cc71eb9ad506c6bb27d7f613cfe60d0cb9c11cf60b32919bf08e557d781

seems orphan, but when list transactions, it show "immature"

[eule]

related?

Code:

REORGANIZE
REORGANIZE: Disconnect 75 blocks; 00000000d4cdea93920c..00000000be297c3fa50a
REORGANIZE: Connect 2 blocks; 00000000d4cdea93920c..6928a457abc4f0f9abaf
CTxMemPool::accept() : accepted acae330997 (poolsz 1)
CTxMemPool::accept() : accepted 78d70ef8ba (poolsz 2)
CTxMemPool::accept() : accepted 2b7a3e135a (poolsz 3)
CTxMemPool::accept() : accepted 2617d7a7e9 (poolsz 4)
CTxMemPool::accept() : accepted 8cf9a476e8 (poolsz 5)
CTxMemPool::accept() : accepted 8deb16bef1 (poolsz 6)
CTxMemPool::accept() : accepted 484c3ba458 (poolsz 7)
CTxMemPool::accept() : accepted a12fe09e88 (poolsz 8)
CTxMemPool::accept() : accepted 4cd52e319e (poolsz 9)
CTxMemPool::accept() : accepted 854af59a78 (poolsz 10)
CTxMemPool::accept() : accepted 9a5ba50cd0 (poolsz 11)
CTxMemPool::accept() : accepted 8c3c750e3b (poolsz 12)
CTxMemPool::accept() : accepted 5f3183cd91 (poolsz 13)
CTxMemPool::accept() : accepted bbabacf713 (poolsz 14)
CTxMemPool::accept() : accepted c72a4747fd (poolsz 15)
CTxMemPool::accept() : accepted 79bd0318ea (poolsz 16)
CTxMemPool::accept() : accepted 87df04fe38 (poolsz 17)
CTxMemPool::accept() : accepted 49e9f5d79e (poolsz 18)
CTxMemPool::accept() : accepted c9aba598bc (poolsz 19)
CTxMemPool::accept() : accepted 04ec2cc009 (poolsz 20)
CTxMemPool::accept() : accepted 6e04d622a9 (poolsz 21)
CTxMemPool::accept() : accepted c8323850ff (poolsz 22)
CTxMemPool::accept() : accepted 5434375f71 (poolsz 23)
CTxMemPool::accept() : accepted 284ecb7003 (poolsz 24)
CTxMemPool::accept() : accepted b40212f758 (poolsz 25)
CTxMemPool::accept() : accepted 701337cb07 (poolsz 26)
CTxMemPool::accept() : accepted 75f4a95ce0 (poolsz 27)
CTxMemPool::accept() : accepted ccbf7ce008 (poolsz 28)
CTxMemPool::accept() : accepted c076dacbde (poolsz 29)
CTxMemPool::accept() : accepted 9479a4f8e6 (poolsz 30)
CTxMemPool::accept() : accepted 8e0d8aa060 (poolsz 31)
CTxMemPool::accept() : accepted d84feee543 (poolsz 32)
CTxMemPool::accept() : accepted 34d222cb6b (poolsz 33)
CTxMemPool::accept() : accepted dd785ba78a (poolsz 34)
CTxMemPool::accept() : accepted 468e016d5e (poolsz 35)
CTxMemPool::accept() : accepted 6fccdb01fd (poolsz 36)
CTxMemPool::accept() : accepted abc88dc86c (poolsz 37)
CTxMemPool::accept() : accepted 4a36c28214 (poolsz 38)
CTxMemPool::accept() : accepted 20ba535eb1 (poolsz 39)
CTxMemPool::accept() : accepted 1c5080c57a (poolsz 40)
CTxMemPool::accept() : accepted e32ee0d54e (poolsz 41)
CTxMemPool::accept() : accepted ae33c6bc04 (poolsz 42)
CTxMemPool::accept() : accepted dc631905a2 (poolsz 43)
CTxMemPool::accept() : accepted a665b5ea48 (poolsz 44)
CTxMemPool::accept() : accepted 75176a0b84 (poolsz 45)
CTxMemPool::accept() : accepted 0976d807fe (poolsz 46)
CTxMemPool::accept() : accepted 483878eb64 (poolsz 47)
CTxMemPool::accept() : accepted 380a6c249b (poolsz 48)
CTxMemPool::accept() : accepted 7881873cce (poolsz 49)
CTxMemPool::accept() : accepted 8978d4d243 (poolsz 50)
CTxMemPool::accept() : accepted 4698485598 (poolsz 51)
CTxMemPool::accept() : accepted 796c60c58a (poolsz 52)
CTxMemPool::accept() : accepted b9333f982d (poolsz 53)
CTxMemPool::accept() : accepted 5bfdbefcbb (poolsz 54)
CTxMemPool::accept() : accepted 81e4ec3de7 (poolsz 55)
CTxMemPool::accept() : accepted 249ecb8714 (poolsz 56)
CTxMemPool::accept() : accepted 7283444e42 (poolsz 57)
CTxMemPool::accept() : accepted 4f1068b636 (poolsz 58)
CTxMemPool::accept() : accepted c4bbad1c68 (poolsz 59)
CTxMemPool::accept() : accepted ffadc2b371 (poolsz 60)
CTxMemPool::accept() : accepted 19da8aac86 (poolsz 61)
CTxMemPool::accept() : accepted 5e7875586d (poolsz 62)
CTxMemPool::accept() : accepted 2a24c4c048 (poolsz 63)
CTxMemPool::accept() : accepted 9cdfb5f408 (poolsz 64)
CTxMemPool::accept() : accepted 28807f6350 (poolsz 65)
CTxMemPool::accept() : accepted 1774f7b2fa (poolsz 66)
CTxMemPool::accept() : accepted ef33b1b9a5 (poolsz 67)
CTxMemPool::accept() : accepted 8b51554319 (poolsz 68)
CTxMemPool::accept() : accepted 4123cf1438 (poolsz 69)
CTxMemPool::accept() : accepted 451c8cc22d (poolsz 70)
CTxMemPool::accept() : accepted 9d708ce16d (poolsz 71)
CTxMemPool::accept() : accepted 6a1fa02a11 (poolsz 72)
CTxMemPool::accept() : accepted c0856a6e80 (poolsz 73)
CTxMemPool::accept() : accepted 32bfe5fead (poolsz 74)
CTxMemPool::accept() : accepted 9445aefb28 (poolsz 75)
CTxMemPool::accept() : accepted 072ccb482d (poolsz 76)
CTxMemPool::accept() : accepted 1385c88fa8 (poolsz 77)
CTxMemPool::accept() : accepted 8c24a41b72 (poolsz 78)
CTxMemPool::accept() : accepted 43f6690ab6 (poolsz 79)
CTxMemPool::accept() : accepted fef5fcedcc (poolsz 80)
CTxMemPool::accept() : accepted 27bb73d2d6 (poolsz 81)
CTxMemPool::accept() : accepted 8c7207e18b (poolsz 82)
CTxMemPool::accept() : accepted 070a4fe57d (poolsz 83)
CTxMemPool::accept() : accepted d133e0422e (poolsz 84)
CTxMemPool::accept() : accepted 32c360aeec (poolsz 85)
CTxMemPool::accept() : accepted afdf77719f (poolsz 86)
CTxMemPool::accept() : accepted 098bec1bc2 (poolsz 87)
CTxMemPool::accept() : accepted 7604b2f0c1 (poolsz 88)
REORGANIZE: done
SetBestChain: new best=6928a457abc4f0f9abaf  height=91036  trust=180392666013  date=06/13/13 11:15:25
SetBestChain: new best=c66e7c5bb1d40c37c835  height=91037  trust=181466411933  date=06/13/13 12:02:55
ProcessBlock: ACCEPTED
ERROR: ConnectInputs() : tried to spend coinbase at depth 462
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
ERROR: ConnectInputs() : tried to spend coinbase at depth 481
ERROR: ConnectInputs() : tried to spend coinbase at depth 477
ERROR: ConnectInputs() : tried to spend coinbase at depth 490
ERROR: ConnectInputs() : tried to spend coinbase at depth 495
ERROR: ConnectInputs() : tried to spend coinbase at depth 494
ERROR: ConnectInputs() : tried to spend coinbase at depth 492
ERROR: ConnectInputs() : tried to spend coinbase at depth 482
ERROR: ConnectInputs() : tried to spend coinbase at depth 469
ERROR: ConnectInputs() : tried to spend coinbase at depth 464
ERROR: ConnectInputs() : tried to spend coinbase at depth 456
ERROR: ConnectInputs() : tried to spend coinbase at depth 453
keypool return 12
getblocks 90973 to 6928a457abc4f0f9abaf limit 500
  getblocks stopping at 91036 6928a457abc4f0f9abaf
getblocks 90973 to c66e7c5bb1d40c37c835 limit 500
  getblocks stopping at 91037 c66e7c5bb1d40c37c835
Flushing wallet.dat
Flushed wallet.dat 221ms
getblocks 91036 to 00000000000000000000 limit 500
ERROR: ConnectInputs() : tried to spend coinbase at depth 462
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
ERROR: ConnectInputs() : tried to spend coinbase at depth 481
ERROR: ConnectInputs() : tried to spend coinbase at depth 477
ERROR: ConnectInputs() : tried to spend coinbase at depth 490
ERROR: ConnectInputs() : tried to spend coinbase at depth 495
ERROR: ConnectInputs() : tried to spend coinbase at depth 494
ERROR: ConnectInputs() : tried to spend coinbase at depth 492
ERROR: ConnectInputs() : tried to spend coinbase at depth 482
ERROR: ConnectInputs() : tried to spend coinbase at depth 469
ERROR: ConnectInputs() : tried to spend coinbase at depth 464
ERROR: ConnectInputs() : tried to spend coinbase at depth 456
ERROR: ConnectInputs() : tried to spend coinbase at depth 453
keypool return 12

[snip]

ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
ERROR: ConnectInputs() : tried to spend coinbase at depth 499
keypool return 12
received block 00000000a69aa2d9f222
SetBestChain: new best=00000000a69aa2d9f222  height=91084  trust=182540157899  date=06/13/13 12:50:42
ProcessBlock: ACCEPTED
keypool return 12

Failed 51%?

[amytheplanarshift]

Here is a screenshot of my old client (original "official" client) and yacexplorer. I am getting a block # discrepancy as well.

[liteuser]

I've got some orphans from past hour that had been accepted (included a PoS block).

getmininginfo gives 91091

[bitdwarf]

My wallet is on block 91095.

Edit: No updated client.

[WindMaster]

Everyone that's showing a lower block count #, are you on a version of the client prior to my Github commits of about an hour ago?  I'm trying to determine now whether everyone having problems is or isn't on the client with the updated scrypt-jane library that I pushed to Github within the last hour.  If anyone showing the lower block count # did not upgrade, then it isn't connected to the changes.  If everyone showing the lower block count # did upgrade, then I'll revert the last 2 commits in the Github repository.

Bitcoin Megastore and eule, did you upgrade in the last hour?