Everyone is welcomed to mine on my p2p YAC pool

http://31.220.1.53:8335

In order to mine

Replace Y1dncJeBobRiYiBop6LWsUXq9fm8HbQfsp with your yac wallet address and mine away.

Pool pays out each time block is found.

No registration needed.

We are hitting n=512 in a couple hours, by the way.

He refers to the second row of his sample.

How could anyone have an OpenCL implementation of scypt-jane?

I didn't think that was possible, not even theoretically.

-Michael

The code I added to yacoind to produce the "networkhashps" info is only an estimate, and is based on spacing between solved blocks over a fairly short period of time.  There isn't a way to directly measure hash rate, the best we can do is estimate it.  Variability is capable of producing the swing you observed above.  From my own data collection process that keeps track of average block spacing, at this time my opinion is that there wasn't a sustained rise in (estimated) hash rate that would be outside the realm of variability.

Now, if the estimated hash rate jumped and then stayed at that level, that would be more interesting and much less likely to be just a variability-induced fluctuation in the way my hash rate estimation code works.

I copied a good portion of the hash rate estimation code from Litecoin.  Our (target) block rate is 2.5x faster than Litecoin.  Perhaps I should tweak the code to average the hash rate estimate across 2.5x more blocks than Litecoin does to try to smooth out some of these swings so we're at least averaging over the same amount of time.  Even Litecoin's hash rate estimate has some pretty wild swings due to variability.

Guys, have you seen bitminter.com? Very neat pool. They do something similar to what we were talking about with bitcoin. Java web start client...relative no-brainer to get started (certainly a LOT better than setting up cgminer). I use cgminer/anubis with my farm, but ran their client on my workstation to try it out. It looks like they have about 8000 miners on their systems, around 2/3 of which are using the bitminter client. Funny thing is, their client does detect the CPU and offer it as a mining device, although I don't think that's used much anymore.



Another option is to create a pushpool client that works like this. A mmcfe fork could be created that offers services like statistics, registration via an API, to allow the user to just download the client and register from it, as well as viewing their statistics. There could be a master pool directory web service that could be used to allow switching between pools possibly. If something like OpenID or Google Accounts OAuth was used, registration could just be off of their google account, for instance, further simplifying things (this is how bitminter works for the initial signin).

p2pool is probably the most "resilent" way to do it, but my thought is that p2pool has a major deficiency currently with their statistics feedback. In short, it really sucks (IMHO). Any user of a tool like this wants to see, at an absolute minimum:
* their current hashrate
* estimated coins per day
* graph of coin yield over the past week or so
* graph of hash rate over the past week or so

This info doesn't necessarily need to be in the tool itself, but has to be available. With bitminter, it's on their site when you're logged in.

If anything, this is food for thought to me at least.

Here it is 

How are you getting these relatively high hash rates?

On my W530 laptop (which is no slouch, it has a core i7 w/32 gb) I'm way down around 10 kh/s, which I don't understand.

What are you guys mining with?

-Michael