wr104 (OP)
|
|
December 07, 2014, 03:27:49 PM |
|
Damn. The Diff jumped to 516 I'm going to have to do another hard fork to fix this. I'm about to give up on this new Diff algo. I'm working on a new Wallet v0.3.6. It is going to take few hours. This update your wallet is not tired? Dude! Yes, very tired. [/quote] Network conditions can change quite a bit in 100 blocks, I'd have gone with modified version of KGW. [/quote] Dgwv2 [/quote] Thanks for the tip. I'll look into the DGWv2
|
|
|
|
esotericizm
|
|
December 07, 2014, 04:15:36 PM |
|
Damn. The Diff jumped to 516 I'm going to have to do another hard fork to fix this. I'm about to give up on this new Diff algo. I'm working on a new Wallet v0.3.6. It is going to take few hours. This update your wallet is not tired? Dude! Yes, very tired. Network conditions can change quite a bit in 100 blocks, I'd have gone with modified version of KGW. [/quote] Dgwv2 [/quote] Thanks for the tip. I'll look into the DGWv2 [/quote] I haven't kept upto date with difficulty algo's but DGW3 has been out for quite some time and if i recall correctly going from DGW2 to DGW3 can be a tough ask.
|
|
|
|
wr104 (OP)
|
|
December 07, 2014, 04:38:57 PM |
|
I haven't kept upto date with difficulty algo's but DGW3 has been out for quite some time and if i recall correctly going from DGW2 to DGW3 can be a tough ask.
Thanks for the heads up. That tells me I'm not the only one out there struggling to come up with a good Diff algo
|
|
|
|
ocminer
Legendary
Offline
Activity: 2688
Merit: 1240
|
|
December 07, 2014, 04:41:33 PM |
|
Damn. The Diff jumped to 516 I'm going to have to do another hard fork to fix this. I'm about to give up on this new Diff algo. I'm working on a new Wallet v0.3.6. It is going to take few hours. This update your wallet is not tired? Dude! Yes, very tired. Network conditions can change quite a bit in 100 blocks, I'd have gone with modified version of KGW. Dgwv2 [/quote] Thanks for the tip. I'll look into the DGWv2 [/quote] I haven't kept upto date with difficulty algo's but DGW3 has been out for quite some time and if i recall correctly going from DGW2 to DGW3 can be a tough ask. [/quote] I cannot find the changes from dgwv2 to v3 right now, i just remember dgwv2 was /is working pretty well
|
suprnova pools - reliable mining pools - #suprnova on freenet https://www.suprnova.cc - FOLLOW us @ Twitter ! twitter.com/SuprnovaPools
|
|
|
esotericizm
|
|
December 07, 2014, 04:47:35 PM |
|
Damn. The Diff jumped to 516 I'm going to have to do another hard fork to fix this. I'm about to give up on this new Diff algo. I'm working on a new Wallet v0.3.6. It is going to take few hours. This update your wallet is not tired? Dude! Yes, very tired. Network conditions can change quite a bit in 100 blocks, I'd have gone with modified version of KGW. Dgwv2 Thanks for the tip. I'll look into the DGWv2 [/quote] I haven't kept upto date with difficulty algo's but DGW3 has been out for quite some time and if i recall correctly going from DGW2 to DGW3 can be a tough ask. [/quote] I cannot find the changes from dgwv2 to v3 right now, i just remember dgwv2 was /is working pretty well [/quote] https://github.com/darkcoin/darkcoin/blob/master/src/main.cpp#L1607Should get you started.
|
|
|
|
c_e_d
Member
Offline
Activity: 100
Merit: 10
|
|
December 07, 2014, 05:11:19 PM |
|
Saw this discussion by chance and thought to give you some input from discussions on another coin.
Main point is, how much is the hashrate changing?
If the changes are rather decent, everything from DS, KWG, DGW to DGW3 should do. DGW3 i.e. uses the last 24 blocks (can be easily modified) to recalculate the diff every block (like most modern algos do to react quicker). It has a minor 'one-off' bug, but nothing serious and easy to fix. Even the btc algo had a bug like this at one point.
If you see big jumps in hashrate, none of the actual algos are helping you here. There is a dev building a hashrate simulator to develop and test new diff algos for this problem.
If you need more info, you can PM me because I don't want to take over your thread and I think I saw some familiar names from the other thread here too.
|
|
|
|
Atomicat
Legendary
Offline
Activity: 952
Merit: 1002
|
|
December 07, 2014, 06:36:25 PM |
|
Well thanks to difficulties I'm finally in on the beginning of a launch, all set up and ready to fly. So, am I right in assuming that we're waiting on the new wallet before firing up the miners? (poor dev, let's all buy him a brain-pillow).
|
|
|
|
Atomicat
Legendary
Offline
Activity: 952
Merit: 1002
|
|
December 07, 2014, 06:46:40 PM |
|
Strange... I'm mining (or rather checking configs) with a 7950 and an R9-290 but it won't accept 8 for shaders multiplier. This is my batch, which works.
cgminer.exe --kryptohash -o 127.0.0.1:38912 -u xxx -p xxx --shaders 1792,2560 --shaders-mul 8,4
|
|
|
|
xinbinbin
|
|
December 07, 2014, 06:47:43 PM |
|
Why I gave the wallet with a password, and then the purse not open, display: error loading wallet, dat:wallet requires newer version of kryptohas, who can help me solve?
|
|
|
|
WORE
|
|
December 07, 2014, 06:51:27 PM |
|
Strange... I'm mining (or rather checking configs) with a 7950 and an R9-290 but it won't accept 8 for shaders multiplier. This is my batch, which works.
cgminer.exe --kryptohash -o 127.0.0.1:38912 -u xxx -p xxx --shaders 1792,2560 --shaders-mul 8,4
Swap your shaders-mul 4,8 Your going to get HW errors on the second card anyway until cgminer is worked on.
|
|
|
|
wr104 (OP)
|
|
December 07, 2014, 07:00:25 PM |
|
Well thanks to difficulties I'm finally in on the beginning of a launch, all set up and ready to fly. So, am I right in assuming that we're waiting on the new wallet before firing up the miners? (poor dev, let's all buy him a brain-pillow).
Yes, a new Wallet version 0.3.6 with yet another hard fork is coming later today. Please, hold your miners till this version is released. Saw this discussion by chance and thought to give you some input from discussions on another coin.
Main point is, how much is the hashrate changing?
If the changes are rather decent, everything from DS, KWG, DGW to DGW3 should do. DGW3 i.e. uses the last 24 blocks (can be easily modified) to recalculate the diff every block (like most modern algos do to react quicker). It has a minor 'one-off' bug, but nothing serious and easy to fix. Even the btc algo had a bug like this at one point.
If you see big jumps in hashrate, none of the actual algos are helping you here. There is a dev building a hashrate simulator to develop and test new diff algos for this problem.
If you need more info, you can PM me because I don't want to take over your thread and I think I saw some familiar names from the other thread here too.
Thanks for the info. But, I think I found why the PID was acting up. I wasn't averaging Block time using the correct set of TX times. Like what my teacher of Control Theory course in my University used to say about controlling systems using feedback loops .... If your sensors aren't reporting correctly, you won't be doing squat.
|
|
|
|
Atomicat
Legendary
Offline
Activity: 952
Merit: 1002
|
|
December 07, 2014, 07:04:33 PM |
|
Strange... I'm mining (or rather checking configs) with a 7950 and an R9-290 but it won't accept 8 for shaders multiplier. This is my batch, which works.
cgminer.exe --kryptohash -o 127.0.0.1:38912 -u xxx -p xxx --shaders 1792,2560 --shaders-mul 8,4
Swap your shaders-mul 4,8 Your going to get HW errors on the second card anyway until cgminer is worked on. Nope! 7950 works with mul 8, 290 with 4 and only 4. Kinda strange. Tried 'tween numbers like 2048 for shaders, crashed, will try changing worksize. No big, just interesting and something of note. Now I was mining earlier, both cards, was running fine except for a couple of hardware errors on the 290, then the driver gave out. Just to be perfectly clear, we're at the "Waiting for work from pool 0" stage, correct? Yep!
|
|
|
|
tacee
|
|
December 07, 2014, 07:09:53 PM |
|
|
|
|
|
tacee
|
|
December 07, 2014, 07:21:21 PM |
|
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
|
|
|
|
kondiomir
Legendary
Offline
Activity: 1568
Merit: 1000
Twitter @Acimirov
|
|
December 07, 2014, 07:44:13 PM |
|
@tacee - you are mining now?
|
|
|
|
Atomicat
Legendary
Offline
Activity: 952
Merit: 1002
|
|
December 07, 2014, 07: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?
|
|
|
|
wr104 (OP)
|
|
December 07, 2014, 08:00:14 PM |
|
shitty wallet,shitty algo,esp shitty miner!!!!!!!!
Thanks for the feedback. Those are exactly my thoughts ATM.
|
|
|
|
WORE
|
|
December 07, 2014, 08: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.
|
|
|
|
Riseman
|
|
December 07, 2014, 08: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?
|
|
|
|
tk808
Legendary
Offline
Activity: 1512
Merit: 1124
Invest in your knowledge
|
|
December 07, 2014, 08: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/
|
|
|
|
|