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

[cashclash]

Block 10.000 soon the Wallet might explode

[1715420334]

1715420334

[1715420334]

1715420334

[1715420334]

1715420334

[1715420334]

1715420334

[WORE]

Block 10.000 soon the Wallet might explode

 

What's in a name?


"blocks" : 10000,
"difficulty" : 78.48539711,

[wr104]

Wallet didn't explode   

[cashclash]

"networkhashps" : 7366
nonce pool at 5,536.48 KH/s

Out of the 20 last Blocks 11 went to the 1830KH/s kinda odd since double as much should have gone to the pool am i right?

[WORE]

"networkhashps" : 7366
nonce pool at 5,536.48 KH/s

Out of the 20 last Blocks 11 went to the 1830KH/s kinda odd since double as much should have gone to the pool am i right?

Too much unknown in that, there was a period where work was unavailable through the pool and I know the dev is watching intently for debug purposes and while working on sgminer/khc build with 2 290's, so expect to be wrong.   The pool is not running stratum.

[WORE]

"networkhashps" : 7366
nonce pool at 5,536.48 KH/s

Out of the 20 last Blocks 11 went to the 1830KH/s kinda odd since double as much should have gone to the pool am i right?

Too much unknown in that, there was a period where work was unavailable through the pool and I know the dev is watching intently for debug purposes and while working on sgminer/khc build with 2 290's, so expect to be wrong.   The pool is not running stratum.

pool seems to have sometimes a little lag when giving new work
this is good for solominers, they will get all the blocks when it happens

I've actually noted more than just a little lag, last night I let it hash there all night, when I got up and checked my miner was hashing away but the pool didn't credit anything for over 100 blocks.  Now tonight I saw my miner setting there waiting for work, restarted it and got work but also checked the pool and I was 1 of 2 miners so it looks like they know there is something going on as it looks like they bounced the server...

[cashclash]

All i see is Blocks should i be surprised, no explosion or implosion yet, whats wrong dev? 

[WORE]

All i see is Blocks should i be surprised, no explosion or implosion yet, whats wrong dev? 

I'll spare dev your beckoning of him for a response:  You were and most probably always will be; wrong, -that is all.

[SpeedDemon13]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

[WhyMe]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

Full config with one 6950@6970 :
x11 = 195w
khc = 240w

[cashclash]

All i see is Blocks should i be surprised, no explosion or implosion yet, whats wrong dev? 

I'll spare dev your beckoning of him for a response:  You were and most probably always will be; wrong, -that is all.

You are not a funny man, i saw lots of Blocks being solved fast and wanted to encourage new Miners.

[WORE]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

Full config with one 6950@6970 :
x11 = 195w
khc = 240w

I'd bet this could be improved upon.  Unlike BTC wallet, KHC does not generate 'dummy work' when there is none so that is a big bonus for solo miners but while pointing at the pool I have yet to see my miner go idle when there is no work available, aside from that KHC is quite new being a 320bit hash so the miner kernel could potentially be optimized quite a bit more than it is.  Took a while before a DRK (x11) optimized kernel was released with sgminer, and it was improved upon further recently.

[WORE]

All i see is Blocks should i be surprised, no explosion or implosion yet, whats wrong dev? 

I'll spare dev your beckoning of him for a response:  You were and most probably always will be; wrong, -that is all.

You are not a funny man, i saw lots of Blocks being solved fast and wanted to encourage new Miners.

Well, bummer.  No future as a comedian, but then again I'd probably have to be interested in that.  Blocks have been flying by, block 10k came and went, as long has the diff algo adheres to dev's design nothing is wrong, at least with the wallet allegedly exploding or imploding.

[jasemoney]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

Full config with one 6950@6970 :
x11 = 195w
khc = 240w

I'd bet this could be improved upon.  Unlike BTC wallet, KHC does not generate 'dummy work' when there is none so that is a big bonus for solo miners but while pointing at the pool I have yet to see my miner go idle when there is no work available, aside from that KHC is quite new being a 320bit hash so the miner kernel could potentially be optimized quite a bit more than it is.  Took a while before a DRK (x11) optimized kernel was released with sgminer, and it was improved upon further recently.

