Sidehack stick solo pool club

[TheRealSteve]

hash is up for today  Fixed order  #636639  0.011 btc 5th

and you've got a new best share
New best share for philipma1957donation: 1078757183.8467309 -> 2366037587.8023853
Apparent 1hr hash rate increase (61%) for donator philipma1957donation: 1.52Th/s -> 2.45Th/s

If it helps, I could extend my notification script so that it reports the hash rates of the monitored addresses at the time a block is hit.
[...]
There's other algorithms that we could consider, but it probably makes sense to keep this simple. Also, someone else might have a better way to do this. It doesn't hurt my feelings if someone has a better alternative.

'better' in what way, I guess I'd have to ask.  This is a fairly elegant solution as it is; considering nobody can predict when (if) the club would hit a block, the only way to be sure you get a share is to partake continuously.  Sure, somebody who joined just moments before a block would be hit would be 'lucky', but one of the running averages could easily be taken.
Other solutions require continuous polling (as the IRC bot does) and e.g. performing a running average based on some start moment.  Also doable, just not nearly as elegant

Other than people tinkering and rented donation hash rate, there's very little movement in workers' individual hash rates for the 1hr figure so far, by the way.

[philipma1957]

hash is up for today  Fixed order  #636639  0.011 btc 5th

and you've got a new best share
New best share for philipma1957donation: 1078757183.8467309 -> 2366037587.8023853
Apparent 1hr hash rate increase (61%) for donator philipma1957donation: 1.52Th/s -> 2.45Th/s

If it helps, I could extend my notification script so that it reports the hash rates of the monitored addresses at the time a block is hit.
[...]
There's other algorithms that we could consider, but it probably makes sense to keep this simple. Also, someone else might have a better way to do this. It doesn't hurt my feelings if someone has a better alternative.

'better' in what way, I guess I'd have to ask.  This is a fairly elegant solution as it is; considering nobody can predict when (if) the club would hit a block, the only way to be sure you get a share is to partake continuously.  Sure, somebody who joined just moments before a block would be hit would be 'lucky', but one of the running averages could easily be taken.
Other solutions require continuous polling (as the IRC bot does) and e.g. performing a running average based on some start moment.  Also doable, just not nearly as elegant

Other than people tinkering and rented donation hash rate, there's very little movement in workers' individual hash rates for the 1hr figure so far, by the way.

I don't see any real problems with it other then how to deal with stick down time.  For now I am going to err on the generous side if a stick crashes and is offline when we hit a block. As long as everyone is pretty much okay with it that way.

[TheRealSteve]

I don't see any real problems with it other then how to deal with stick down time.  For now I am going to err on the generous side if a stick crashes and is offline when we hit a block. As long as everyone is pretty much okay with it that way.

It would have to have been offline for a sufficient amount of time to also impact the 1d rolling average pretty badly.  But yeah, otherwise - since you're poking at linux anyway - look up cron jobs   Can just download each participants' stats to a daily stats file and tally up the numbers as appropriate if/when a block is found.

[edonkey]

I don't see any real problems with it other then how to deal with stick down time.  For now I am going to err on the generous side if a stick crashes and is offline when we hit a block. As long as everyone is pretty much okay with it that way.

It would have to have been offline for a sufficient amount of time to also impact the 1d rolling average pretty badly.  But yeah, otherwise - since you're poking at linux anyway - look up cron jobs  Can just download each participants' stats to a daily stats file and tally up the numbers as appropriate if/when a block is found.

That would be a simple solution too. It's easy to periodically query the JSON stats of the workers and save that in a file. In fact, that's what the notification script does, although currently it only "remembers" the last query without a historical record, so every 90 seconds it would be updated.

That probably doesn't matter since the script stores the JSON results in its entirety, including the daily average. Should be enough to figure out the hash rate contribution given that people will notice that the club found a block in way less than a day. A solved block would be noticed in seconds, I suspect

That said, if there was interest in keeping a limited historical record, that would be pretty easy to add. I designed the stats file format so that it would be easy to extend with new data structures.

Note that instead of using the script directly, anyone familiar with Python could take a look at it as an example. Most of the complexity of the script comes from command line option handling and support for authenticated emails. The actual code that loops through a list of workers querying the JSON stats URLs is just a few lines of code.

In the meantime if Phil wants to play with the script as-is, I've PM'd him with the info to get started, plus a discussion of other additions that could be made to to the script.

[vapourminer]

so with this basically everyone pools their sticks together to one addy and if a block is found the reward is split evenly?  nifty idea, better than using the stick by yourself

no just one sidehack stick is the admission ticket to this club.  the rest is optional but highly appreciated

[philipma1957]

I don't see any real problems with it other then how to deal with stick down time.  For now I am going to err on the generous side if a stick crashes and is offline when we hit a block. As long as everyone is pretty much okay with it that way.

