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

cyptohunter

full member

Activity: 126

Merit: 100

Quote from: wr104 on December 13, 2014, 06:49:34 PM

NEW Wallet v0.3.9 Available

Fixes since v0.3.8

Encrypting Wallet caused the app to fail to load, displaying the following message: "Error loading wallet.dat: Wallet requires newer version of Kryptohash".
Stopping the Wallet app and then restarting it after a re-target resulted in a wrong calculation of the Diff value and the Wallet app stopped synchronizing with the network.

Download from GitHub
https://github.com/kryptohash/kryptohash/releases/tag/v0.3.9

Is v0.3.9 madatory update?
when I update from v0.3.8 to v0.3.9 ,I lost 14 blocks which I found before,why? Huh

?

kingscrown

hero member

Activity: 672

Merit: 500

http://fuk.io - check it out!

interesting i will wait for exchanges

hero18688

sr. member

Activity: 392

Merit: 250

LOL.The diff is 6 times than I mine it a week ago.

jjjordan

sr. member

Activity: 271

Merit: 251

Anybody mining with nvidia cards? GTX 970 maybe?....

Quote from: jjjordan on December 10, 2014, 11:51:57 AM

Oh, I knida missed if this miner is for AMD only or I can use it with GTX 970?

wr104

sr. member

Activity: 329

Merit: 250

NEW Wallet v0.3.9 Available

Fixes since v0.3.8

Encrypting Wallet caused the app to fail to load, displaying the following message: "Error loading wallet.dat: Wallet requires newer version of Kryptohash".
Stopping the Wallet app and then restarting it after a re-target resulted in a wrong calculation of the Diff value and the Wallet app stopped synchronizing with the network.

Download from GitHub
https://github.com/kryptohash/kryptohash/releases/tag/v0.3.9

WORE

sr. member

Activity: 350

Merit: 250

Quote from: Arux on December 13, 2014, 04:42:58 PM

my wallet stuck at block 8899 Huh

at the same time, nonce-pool is at block 8981.

What should I do?

[edit]solve: i deleted blk00000.dat, and a synchronization later, i'm at the same block as nonce-pool.

Is a bug the dev previously noted on this thread. The wallet is calculating the wrong diff and this lead to orphaned blocks logged. Fix is to run wallet with the --reindex command until new release.

Arux

hero member

Activity: 500

Merit: 500

my wallet stuck at block 8899 Huh

at the same time, nonce-pool is at block 8981.

What should I do?

[edit]solve: i deleted blk00000.dat, and a synchronization later, i'm at the same block as nonce-pool.

Arux

hero member

Activity: 500

Merit: 500

Quote from: martin23 on December 13, 2014, 09:29:16 AM

Hi. I´m solo mining and my minner says "Found block" but Accepted an Rejected is zero. And there is no income in my wallet. Is this correct?

when you find a block it's look like this:

antonio8

legendary

Activity: 1400

Merit: 1000

Quote from: martin23 on December 13, 2014, 11:34:58 AM

Quote from: antonio8 on December 13, 2014, 10:08:03 AM

Quote from: martin23 on December 13, 2014, 09:29:16 AM

Hi. I´m solo mining and my minner says "Found block" but Accepted an Rejected is zero. And there is no income in my wallet. Is this correct?

That is a known issue with the miner. If you look at your best share (which might be incorrect also) it show 40.

The current difficulty is over 100 (or at least the last time I checked).

It might take you a while to find a block solo mining now.

Thank You for explanation

Anytime.

But you might want to look at possibly joining the pool in the OP with your hash rate.

martin23

newbie

Activity: 51

Merit: 0

Quote from: antonio8 on December 13, 2014, 10:08:03 AM

Quote from: martin23 on December 13, 2014, 09:29:16 AM

Hi. I´m solo mining and my minner says "Found block" but Accepted an Rejected is zero. And there is no income in my wallet. Is this correct?

That is a known issue with the miner. If you look at your best share (which might be incorrect also) it show 40.

The current difficulty is over 100 (or at least the last time I checked).

It might take you a while to find a block solo mining now.

Thank You for explanation

wr104

sr. member

Activity: 329

Merit: 250

Guys, I'm working on a new version for the Wallet to address few issues I've seen so far.

The most notorious bug is one that is only seen when the app is closed and then later restarted after a new retarget has occurred. In this case, the wallet will calculate the wrong Diff when it reaches the retarget and will get stuck there logging a bunch of errors regarding Orphan blocks.

To workaround this bug (until a new Wallet version is available), you must start the Wallet app with the --reindex parameter.

antonio8

legendary

Activity: 1400

Merit: 1000

Quote from: martin23 on December 13, 2014, 09:29:16 AM

Hi. I´m solo mining and my minner says "Found block" but Accepted an Rejected is zero. And there is no income in my wallet. Is this correct?

That is a known issue with the miner. If you look at your best share (which might be incorrect also) it show 40.

The current difficulty is over 100 (or at least the last time I checked).

It might take you a while to find a block solo mining now.

martin23

newbie

Activity: 51

Merit: 0

Hi. I´m solo mining and my minner says "Found block" but Accepted an Rejected is zero. And there is no income in my wallet. Is this correct?

https://dl.dropboxusercontent.com/u/678926/screen-khc.png

WORE

sr. member

Activity: 350

Merit: 250

Quote from: bt_spectro on December 12, 2014, 10:06:40 PM

Quote from: cyptohunter on December 12, 2014, 08:25:01 PM

why the diff and net hashrate jump high and low ,now and then?? Huh

I don't think we can control hashrate but the dev selected a PID algorithm (http://en.wikipedia.org/wiki/PID_controller) to control the difficulty and it seems to be working as designed. I studied control systems theory in college and i'm intrigued by how this could be applied to control difficulty on a cryptocoin.

Remember from the OP, setpoint is a block every 180 seconds (or 100 blocks every 5 hrs). As far as I can tell the PID is right on getting there.

Yes, but network conditions can change quite rapidly, and only within a few blocks, 100 blocks will be a long trip if say you have a pool go down that was a contributor of %30+ to over all network hash rate. Might have been better to do 100 block sensor survey but block diff to change every 50 blocks.

bt_spectro

newbie

Activity: 31

Merit: 0

Quote from: cyptohunter on December 12, 2014, 08:25:01 PM

why the diff and net hashrate jump high and low ,now and then?? Huh

I don't think we can control hashrate but the dev selected a PID algorithm (http://en.wikipedia.org/wiki/PID_controller) to control the difficulty and it seems to be working as designed. I studied control systems theory in college and i'm intrigued by how this could be applied to control difficulty on a cryptocoin.

Remember from the OP, setpoint is a block every 180 seconds (or 100 blocks every 5 hrs). As far as I can tell the PID is right on getting there.

cyptohunter

full member

Activity: 126

Merit: 100