It makes absolutely no difference to the hashrate since work generation is done on the miner. The frequency of getblocktemplate requests correlates with the amount of transactions you are likely to include from the current set of transactions. The more frequently you do it, the more transactions on average you will have. It is the pool/pool software that determines the frequency of GBT requests. Stratum stipulates updates should occur every minute and usually the pool software will have an updated set of transactions along with each stratum update, but there is nothing stopping the pool from just sending the old set of transactions every minute. Most pools send out a new set of transactions every minute; p2pool does not, usually waiting longer, and ckpool defaults to doing it every 30 seconds which is why the ckpool instances out there have more transactions on average (it also NEVER generates transaction free work templates).

Once more, I'm very sorry to see you go but certainly understand your reasons which are very sound and sensible. You've been an upstanding part of the bitcoin community who ran a very solid outfit with this pool. I wish you well with whatever further ventures you choose and hope they involve bitcoin in some other way.

32bit processor? There's no 32 bit support in ckpool code.

Restarted pool with newly coded in M of N multisig address (i.e. starting with 3) support. This code is still fresh so there is a small chance of instability due to the new changes but I'll be watching it very carefully.

Very sorry about the inconvenience but I'm sure no one would have liked to have mined a block they never received...

Mine on!

0.5% which is only 0.125BTC

A private entity had a unique solo instance that was signed avahuobi (but still said ckpool).

I've released a new version of cgminer 4.9.2 which should hopefully work a little better with these, but there's only so much software can do to compensate for hardware designs...

New release: Version 4.9.2 - 12th June 2015

Long term stability updates, clean ups and driver updates.


Human readable changelog:

- Various drivers that failed to initialise (notably Antminer U3s) have been fixed by addressing various low level detection issues with other drivers.
- Blockerupter tube driver has been disabled by default in binary builds since it's broken, and the configuration advises against it.
- Fixes for various BFL devices not being properly recognised.
- Getwork support has been completely REMOVED. Only local work generation protocols are now supported (stratum, GBT and solo mining). No pool should be providing getwork support in the modern mining era anyway.
- Queue option has been REMOVED. The option is now silently ignored to not break existing configurations but no more will any antminer binaries be able to set it to 8000 or something stupid. Any attempt to tune this value is pointless and dates back to getwork.
- Expiry and scan-time have also been REMOVED. They are irrelevant with local work generation and asic mining speeds and no getwork.
- failover-only option has been REMOVED. As per above.
- Pool failover has been cleaned up without getwork
- Default Antminer U3 voltage has been changed to 775 since 750 is rarely enough to get 2nd generation ones running at full speed.
- U3 will USB reset on no shares for 2 seconds instead of 1.
- Major antminer S1/S2/S3 driver updates courtesy of kano. Use his provided firmware links.
- Systemd support courtesy of Gabe Evans
- Update to latest libjansson with custom fixes imported from ckpool
- Support for building with system libjansson (dunno why you'd want to do this so it's advised against in the config option but it seems people want useless stuff and it's harmless) - Gabe Evans
- SP30 uses applog instead of printf -  Gabe Evans
- Make json rpc requests valid -  Gabe Evans
- Syslog limits to logging - Gabe Evans
- Build configuration fixes for building from git with newer systems.
- Support mining.reconnect with port as a string or value.
- Numerous clean ups and fixes to minimise risk of invalid memory operations in the code.
- Fix for a rare crash on pool switching during failover.


Full changelog:

- Only blacklist devices on iManufacturer if they don't have an iProduct
- Simplify the pool work choice switching now that only local work generation is
supported
- Check for absense of stratum notify on stratum pools to see if they're usable
- Remove getwork support
- Remove test for localgen since all work will be
- Deprecate failover only option in anticipation of removing getwork
- Deprecate expiry option and fix it to 10 minutes, replacing all deprecated
config calls in the API with a deprecated message
- Deprecate scan-time which is irrelevant with ASIC speed mining
- Deprecate opt_queue since all mining is now local work generation which is
rapid and it serves no useful purpose to generate work that is potentially
stale, increasing CPU usage to check it before using it
- Change default au3 voltage to 775 to more reliably run at default frequency
- Set correct timeout for AU3 in icarus_detect_one though it won't affect
functioning
- Blacklist LIX device which doesn't exist
- Round up fail time to next highest integer on icarus
- AntS3 - set default work delay
- add pool block quality to api
- AntS3 - redo work send/stats and add a tuning option - not yet tuned
- Ant - ignore useless options in case they are passed
- AntS3 - initial S3 merge basic support
- Ant voltage isn't S1
- API - restore IPv4 address .0 padding and update copyright dates
- ants2 - separate freq from options
- ants2 - make it compile :p
- ants2 - add voltage
- ants2 - remove libusb/udev dependency since it doesn't use USB
- AntS1 ensure correct endian and correct wid
- libsystemd: Notify watchdog
- libsystemd: Notify run state and status line
- Catch SIGABRT signal and exit gracefully
- Add libsystemd configure option (default disabled)
- Document --with-system-jansson configure option
- SP30: Fix logging to use applog over printf calls
- Allow building with system jansson
- Set request ID in validateaddress JSON-RPC request.
- Cope with reconnect being sent a port number as an integer or string
- Added syslog mask to limit amount of output
- regressed with "BAL" little-jalapenos
- Add yet more whitelisting of BMA devices, removing the case insensitive match
for manufacturer
- Fix detection of no mining device configuration.
- Remove LT_INIT from configure which breaks ltmain.sh detection for some
automagic reason
- Add missing hashtable_seed file
- Add missing file
- Speed up shutdown by decreasing usb poll time to 100ms and using no timeout on
exit
- Cope with attempted reuse of strings in input_pool
- Manage failed URL entry at startup more gracefully, adding stratum+tcp://
automatically if http:// isn't specified
- Fix various symbol size change warnings
- Import jansson updates from ckpool
- Check for attempts to copy to/from null in cg_memcpy
- Use cg_memcpy throughtout bitfury driver
- Use cg_memcpy throughout cgminer.c and util.c
- Use alloc helper in miner.h
- Use alloc helpers in bitfury driver
- Use alloc helpers in spondoolies drivers
- Use alloc helpers in bflsc driver
- Align_len in all alloc helper calls
- Use align_len in all alloc helpers
- Use alloc helpers in usbutils
- Use alloc helpers in icarus driver
- Use alloc helpers in avalon4 driver
- Use alloc helpers in api.c
- Use the alloc helpers in util.c
- Convert all users of alloc to use the helpers in cgminer.c
- Add helper functions to various alloc functions that automatically check for
failure
- Fix rare dereference error on pool stratum queue

We've both said numerous times, there is no valid solution to its most significant scalability problems. Pooled mining is a solution to the variance of solo mining - the more miners there are the less the variance. p2pool is the anti-solution to pooled mining - above a certain size, the more miners there are, the more variance there is; it is just solo mining on a smaller scale. It doesn't matter how much money you throw at us, we can't solve this problem in its current form. Rewriting the p2pool software in a scalable language like C only makes each node able to handle more miners - and that's not really important since the idea is each miner runs their own node for their own hardware. It does not solve the design issue.


Kano's ckpool runs ckpool software which is absolutely all free and open code. Centralised it may be, but closed it most definitely is not.

It seems there was a hardware issue overnight and the provider corrected it and restarted the machine. Apologies for the outage. While mining is working again, I will restart the pool shortly as a precaution though most of you won't fail over during the restart.

Thanks. It's recognising it fine and running it as a monarch so if it's not working then they changed the protocol and, well, there's no sign of any updated protocol documentation and I do believe all communication channels between the cgminer development team and BFL have effectively been severed so... fuck.

https://www.blocktrail.com/BTC/tx/e314f49c56f85eba3776ef36021640a064b998650b32b11a548eca2e30b0d5ab

{"hashrate1m": "776T", "hashrate5m": "685T", "hashrate1hr": "671T", "hashrate1d": "582T", "hashrate7d": "195T"

Check out the diff on that one...

My guess is yet another USB identity to confuse cgminer further, possibly even intentionally from their end. Do the usual and get the dump of adding "-D -T 2>log.txt" to your cgminer commands on startup and dump the contents of log.txt here to see what cgminer makes of it.

Glad you like it. The first cgminer release I put it into was version 1.3.0, Jul 19 2011

The antminers use a variant of cgminer which I created.

The pool strategies include a strategy of switching called "rotate" which I put in the code in Jul 20 2011.

You are recreating the wheel and adding an extra tool to do what cgminer already does.

Congratulations to 15xrck4w1yyfGyjLugM2Ppsvy6yb9fLGQP

https://www.blocktrail.com/BTC/tx/b8fc072e6c82167989a96cf57a2f5b881c89810b40ebc1f42b38b46f46129ff0

Use their dedicated pool thread please.

immaminer you are still trying to log in unsuccessfully


In addition, dear user trying to log in with the following:
1N8CDMDK6yhsmRW9k1bHJTGLnzwbbz9RPn1N8CDMDK6yhsmRW9k1bHJTGLnzwbbz9RPn

It appears you have input your bitcoin address twice and it is invalid and you are unable to mine.