It would have to have been offline for a sufficient amount of time to also impact the 1d rolling average pretty badly.  But yeah, otherwise - since you're poking at linux anyway - look up cron jobs  Can just download each participants' stats to a daily stats file and tally up the numbers as appropriate if/when a block is found.

That would be a simple solution too. It's easy to periodically query the JSON stats of the workers and save that in a file. In fact, that's what the notification script does, although currently it only "remembers" the last query without a historical record, so every 90 seconds it would be updated.

That probably doesn't matter since the script stores the JSON results in its entirety, including the daily average. Should be enough to figure out the hash rate contribution given that people will notice that the club found a block in way less than a day. A solved block would be noticed in seconds, I suspect

That said, if there was interest in keeping a limited historical record, that would be pretty easy to add. I designed the stats file format so that it would be easy to extend with new data structures.

Note that instead of using the script directly, anyone familiar with Python could take a look at it as an example. Most of the complexity of the script comes from command line option handling and support for authenticated emails. The actual code that loops through a list of workers querying the JSON stats URLs is just a few lines of code.

In the meantime if Phil wants to play with the script as-is, I've PM'd him with the info to get started, plus a discussion of other additions that could be made to to the script.

I will get some alone time on it tonight. I think a 48-72 hour history is long enough if possible.
I would hate for someone to run a stick 20 days in a row go away for a week end have the stick crash and not get anything.
Once I have a working one set up I can look at it 2x a day to see if someone is attempting to game the system.  these first 30 days are looser due to the extra hash I am tossing at this. but after 30 day we should have this set up just fine. 

[notlist3d]

I don't see any real problems with it other then how to deal with stick down time.  For now I am going to err on the generous side if a stick crashes and is offline when we hit a block. As long as everyone is pretty much okay with it that way.

It would have to have been offline for a sufficient amount of time to also impact the 1d rolling average pretty badly.  But yeah, otherwise - since you're poking at linux anyway - look up cron jobs  Can just download each participants' stats to a daily stats file and tally up the numbers as appropriate if/when a block is found.

That would be a simple solution too. It's easy to periodically query the JSON stats of the workers and save that in a file. In fact, that's what the notification script does, although currently it only "remembers" the last query without a historical record, so every 90 seconds it would be updated.

That probably doesn't matter since the script stores the JSON results in its entirety, including the daily average. Should be enough to figure out the hash rate contribution given that people will notice that the club found a block in way less than a day. A solved block would be noticed in seconds, I suspect

That said, if there was interest in keeping a limited historical record, that would be pretty easy to add. I designed the stats file format so that it would be easy to extend with new data structures.

Note that instead of using the script directly, anyone familiar with Python could take a look at it as an example. Most of the complexity of the script comes from command line option handling and support for authenticated emails. The actual code that loops through a list of workers querying the JSON stats URLs is just a few lines of code.

In the meantime if Phil wants to play with the script as-is, I've PM'd him with the info to get started, plus a discussion of other additions that could be made to to the script.

I will get some alone time on it tonight. I think a 48-72 hour history is long enough if possible.
I would hate for someone to run a stick 20 days in a row go away for a week end have the stick crash and not get anything.
Once I have a working one set up I can look at it 2x a day to see if someone is attempting to game the system.  these first 30 days are looser due to the extra hash I am tossing at this. but after 30 day we should have this set up just fine. 

I would love if we did get some stats.  I really would like to see it turn into a social aspect to.   Not sure what is best but say if had a website that tracks/shows stats maybe a social aspect like troll box, or something I think could be fun.

I'm would also love if we had a stat that told something like with current X speed we stand a 1 in X chance of hitting block.   Would enjoy watching that just like I watch difficulty.

[Mikestang]

My single stick pointed at the club address is down to 125 frequency, I have it running solo on an old laptop and that was all I could squeeze out the stick at 0.5a measured at the usb port.  I have very little hash going at this point in the summer, I'll see if I can't free up a bit more from regular solo lottery mining and share it here.  It wouldn't be much, but every GH helps.

More stats to watch would be really fun, but hopefully no one loses sleep over it.

Is the intention at some point to only have Compac sticks pointed to the club?  I think ultimately that would be really cool.

[notlist3d]

My single stick pointed at the club address is down to 125 frequency, I have it running solo on an old laptop and that was all I could squeeze out the stick at 0.5a measured at the usb port.  I have very little hash going at this point in the summer, I'll see if I can't free up a bit more from regular solo lottery mining and share it here.  It wouldn't be much, but every GH helps.

More stats to watch would be really fun, but hopefully no one loses sleep over it.

Is the intention at some point to only have Compac sticks pointed to the club?  I think ultimately that would be really cool.

