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.
Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 57. (Read 149437 times)
December 08, 2014, 12:36:57 AM
December 07, 2014, 11:26:33 PM
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? 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
December 07, 2014, 10:22:58 PM
Is the wallet turned off for mining currently.
December 07, 2014, 10:05:14 PM
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
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
December 07, 2014, 09:49:59 PM
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....
December 07, 2014, 08:39:01 PM
Unfortunately, this is not our first rodeo. We had to do the same thing at block 5000 and miners here understood.
December 07, 2014, 07:30:33 PM
Working on a new Wallet version 0.3.6 to fix the Diff algorithm once again. Will hard fork at block 5599.
December 07, 2014, 07:25:59 PM
tough crowd
Now again stop mining ? December 07, 2014, 07:21:54 PM
tough crowd
December 07, 2014, 06:21:32 PM
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.
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.
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.
December 07, 2014, 06:04:09 PM
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.
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.
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.
December 07, 2014, 05:26:20 PM
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.
December 07, 2014, 04:55:28 PM
"ASIC-mining dominance has been asserted by mining pools over the past few years for various cryptocurrencies. The uptick in ASIC-resistant algorithm usage has participation from altcoins like Heavycoin and Ultracoin. Vertcoin is going so far as to completely changing their coin’s mining algorithm..."
http://www.coinssource.com/kryptohash-joins-anti-asic-alt-coins/
http://www.coinssource.com/kryptohash-joins-anti-asic-alt-coins/
December 07, 2014, 04:43:59 PM
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?
December 07, 2014, 04:09:47 PM
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
Well now, if you are better at migrating old code from 256bit hash to 320bit, then get off your hands and show us all what you got.
December 07, 2014, 04:00:14 PM
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
Thanks for the feedback. Those are exactly my thoughts ATM.
December 07, 2014, 03:46:41 PM
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
Patience! Especially when one is given something for free.
Now tell me, what videocards do you have, what error messages are you getting?
December 07, 2014, 03:44:13 PM
@tacee - you are mining now?
December 07, 2014, 03:21:21 PM
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
December 07, 2014, 03:09:53 PM
I don't why my miner is aways HW and WU is 0.0/m 
Jump to: