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

[wr104]

What about the --gpu-dyninterval option? Does it make sense to play with or is the default value always the best? Are there any other options except shaders and multiplier that can possibly affect the hashrate?

The most important options in cgminer-khc are 'shaders' and 'shaders-mul'.  The former has to match be the number of stream processors in your GPU, the latter is the number of consecutive OpenCL threads per stream processor.

If your GPU has 2048 Stream Processors and you select 8 for 'shaders_mul', the KSHAKE320 OpenCL Kernel will simultaneously run 16384 threads every time the Kernel is executed.  Now, the current KSHAKE320 algorithm requires 64Kb per thread so, in order to run with with 8 for shaders_mul, your Video card needs at least 1Gb of available VRAM.

The other parameters that can affect your mining is the --expiry and --scan-time which are both set to 30 sec by default.   I would not go below 10 seconds for expiry because, cgminer resets the Nonce back to zero every time it calls "getwork" and gets a new block template.
 

I haven't played with the --gpu-dyninterval option. I do see that it changes the dynamic inside the opencl_scanhash() function but, I'm not sure that if changing this option will have a positive effect on performance.




 

[Riseman]

Thanks. I use the actual amount of shaders of my GPU and the highest multiplier it can start with (16). So the miner consumes about 3GB VRAM.

The other parameters that can affect your mining is the --expiry and --scan-time which are both set to 30 sec by default.   I would not go below 10 seconds for expiry because, cgminer resets the Nonce back to zero every time it calls "getwork" and gets a new block template.

Does it mean that when a new block arrives all the miners in the network start hashing from the same nonce value? I think it's quite impractical because in this case solving the block is not a matter of luck at all but purely a matter of hashrate. So the slower miners have no chance of finding the correct hash first if I got it right.

[wr104]

Thanks. I use the actual amount of shaders of my GPU and the highest multiplier it can start with (16). So the miner consumes about 3GB VRAM.

The other parameters that can affect your mining is the --expiry and --scan-time which are both set to 30 sec by default.   I would not go below 10 seconds for expiry because, cgminer resets the Nonce back to zero every time it calls "getwork" and gets a new block template.

Does it mean that when a new block arrives all the miners in the network start hashing from the same nonce value? I think it's quite impractical because in this case solving the block is not a matter of luck at all but purely a matter of hashrate. So the slower miners have no chance of finding the correct hash first if I got it right.

Miners in the network never receive the same exact block. Few things always change, like the nTime value which updates every time you call getwork.  Also, the first TxOut in the block is always the coinbase and this TX contains your unique public address.

[wr104]

tough crowd

[z38630610]

tough crowd

Now again stop mining ?

[wr104]

Working on a new Wallet version 0.3.6 to fix the Diff algorithm once again.  Will hard fork at block 5599. 

[wr104]

Unfortunately, this is not our first rodeo. We had to do the same thing at block 5000 and miners here understood.

[Atomicat]

Unfortunately, this is not our first rodeo. We had to do the same thing at block 5000 and miners here understood.

...and patiently compose a haiku.


The B that is an 8
Fuzzy logic softens the head-desk hammers
End is just the Start

Edit:  Ohmmmmm....

[wr104]

At 103 Diff, the mining the block I need for the fork is taking hours  

It seems, there won't be a new wallet till tomorrow.

Edit: Wait a min.  I just realized that I don't need to mine it.  I can put whatever I want in the checkpoint   

[antonio8]

Is the wallet turned off for mining currently.

[xinbinbin]

At 103 Diff, the mining the block I need for the fork is taking hours  

It seems, there won't be a new wallet till tomorrow.

Edit: Wait a min.  I just realized that I don't need to mine it.  I can put whatever I want in the checkpoint   

Trading platform wallet was closed, can solve?

[wr104]

As soon as the new wallet becomes available tomorrow, the trading platform will reopen.

The fork at current diff is taking longer than I was expecting.

[wr104]

Fork is ready. I'm compiling Wallet 0.3.6

[WORE]

Fork is ready. I'm compiling Wallet 0.3.6

So, I've been mining this whole time and you are hard forking it again?  (no I'm kidding)


Yay.  And for everyone repeatedly asking if the mining has opened again, no!  Not until tomorrow...    And certainly not when the new wallet has been released.  No way...   


(Think they bought it?)

[wr104]

I'm going to have to continue tomorrow.

There are few issues with the checkpoint that I have to address before I can release 0.3.6

I ask for your patience.

[WORE]

I'm going to have to continue tomorrow.

There are few issues with the checkpoint that I have to address before I can release 0.3.6

I ask for your patience.

You know my position, take your time, get it right.

[wr104]

New Wallet version 0.3.6 - MANDATORY UPGRADE

https://github.com/kryptohash/kryptohash/releases/tag/v0.3.6

VERY IMPORTANT

1) Backup your wallet.dat file.  
2) Execute kryptohashd or kryptohash-qt with the --reindex  parameter for ONE TIME to allow the wallet to fork correctly at block 5600.

Note: If your wallet gets stuck reindexing at block 3599 (seen with the Linux wallet) then, you need to download the entire blockchain.

[xinbinbin]

New Wallet version 0.3.6 - MANDATORY UPGRADE

https://github.com/kryptohash/kryptohash/releases/tag/v0.3.6

VERY IMPORTANT

1) Backup your wallet.dat file.  
2) Execute kryptohashd or kryptohash-qt with the --reindex  parameter for ONE TIME to allow the wallet to fork correctly at block 5600.

Note: If your wallet gets stuck reindexing at block 3599 (seen with the Linux wallet) then, you need to download the entire blockchain.

Block card in 5608? Don't go block, no platform Wallet

[wr104]

Waiting for work from Pool 0

block 5608 stuck?

need some more explanation what is happening, people may be able to help.. like to follow new try, new algos

Currently, there are no transactions on the network.

Unlike bitcoin and other altcoins, the Kryptohash wallet will not give miners "dummy" work when the transaction mempool is empty.  I'm setting up one of my wallets to being sending 1 TX every 10 mins.

[antonio8]

And we're off.

EDIT: Just found a block