I think keeping it to smaller USB's at least.  I hope it is that you can add extra, but it remains somehow where 1 1T machine does not kill all compacs when we do track speed's in a month.

[baktegon]

baktegon here again!

I've got them working! all 4 sticks should be pointed at the sidehack pool. I'm using regular cgminer-gekko on an ubuntu HP desktop from ages ago. All four sticks are showing hashrate in cgminer so this is good! I'm still waiting on my usb hub to run these on the raspberry pi but for the next couple of days I should be good to go.

It looks like my stats are showing up at http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.baktegonUnit01


thanks for the help all!

[Jake36]

baktegon here again!

I've got them working! all 4 sticks should be pointed at the sidehack pool. I'm using regular cgminer-gekko on an ubuntu HP desktop from ages ago. All four sticks are showing hashrate in cgminer so this is good! I'm still waiting on my usb hub to run these on the raspberry pi but for the next couple of days I should be good to go.

It looks like my stats are showing up at http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.baktegonUnit01


thanks for the help all!

Are the sticks on a hub or plugged into the ports on the computer?

Looks like they are dropping off, so if they are on the ports in the computer, it probably doesn't have enough power on the ports for all 4, same goes if they are in a hub.

Try just 1 stick for a while and see what it does.

Edit: never mind, looks like they are coming back up.

[baktegon]

baktegon here again!

I've got them working! all 4 sticks should be pointed at the sidehack pool. I'm using regular cgminer-gekko on an ubuntu HP desktop from ages ago. All four sticks are showing hashrate in cgminer so this is good! I'm still waiting on my usb hub to run these on the raspberry pi but for the next couple of days I should be good to go.

It looks like my stats are showing up at http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.baktegonUnit01


thanks for the help all!

Are the sticks on a hub or plugged into the ports on the computer?

Looks like they are dropping off, so if they are on the ports in the computer, it probably doesn't have enough power on the ports for all 4, same goes if they are in a hub.

Try just 1 stick for a while and see what it does.

Edit: never mind, looks like they are coming back up.

I have them all plugged into a hub. I was getting used to using the minera interface for cgminer so using the regular version had a few missteps for me. I finally got everything typed in the way I wanted it so should be stable now for the next several days. Woo contributing!

[philipma1957]

Morning to all.  Fresh hash is up  0.011 btc  order #638911  should last for 6 hours


https://www.nicehash.com/

http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957donation

[notlist3d]

Morning to all.  Fresh hash is up  0.011 btc  order #638911  should last for 6 hours


https://www.nicehash.com/

http://solo.ckpool.org/workers/1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957donation

Thanks for sending more hash to it!  Hopefully we get lucky one day.

Does anyone have any good ideas to make this club a little more social?   I am really hoping we can get a social aspect to it.

[-ck]

Does anyone have any good ideas to make this club a little more social?   I am really hoping we can get a social aspect to it.

How about the oldest "social" medium on the internet - IRC? Start your own channel or join the #ckpool one.

[edonkey]

I've updated the CK solo pool notification script with the following changes:

• When notified of changes (like a new block found or best share improvements) the hash rate stats of the affected monitored addresses is also reported. So if the club finds a block, the hash rates of all the monitored workers will be reported.
• If the --verbose option is on, the email text will be logged locally. This could be useful if the email can't be sent but an important event like a found block happened. In this situation, the email text could be pulled out of the log.
• Fixed some problems sorting mining addresses.
• Cleaned up the formatting of the email body text.
• Added an testing/developer option that allows the caller to pretend like a specified address found a block. Previously I had to hard code script globals to force block found testing.

Here's the github URL for anyone who's interested in playing with the script:

http://edonkeycoin.github.io/ckpoolnotify/

I've tested the latest version with the current list of club workers, and it seems to work fine. I was a bit concerned that a large number of workers might make the command line too big, but it seems fine for now (on the Mac at least).

If you've followed the read me instructions and gotten your email credentials to work with a test email, then a command line like the following will monitor the list of known workers at this time (substitute your own email credentials, of course):

Code:

./ckPoolNotify.py --verbose --server "smtp.gmail.com:587" --user edonkeycoin@gmail.com --users "1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX" --workers "1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.edonkeystick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.VirosaGITSdonation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.notlist3dstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.larry12stick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.larry12s5donation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.vapourminerstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.fullzerostick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jake36stick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.TheRealStevestick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.alienesbstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Chris_Sabianstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Ecnadstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.mikestangstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.baktegonUnit01,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.slimepuppysticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.slimepuppydonation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.peptostick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.kipper01"

At some point I'll support a config file to make it easier to manage a large list of workers.

If you're using the script and you want to update to a new version, all you have to do is stop the current script, replace it with the latest, then start it up again.

