You mean with blockmaxweight right?

@-ck

I get a segfault with ckpool-splns. It is easily reproducible and so is the fix.

When starting with empty/nonexistant log directories and sock directories, ckpool starts but segfaults as soon as it connects to a bitcoind.

Fix I stumbled upon is to run non-splns ckpool for a bit, then close and run ckpool-splns. No segfaults.

Sorry if this is documented somewhere. Bitbucket seems to have been a mess lately.

@Blokforge can you confirm whether or not PayPal wul be acceptable for us based orders when the time comes (today, tomorrow)

Got it. So if I compile and run the splns fork I can expect it to work like your splns pool @ ckpool.org?

so, ckpool-splns changes that control the coinbase generation are in stratifier? Is it all documented only in code? or also in a readme somewhere?

is that fork public?

edit: nevermind i found it

hi ck and kano

sorry to hear about the falling out.

without ckdb, there's no "easy way" to have ckpool set the generation address to the address of the user who finds it, right? And ckdb is still "as-is" in this repo?

@Claymore is there any expected power consumption differences between ASM 1 and ASM 2?

This could be a matter of tweaking, but the new GG ASM kernels reported similar performance locally as Claymore, but at the pool the performance was not as good. Higher rate of stale shares as well. (I also realize are other factors that could have lead to this). I'm talking in terms of 24 hr averages. Lower power consumption than Claymore though, which is nice.

This was on pre4 with the initial ASM stuff dropped in on windows 10. I will test out the pre5 release this week sometime.

I dropped your new files in over top of version pre4 and am also seeing a 1-1.5 mhs boost on my RX 470s and 480. Did not try on R9 390, but it was already performing as good as Claymore ever had.

some additional info:

R9 390 with gateless gate & ethash-new = 31.9-32 mhs. xI of 1920, worksize 192, 2 threads

This is the same or better performance I get from Claymore. I am getting slowly increasing HW errors, but no rejected shares or issues shown at the pool side.

This card has +6.5% core clock and 1550 mhz memclock. Drivers are 17.3.2 on Windows 8.1.

ethash-new working well here. Using your parameters I get:

RX480 (4GB) = 27.x mhs
RX470 (4GB) = 24.x mhs

Cards have custom memory straps, underclocked cores, and overclocked mem. With Claymore I get reported RX480 (4GB) = 28.9 mhs and RX470 = 26.x mhs with same clocks. Can probably tweak the gateless gate/ethash-new setup.

One interesting thing to note is that with Claymore, a graph of GPU load spikes up and down. With gateless/ethash-new it is flat at 100%. Some initial test seems to indicate the load will spike when only one thread, but will flatline at 100% when 2 threads are used.

I did not yet check power consumption.

Same, although it seemed to work on nicehash...

Have been following this thread for a few weeks. Most of this is above my head. I do understand that there are improvements being made. 2 really basic questions though...

1) Do these improvements only help equihash? or would they boost all algorithms? specifically interested in ethash/daggerhashimoto.

2) Are these improvements only available on linux or would they translate to windows as well?

From 20878 zip code

H81 Pro BTC Motherboard - 0.1 BTC

Phenom II X4 965 BE - 0.05 BTC

Athlon II X4 620 - 0.025 BTC

4GB DDR3-2400 G.skill RAM - 0.03 BTC

Asus R9 270 DirectCU II OC - 0.03 BTC

Shipping not included in any price.

Escrow by request.

Buyer pays shipping and escrow (if requested).

Is the 1000W a RM, RMX, or RMi? Also, pic?

PM Sent

Shutting down Luckypool.co for lack of use.

Claymore this is definitely not a trojan yes?

EDIT: just saw you confirmed and edited first post. Thanks