[ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif

[nigttran]

Many many errors. Hic hic.

I'm wait fixed

[wr104]

Many many errors. Hic hic.

I'm wait fixed

If you won't tell which errors, I won't be able to fix them.

[vntiange]

CG show difficulty 2, wallet display difficulty ": 31.99957275, synchronize the 5609 piece, suddenly have 26 hours block to synchronize again...
 

[wr104]

CG show difficulty 2, wallet display difficulty ": 31.99957275, synchronize the 5609 piece, suddenly have 26 hours block to synchronize again...
 

Let me see the getinfo

[cashclash]

same here with 26h sync and nothing happens restarted wallet a few times and now im 27h back

18:14:34

getinfo

{
"version" : 30600,
"protocolversion" : 70003,
"walletversion" : 10500,
"balance" : 0.00000000,
"blocks" : 5611,
"timeoffset" : -2,
"connections" : 8,
"proxy" : "",
"difficulty" : 31.99957275,
"testnet" : false,
"keypoololdest" : 1417874009399,
"keypoolsize" : 102,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""
}

[Atomicat]

CG show difficulty 2, wallet display difficulty ": 31.99957275, synchronize the 5609 piece, suddenly have 26 hours block to synchronize again...
 

Same here, block 5611, network traffic twitches but that's it.  Interesting that cgminer is cranking away, for better or worse.  71Kh/s from the 7950, 125Kh/s and an occasional error from the 290.  Ha!  Just said it found two blocks, still at 5611 though and nothing in the transactions log.  Think I"m gonna update my drivers.

"version" : 30600,
"protocolversion" : 70003,
"walletversion" : 10500,
"balance" : 0.00000000,
"blocks" : 5611,
"timeoffset" : 0,
"connections" : 3,
"proxy" : "",
"difficulty" : 31.99957275,
"testnet" : false,
"keypoololdest" : 1418052350074,
"keypoolsize" : 101,
"paytxfee" : 0.00000000,
"relayfee" : 0.00010000,
"errors" : ""

"blocks" : 5611,
"currentblocksize" : 1864,
"currentblocktx" : 3,
"difficulty" : 31.99957275,
"errors" : "",
"genproclimit" : -1,
"networkhashps" : 1402,
"pooledtx" : 3,
"testnet" : false,
"generate" : false,
"hashespersec" : 0

[Atomicat]

Just got up to date!

Edit"  And now we seem to be back to waiting for work, ah, there we go, and a block found but not showing up in transactions, still showing block 5612

[cashclash]

nvm the 27h just went away

[cashclash]

@Atomicat
which r9 290 do you have and what settings do you use for them?

[antonio8]

You have to ignore the read out in cgminer since this coin is coded different.

When you find one and it is accepted then it will show accepted in cgminer.

Been discussed a few pages back.

[vntiange]

Accepted 066f3670 Diff 39/31 BLOCK!
On the block 5613 at present, there is no display to synchronize again.

[Atomicat]

@Atomicat
which r9 290 do you have and what settings do you use for them?

It's an XFX I just picked up last week.  Cards max out at --shaders 1792,2560 --shaders-mul 9,6.  Got three New block detected's so far and four Found Block's.  Four hardware errors on the 290, none on the other.

Could be card/driver/bios.  I just picked it up and haven't thrashed it into shape yet (damn, no hynix mem!)  I think the person who sold it to me thought they were dumping a lemon.  It had one of those awful blocks for a cooler and my jaw dropped when I saw it was idling at 80C!  But I intended to slap this Thermaltake 2.0 on it anyways, and now it stays under 70 no matter what the voltage or load.  Quite possible he might have cooked it a bit just trying to run anything.

So, one valid block somewhere because I'm at 5613 now.  Going to update those drivers, back in a bit.

[WORE]

@Atomicat
which r9 290 do you have and what settings do you use for them?

It's an XFX I just picked up last week.  Cards max out at --shaders 1792,2560 --shaders-mul 9,6.  Got three New block detected's so far and four Found Block's.  Four hardware errors on the 290, none on the other.

Could be card/driver/bios.  I just picked it up and haven't thrashed it into shape yet (damn, no hynix mem!)  I think the person who sold it to me thought they were dumping a lemon.  It had one of those awful blocks for a cooler and my jaw dropped when I saw it was idling at 80C!  But I intended to slap this Thermaltake 2.0 on it anyways, and now it stays under 70 no matter what the voltage or load.  Quite possible he might have cooked it a bit just trying to run anything.

So, one valid block somewhere because I'm at 5613 now.  Going to update those drivers, back in a bit.

You can only mine on the first card until dev works on the miner.  Everyone with multi card rigs has this problem.

[Atomicat]

You can only mine on the first card until dev works on the miner.  Everyone with multi card rigs has this problem.

Interesting, dropped the mult on the 7950 from 9 to 8, increased hash from 80 to 110 proving that just because you can, might not be good.  Still get hw error on 2'nd card when dropped from 6 to 4.  I'll try starting separate instances, see if that works.  If not, well, that 290 is great for mining Diamond.

[WORE]

You can only mine on the first card until dev works on the miner.  Everyone with multi card rigs has this problem.

I'll try starting separate instances, see if that works.

Has been tried, you may do better if you install 12x/13x drivers.  I didn't go that far because of the increased performance offered with the 14.9 drivers.

[wr104]

Assuming that there won't be anymore unpleasant surprises with the Diff algo, I can now begin working on fixing cgminer-khc.

[antonio8]

Assuming that there won't be anymore unpleasant surprises with the Diff algo, I can now begin working on fixing cgminer-khc.

Have you looked at the sgminer since there have been more improvements to it?

[wr104]

Assuming that there won't be anymore unpleasant surprises with the Diff algo, I can now begin working on fixing cgminer-khc.

Have you looked at the sgminer since there have been more improvements to it?

The latest sgminer 5.0.1 looks very interesting.  I like the fact that VS2013 can be used which for me is a big plus since it is what I use for debugging.   

I'm going to check how hard it would be to add my KSHAKE320 PoW algo into sgminer.

[antonio8]

Assuming that there won't be anymore unpleasant surprises with the Diff algo, I can now begin working on fixing cgminer-khc.

Have you looked at the sgminer since there have been more improvements to it?

The latest sgminer 5.0.1 looks very interesting.  I like the fact that VS2013 can be used which for me is a big plus since it is what I use for debugging.   

I'm going to check how hard it would be to add my KSHAKE320 PoW algo into sgminer.

Awesome. I hope it saves you time and energy.

[slashbinslashnoname]

 ^_^still mining @ 6khs

Edit: automoderate