If you're on the Mac and you opted to set up the script as a daemon, then you'll have to unload and reload the daemon. Here's the basic command lines to use (replace the path to the new script before using):

Code:

# Copy the updated version over the old
sudo cp -rp ~/ckPoolNotify /Library/Application\ Support

# Unload and reload the daemon
sudo launchctl unload /Library/LaunchDaemons/org.edonkey.mining.ckpoolnotify.plist
sudo launchctl load /Library/LaunchDaemons/org.edonkey.mining.ckpoolnotify.plist

One odd thing I noticed while testing the latest is that none of the pool workers have a 7 day hash rate average. I don't know why this is. Maybe if there are any club members that have less than 7 days in, then none of the 7 day averages for the others get reported?

It might not matter if we rely on the 1 day average, or if we add a mechanism to remember a few days worth of hash rate (which Phil suggested).

[Jake36]

I've updated the CK solo pool notification script with the following changes:

• When notified of changes (like a new block found or best share improvements) the hash rate stats of the affected monitored addresses is also reported. So if the club finds a block, the hash rates of all the monitored workers will be reported.
• If the --verbose option is on, the email text will be logged locally. This could be useful if the email can't be sent but an important event like a found block happened. In this situation, the email text could be pulled out of the log.
• Fixed some problems sorting mining addresses.
• Cleaned up the formatting of the email body text.
• Added an testing/developer option that allows the caller to pretend like a specified address found a block. Previously I had to hard code script globals to force block found testing.

Here's the github URL for anyone who's interested in playing with the script:

http://edonkeycoin.github.io/ckpoolnotify/

I've tested the latest version with the current list of club workers, and it seems to work fine. I was a bit concerned that a large number of workers might make the command line too big, but it seems fine for now (on the Mac at least).

If you've followed the read me instructions and gotten your email credentials to work with a test email, then a command line like the following will monitor the list of known workers at this time (substitute your own email credentials, of course):

Code:

./ckPoolNotify.py --verbose --server "smtp.gmail.com:587" --user edonkeycoin@gmail.com --users "1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX" --workers "1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.philipma1957sticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.edonkeystick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.VirosaGITSdonation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.notlist3dstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.larry12stick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.larry12s5donation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.vapourminerstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.fullzerostick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Jake36stick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.TheRealStevestick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.alienesbstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Chris_Sabianstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.Ecnadstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.bmoscatosticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.mikestangstick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.baktegonUnit01,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.slimepuppysticks,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.slimepuppydonation,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.peptostick,1JiWuyX94wrCr7JhkAn7x5qNMCEef1KhqX.kipper01"

At some point I'll support a config file to make it easier to manage a large list of workers.

If you're using the script and you want to update to a new version, all you have to do is stop the current script, replace it with the latest, then start it up again.

If you're on the Mac and you opted to set up the script as a daemon, then you'll have to unload and reload the daemon. Here's the basic command lines to use (replace the path to the new script before using):

Code:

# Copy the updated version over the old
sudo cp -rp ~/ckPoolNotify /Library/Application\ Support

# Unload and reload the daemon
sudo launchctl unload /Library/LaunchDaemons/org.edonkey.mining.ckpoolnotify.plist
sudo launchctl load /Library/LaunchDaemons/org.edonkey.mining.ckpoolnotify.plist

One odd thing I noticed while testing the latest is that none of the pool workers have a 7 day hash rate average. I don't know why this is. Maybe if there are any club members that have less than 7 days in, then none of the 7 day averages for the others get reported?

It might not matter if we rely on the 1 day average, or if we add a mechanism to remember a few days worth of hash rate (which Phil suggested).

There's not even a 7 day average listed on the pool, so that would have to be something a script would need to keep track of 1 day and add up, to report on.

[-ck]

There's not even a 7 day average listed on the pool, so that would have to be something a script would need to keep track of 1 day and add up, to report on.

No I never envisioned people would need that data per worker.

[baktegon]

Got my 2.0 hub in, sticks are now mining on the Rasp Pi!

I still can't minera to see my sticks however....so I'm just running cgminer from the cmd line.

Also, i can't seem to access the sidehack pool but i can access regular ckpool? Any ideas what i've done wrong?

http://postimg.org/image/ei35w3cop/

[Jake36]

Got my 2.0 hub in, sticks are now mining on the Rasp Pi!

I still can't minera to see my sticks however....so I'm just running cgminer from the cmd line.

Also, i can't seem to access the sidehack pool but i can access regular ckpool? Any ideas what i've done wrong?

From the image, looks like everything is right for the pool (except for maybe change the Unit01 to Stick01 or even just stick, makes it easier to keep track of that they are sticks or if it's donated hash).

If your trying to start with both pools in the command line, while you are in the screen in the pic, try using the "a" and just add a second instance of the club pool again; if it works, it narrows down where to start looking.