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

[antonio8]

Guys, at the current Diff, it is going to take days to reach Block 5200 where it is expected to retarget to a lower value.

I'm going to have to create a new wallet version with a hard fork at block 5098 and get a lower retarget value for a brand new block 5100.

You are doing a fantastic job at making adjustments. Thanks.

Just curious if cgminer is causing issues also with read outs. Wallet shows difficulty of 902.1813 while cgminer still shows over 1.86k.

[wr104]

Since I also have big dramas at the office, the ETA for next wallet is going to be, 12 hours from now (or Dec 6th, 2:00AM  GMT)

I'm going to try to get home early so, I can begin working on the hard fork at block 5098 and a new retarget value for block 5100

Thanks for your patience.

[wr104]

Guys, at the current Diff, it is going to take days to reach Block 5200 where it is expected to retarget to a lower value.

I'm going to have to create a new wallet version with a hard fork at block 5098 and get a lower retarget value for a brand new block 5100.

You are doing a fantastic job at making adjustments. Thanks.

Just curious if cgminer is causing issues also with read outs. Wallet shows difficulty of 902.1813 while cgminer still shows over 1.86k.

Well, not as fantastic as I was expecting.  3 Wallet versions in 3 days isn't what I was hoping to see but, I'm learning a very good deal about how these coins operate in the real world and not to trust too much the simulations I was performing on my Testnet in the last few months.

cgminer-khc does have few serious problems.  But this Diff value problem you mention seems to be just a display issue, perhaps a mismatch in the algorithm to estimate the Network Diff.  I'll fix it as soon as I fix the extra GPU mining problem which is at the top of my to do list.

[cashclash]

Compiled cgminer-khc from git repo but when i fire it up i get

No suitable long-poll found for http://127.0.0.1:38912




edit: same happens if i use the https://github.com/kryptohash/cgminer-khc/releases

[WORE]

Compiled cgminer-khc from git repo but when i fire it up i get

No suitable long-poll found for http://127.0.0.1:38912




edit: same happens if i use the https://github.com/kryptohash/cgminer-khc/releases

Yes, whenever you mine solo there is no long-poll server found, this is usually only found on pools.  The reason you are awaiting work on pool 0 is found in previous posts.

[cashclash]

thanks WORE, was just making sure im set and ready 

[kondiomir]

How to sync guys ? I'm with last wallet 0.3.4 and loaded blockchain again but it is stuk on block 5104.

PLS Advise ?

[cashclash]

we all are (:

[kondiomir]

The last wallet cannot fix this ??
OMG .. WTF !

[WORE]

The last wallet cannot fix this ??
OMG .. WTF !

The last wallet did not address the ultra high difficulty on new block generation, the next 100 blocks would have been brutal to solve without a pool and long-pole server to distribute work for new block generation so he is hard forking it at block 5098 to address this.  Mind you this would not have happened if everyone updated their wallet to 0.3.3 when asked to do so, and because of that he had to make the wallet deny connections to obsolete versions of the wallet, so if people don't keep up on new developments and actually read the thread, you won't be able to sync your wallet.  On the plus side those that fail to keep up and read will not be able to screw up the blockchain for everyone else...

[kondiomir]

I see.. then.. what ? This is the end for this coin ? 

[antonio8]

I see.. then.. what ? This is the end for this coin ? 

Not the end of the coin just the evolution of it.

I like that the dev is staying on top off things. I hope this coin has success for his efforts.

On a side note,  since the coin is going to be hard forked or rolled back does it make any sense to mine it right now until the wallet is released?

I am not sure how that works.

[wr104]

I'm back home and working on the Fork.   Expect an update within the next 2 - 3 hours.

[z38630610]

I'm back home and working on the Fork.   Expect an update within the next 2 - 3 hours.

we waiting

[wr104]

Still working on it.

[z38630610]

Still working on it.

now wallet 5015 block ? its right ? not sync behind 18 hours ?

[WORE]

Still working on it.

now wallet 5015 block ? its right ? not sync behind 18 hours ?

Nothing can be determined is right until the next wallet release, it is stated in the FIRST POST of this thread that the hard fork will occur at 5098 and the more you pester him with questions, the longer it is going to take.  But that makes it OUR time you are burning...

[z38630610]

Still working on it.

now wallet 5015 block ? its right ? not sync behind 18 hours ?

Nothing can be determined is right until the next wallet release, it is stated in the FIRST POST of this thread that the hard fork will occur at 5098 and the more you pester him with questions, the longer it is going to take.  But that makes it OUR time you are burning...

oh, we wait next wallet release !now waiting

[wr104]

Patience. We are almost there.  I need to mine few transactions to ensure the new fork is longest chain.  I don't want to risk yet another fork.



BTW, the diff at 5100 is now 16.7695

[WORE]

Patience. We are almost there.  I need to mine few transactions to ensure the new fork is longest chain.  I don't want to risk yet another fork.



BTW, the diff at 5100 is now 16.7695

Take your time man, get it right, I know where you are in terms of coding...