I'm looking to add to our team of core programmers. There is much to be done for 0.4.5. Anyone is welcome! Send me a PM or "apply" in this thread. Better yet, submit a pull on github

I unfortunately have very little programming knowledge - but I would be more then willing to help beta-test any new versions or updates.

Something else I noticed in 0.4.4 that maybe we could correct in 0.4.5; it seems that the 'estimated total blocks' and 'last block time' in the debug window might not be right. Below is a screenshot of my debug window. The client is fully synced and has been running for a few days.

OK thanks for offering to help test. The estimated total blocks just shows the last checkpoint in the code, so I will change it to show current block if greater than last checkpoint.

Hello Joe et al,

I believe the code for that element is problematic in lots of other coins, including bitcoin. Looking at rpcconsole.ui the line is row 11, known as "totalBlocks". Now looking at rpcconsole.cpp function

I think there is some (a lot) of cruft in the bitcoind and bitcoin-qt source code that *coin "cloners" just keep carrying along and pretty soon (it's been 5 years of bitcoin now) no one will know what or why some code exists

I don't think the original bitcoin had any notion of checkpoints, so I don't know when this code came in?

I vote to fix the labels in rpcconsole.ui, rename the code in rpcconsole.cpp (and rpcconsole.h too) and in main.cpp to reflect whatever that element really is!! Or just delete all of it!!!(lol)

Ron

BTC: 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf The day is coming when a single carrot, freshly observed, will set off a revolution. Paul Cezanne

Yesterday on IRC we had a discussion about this and it was decided to remove the 'number of blocks of peers' display completely.It is unreliable information and not needed for progress reporting - the progress estimate based on block times is used for that....

So on May 6th of this year, 2014, Wladimir decided to dump it! After ~5 years! Ah, great minds think alike

The build date is in version.cpp If you undef#define GIT_ARCHIVE 1 then you will get your compile date IIRC?(tips may be placed in the hat on the floor )Ron

BTC: 1DPvP6WoZzaNQ9Nxzd64hjYad1kyQzTTbx YAC: Y3ZggXDvnRJaRwtVGyGJwt6DMLN3EPQpQf The day is coming when a single carrot, freshly observed, will set off a revolution. Paul Cezanne

so you guys tell me what to expect with 1.2 khash/s in yac per day ...

imo about 1300 to 1500 yac

my confirmed and unconfirmed after exactly 24h was about 650 yac

I'm now into 37 hours and it doesn't look to catch up at all.

PS:in the past such calculations worked out just fine (n14 + n15)

As a brainstorm and without diving too much into it, I wonder if estimations assume pool hashrate as total network hashrate. At NFactor 14,15 it just so happened that coinmine dominated total network hashrate, so a mistake like that would have had negligible impacts.

I think it is time the pools post in hash/s vs khash/s. I contacted yac.m-s-t.org about it a while back, but it will be worth doing again, yac.coinmine.pl especially.

In other news, YAC is in THIRD place in voting at www.crypto-trade.com/voting. If nothing changes, YAC will be listed on that exchange (including a USD/YAC pair) in 6 weeks! It would be great to see it not be leap-frogged by another coin, but I guarantee it will require more votes. I'd love to see it happen organically without any more BTC donated to get YAC on that exchange.

Now it is clear. Something is not ok and you really do not get enough if rig is 4x 0.34kh/s (>1.3kh/s brut. total) and all works optimally.

I can not help with R7 240 4Gb settings (and also there is many other things that just card model) because I use Nvidia 750 Ti rigs for YAC. (one 750Ti give around 0.3 - 0.33kh/s with very conservative OC and also with 1x risers. (1x risers also drop small amount of hashrate when use with Nvidia cards but Radeons are different and risers do not mean "anything")

If you look pool statistics and there Graphs, what it tell about your hashing speed (if yoy try estimate some kind of average from graph)

(With R9 280x rigs I meet so severe difficulties with chacha N16 that I give hands up with these, partially also due to lack of time to do exercises, and I leave these for N14 mining)

I have one R7 240 4Gb waiting on my table for some tests later after I get some free time and some HW for start testing with it.

so you guys tell me what to expect with 1.2 khash/s in yac per day ...

imo about 1300 to 1500 yac

my confirmed and unconfirmed after exactly 24h was about 650 yac

I'm now into 37 hours and it doesn't look to catch up at all.

PS:in the past such calculations worked out just fine (n14 + n15)

As a brainstorm and without diving too much into it, I wonder if estimations assume pool hashrate as total network hashrate. At NFactor 14,15 it just so happened that coinmine dominated total network hashrate, so a mistake like that would have had negligible impacts.

I think it is time the pools post in hash/s vs khash/s. I contacted yac.m-s-t.org about it a while back, but it will be worth doing again, yac.coinmine.pl especially.

In other news, YAC is in THIRD place in voting at www.crypto-trade.com/voting. If nothing changes, YAC will be listed on that exchange (including a USD/YAC pair) in 6 weeks! It would be great to see it not be leap-frogged by another coin, but I guarantee it will require more votes. I'd love to see it happen organically without any more BTC donated to get YAC on that exchange.

Good news! Yac/Usd is cool, hopefully they don't kill crypto-trade this time.

I set up my own pool after latest N change and my coin generation doubled after that.However I have issues with my network that only affect my gpu miner.

I get at least 10% of these errors with yaccminer (gpu):Rejected 810ea74e Diff 1/0 GPU 0 (job not found)

Every couple of minutes I get "Stratum connection to pool 0 interrupted".

No errors from cpu miner working on the same machine, connecting to same port with same pool difficulty.Nevertheless yacminer's sucessfull submission share rate is almost double than my cpus (so is it's hash rate).

My friend also mines on this pool with all cpu miners - he is also finding far more (2x-3x) blocks with his miners than I do with my gpu miner and he's comulative hashing rate isn't much higher than my gpu's. Besides more of my gpu mined blocks get orphaned (50% at least).

I am sure coinmine.pl is loosing at least half of what it could produce with that hash rate. I don't know why.

Also I think CPU miners on that pool are loosing even more: Pool difficulty was probably not ment to go that far below 1 than it was "pushed" with N factor increments. I tried setting my pool difficulty to 0.001, 0.000001, even 1e-15 and dual core athlon 64bit for example still needed hours to hit a share. That means pools don't know exactly "when" cpu miners were working because their share submissions are so rare. And gpu miners submit far more shares and rarely find a block - at least that is what I am observing.

So there are many issues combined here, but I think current block rewards this high are due problems that GPU miners are observing. Pools also have issues with setting/calculating fair share difficulty. Perhaps miner software also have issues with recognizing difficulty (difficulty number get's rounded and numeric precision isn't accounted properly?).

I don't have time to check all the code now, my own priority is to fix my network issues. And after that gpu miner's picture could improve a bit.But I can also confirm that my friend who is now mining on my pool with cpu miners gets 2-3x what he got on the public pool before.

I mean together we have less than 1kh and we hit 5-10 blocks per day. Plus orphans.In a way that is encouraging, because I think we all could be mining on "private" pools until reward get's below 40 or even 25.

I will be glad to hear if someone has any recommendations for my gpu miner's problems (yacminer --scrypt-chacha --lookup-gap 6 -R 1280).

Only the first 6 miners at https://www2.coinmine.pl/yac show a hashrate above 1 khash,I do believe many miners there share the same issues as I do at that pool.

It seems to me that the pool doesn't count every share.

I'll shed some light on this - For some reason feelep lowered the share difficulty to 0.25 (a non-integer). From my memory, the mining software doesn't even validate any share unless its difficulty is 1 or higher - and it's all integer based, so it would be a major undertaking to make it work for his pool. So, you are definitely losing out compared to people who can submit shares lower than 1 (maybe cudaminer or ccminer can?). I spent an afternoon looking through the yacminer code for where it made that determination to only validated shares of diff 1 or higher, but never found it (it may have been in the CPU miner software). That's when I decided to solo mine, and started netting almost double compared to the pool.

Only the first 6 miners at https://www2.coinmine.pl/yac show a hashrate above 1 khash,I do believe many miners there share the same issues as I do at that pool.

It seems to me that the pool doesn't count every share.

I'll shed some light on this - For some reason feelep lowered the share difficulty to 0.25 (a non-integer). From my memory, the mining software doesn't even validate any share unless its difficulty is 1 or higher - and it's all integer based, so it would be a major undertaking to make it work for his pool. So, you are definitely losing out compared to people who can submit shares lower than 1 (maybe cudaminer or ccminer can?). I spent an afternoon looking through the yacminer code for where it made that determination to only validated shares of diff 1 or higher, but never found it (it may have been in the CPU miner software). That's when I decided to solo mine, and started netting almost double compared to the pool.

Hi - sorry - I could not follow this thread. I was not aware of miner's limitation to diff 1 so I will change stratum settings right now.

Great? My earnings drops dramatically. 50% drop or even more. Without any markable change in difficulty what have been around 0.0012. Something is now very odd if compare time before this change. Also now there is lot of more times when my workers drops offline. Previously my 2 rigs (GPU rigs) never show in pool "my workers" that they are off. Now many times. Now my other miners, (i7 cpu's) are mostly "off". Previously system (pool) works just ok. Now it is so terrible that perhaps need try solo. I do not accept over 50% drop without any markable change in Network and my hashrate. Rule no 1. is that do not "repair" and "adjust" well working system.

Please change pool hashrate display to display hashes/s instead of khashes/s. khash/s display is too rough for N16.With this peoples can check what miner display and pool thinks about hashrate. If there is too big difference then people need find problem in his own end.

I can not yet proof it but now it really looks like that pool do not count every accepted shares. (if I look my miners displays and pool dashboard "valid" count. They do not match and after this change situation looks like more bad. (lest in my case)