OK, I am pretty sure that Diamondcoin on my pool is on the correct blockchain (transactions are visible in Diamond block explorer + when I synced Windows wallet as per steps on DMD OP, I can also see transactions).

I hope it will stay this way. We'll see.

As for the previous payouts... I have about 300 DMD that were not paid out while DMD blockchain was stuck. I'll pay them out manually once the network settles down.

PS: The automatic payment should be working ok now, for example see: http://diamond.danbo.bg:2750/tx/1ac84c0f2ee8970054fb18460948b7430efd7680ad021ae3689e4d1e9951ba11#i6

SaffronCoin Coin new wallet v2.4.1 or v1.3.4 classic
http://saffroncoin.com/#wallets

<sfrdev_mob> These versions disconnect the older clients who haven't updated
<sfrdev_mob> Do note that you need to redownload the blockchain

current block is 171823

These are the DMD payments that I sent 5 minutes ago for the time that payments were stuck (31 July - 1 August).

If you are not in the list, please PM me with your DMD wallet address and hashrate (don't write in the thread), I'll check the logs and we'll resolve this.

dFqhVwNJVUoGnWyEAXunyTHzfwbF8dQmq3     0.121777
dVgn7vLJRNUn7oTTfqHHAbTU2YYsTd9C5H      14.2546
dYZfJWNn9tNd9dkxdeUZrL4FsNVAVxnh37     17.9042
dcWh5R6H698nb8CyA2mTmaJAVQ1NbeRxrk     1.715
dWB4uGp3JGk5TdLCSGMWjWprc3gaHJFxtw     5.0574
dFrbh72KkG9nJq5CcERK7enKVYXuV4hic5     15.2376
dP3JvmgUwaSRRBnPPLqCQADYpbJzfokiaC     15.1495
dPMEbYG6xyvwbznQvGeJq7mVpKoPqM7Sci    10.8993
dN5Uw5EJYApoaJqXqwFuq7oV2fe4pqim88     13.3596
dYnvY8M84AMkq2o6K3wQPSAfpCY4w8G4fw     8.6143
dLR8LaWySojvi3dmaB9ioz48eSzFqVGRDx     84.7235
dT9xGBQMFNsEet3uTbzLEhShPKoPaqH8J7     7.5302
dNq11HoLRZfCoFiSQcwrfAMRPSncL6QE3D     18.6692
dQUwgS3RZDqEnsdDgTdjPKuH3yJgBSGTtC     3.0153
dH5rj9E148FsgyYpxPUjE3ezSUapz5PyV4     14.4223
dX37iCdhQHgwnyAVGjcraYgNwg11XrudbF     4.7944
dZgy55s3LXhhkx66dYYSMEKhtdFYgKBFzm     3.4591
dE4iqdxASGxVhW6EnU9hYJwi5ACr4ABnAn     23.7168



Thanks!

Thanks a lot for your great job !

Weird... I can't reach 15MH with 6970... -g 4 slightly improves speed but top is 13MH, older badman built sgminer 4.0 (from march 26th) gives 15Mh on 6970

I'll try to change opencl files to see if there is difference

Hey, fellow krypto geeks!

DOKDO?? It's alive and well. I exchange regular emails with the lead dev. But the English-language community is tiny, so trading is manual. But I have been following the coin for months now, and have confidence in the dev team. Indeed, we have had some bad luck (the first English-language exchange went belly up . . . ); but apparently btc  kor will be online withing days.

Mark (IndiaMikeZulu); Western Australia

You can find us https://cryptocointalk.com/topic/6872-dokdocoin-dokdo-information/page-16

bat file is:

In the wallet I only changed wallet address and removed gpu-core/mem settings
With older sgminer I use -g 4 -w 256 -I 20

@srcxxx

Pretty new to Linux here but I have to say something at least.

I made a build from your github repository today.
It was the easiest, CLEANEST build I've done in my 3 months using Linux. (no errors/warnings)

It looks like you spent some time developing and delivering a quality product.

Nicely done 

> Running on older sgminer speed is 14.1MH/s with 14.6 and 14.8MH/s with opencl files from 13.12
> Same conf&bat run from grs-sgminer gives 12.3MH/s
> Running myriadcoin-optimized the speed is a bit lower ~ 11.9-12MH/s
> Also tested on 5850 - no gain either. But on 290 the speed increase is stunning

Hi!

OK, looks like the kernel is not good for the old hardware that you mentioned.
So I don't recommend that you use grs-sgminer.
I'm quite surprised that just plain myriad-groestl is slower in grs-sgminer, because it is based on OpenCL kernel from sph-sgminer.
Anyways, I'm working on completely different groestl algo and hoping it'll be a lot faster.
In the meantime, I recommend that you use your old miner and some other pool.
I will post to coin threads once I have a faster miner.

Thanks for your time.

"thread concurrecy" is actually a buffer size, which is used only on scrypt, as far as I now.
surely not on groestl.