with the newer kernel switching on the fly miners this could be very interesting. you could mine this until a blocks solved, then while theres no dummy work it could switch kernel over to any stratum server, then flip back when it notices work available from KHC. with 3 minute blocktimes there will still be plenty of idling. or if you didnt want to mine something else and deal with pool/kernel changes... the first powersaving improvement would be to stop the GPU from trying to hash the nothing and go to idle while waiting for the next work.

[nonce-pool]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

Full config with one 6950@6970 :
x11 = 195w
khc = 240w

I'd bet this could be improved upon.  Unlike BTC wallet, KHC does not generate 'dummy work' when there is none so that is a big bonus for solo miners but while pointing at the pool I have yet to see my miner go idle when there is no work available, aside from that KHC is quite new being a 320bit hash so the miner kernel could potentially be optimized quite a bit more than it is.  Took a while before a DRK (x11) optimized kernel was released with sgminer, and it was improved upon further recently.

with the newer kernel switching on the fly miners this could be very interesting. you could mine this until a blocks solved, then while theres no dummy work it could switch kernel over to any stratum server, then flip back when it notices work available from KHC. with 3 minute blocktimes there will still be plenty of idling. or if you didnt want to mine something else and deal with pool/kernel changes... the first powersaving improvement would be to stop the GPU from trying to hash the nothing and go to idle while waiting for the next work.

The GPU does go idle while waiting for the next work, as the pool is running we generate a tx when the mempool is empty, keeping your miners running nearly 100% of the time, you would see the same result if you was to solo mine right now as well.

[jasemoney]

Anyone test the power consumption of the algo versus X11 and other algos? Just curious about the results...

Full config with one 6950@6970 :
x11 = 195w
khc = 240w

I'd bet this could be improved upon.  Unlike BTC wallet, KHC does not generate 'dummy work' when there is none so that is a big bonus for solo miners but while pointing at the pool I have yet to see my miner go idle when there is no work available, aside from that KHC is quite new being a 320bit hash so the miner kernel could potentially be optimized quite a bit more than it is.  Took a while before a DRK (x11) optimized kernel was released with sgminer, and it was improved upon further recently.

with the newer kernel switching on the fly miners this could be very interesting. you could mine this until a blocks solved, then while theres no dummy work it could switch kernel over to any stratum server, then flip back when it notices work available from KHC. with 3 minute blocktimes there will still be plenty of idling. or if you didnt want to mine something else and deal with pool/kernel changes... the first powersaving improvement would be to stop the GPU from trying to hash the nothing and go to idle while waiting for the next work.

The GPU does go idle while waiting for the next work, as the pool is running we generate a tx when the mempool is empty, keeping your miners running nearly 100% of the time, you would see the same result if you was to solo mine right now as well.

weird i didnt notice my miner slow down when solo. will investigate

[WORE]

all the "cool" coins are now X something, xmr, xpy...
so should we start calling this one xhc and xryptohash

This is not a scrypt or standardized x[y] scrypt coin.  It is a new algo that can be modified to combat the idea of the asic, and with pid to control diff, it is in a class by itself, beyond that it complies with new standards.  It does not need an 'X' to be 'cool', it has that all on it's own.

[mrmanager]

all the "cool" coins are now X something, xmr, xpy...
so should we start calling this one xhc and xryptohash

This is not a scrypt or standardized x[y] scrypt coin.  It is a new algo that can be modified to combat the idea of the asic, and with pid to control diff, it is in a class by itself, beyond that it complies with new standards.  It does not need an 'X' to be 'cool', it has that all on it's own.

This is why I decided to bring my GPUs out of retirement.

It looks like someone has bought up quite a few sells on lazycoins.

[wr104]

all the "cool" coins are now X something, xmr, xpy...
so should we start calling this one xhc and xryptohash

xLOL

[xinbinbin]

all the "cool" coins are now X something, xmr, xpy...
so should we start calling this one xhc and xryptohash

xLOL

Development, you want to go on holiday, came back for Christmas?