Hey guy,

It's been a while.  I'm debating the idea or re-launching the Kryptohash Coin.  What do you guys think?

However, keep in mind that re-launching KHC in practice means the Blockchain will restart from Genesis. Also, I would like take the opportunity to address some of the known issues that the coin had during it's original 18 months run and, make some improvements as well. These are:  

 a) No more PID algorithm to calculate the Network Difficulty: This Diff algo was the cause of all the Forks we had.  I would like to use the simplest Diff algo out there which is the one found in Bitcoin Core.  This algo does have some issues and a lot of detractors but, IMO it works fine for coins that have long re-target periods and most importantly, it meets the KISS principle (Keep It Simple Stupid).

 b) The Block time will be 6 minutes and the Difficulty re-target will be every 1200 blocks (~5 days).

 c) The total number of KHC to be mined will be 20,997,436.32 (or 20,997,436,320,000 kryptohash-toshis). Satoshi-wise, KHC will be 100 times less inflationary than Bitcoin Core.  Also, the Subsidy will end once the amount drops below 1 Cent.


 d) No Pre-mine, no ICO, no BS.  I want to coin to grow by acceptance, the same way the old BTC, LTC, etc did it.  

 e) No more restrictions to mine empty blocks (a.k.a. Selfish Mining): Miners always complained about the 'Waiting for Work' message when there were no Transactions in the Network and, it also caused cgminer to hang.

 f) No more mandatory fee per transaction. Let the market decide the fee amount.

 g) The PoW algorithm will continue to be KSHAKE320 and Signatures will continue to use Ed25519. They've proven to work great.

 h) The Block limit will be 10Mb (10 times the current limit found in Bitcoin core).
 
 i) I will continue working on developing the original idea that Kryptohash would handle multiple blockchains via Region codes.  I'll provide further details once I get the prototype running on the TestNet.


 

 

I'm able to build Linux executables just fine using Bash for Windows but, I can't seem to figure out how to build executables that can run on Windows.

I'm not sure what those errors above mean but, I had a lot of trouble running any script until I realized the issue was related to extra CR (or LF) characters added by Windows to all these files that I obtained using Git for Windows.  To solve this, I deleted the project and used Git on the Bash environment itself to obtain a fresh copy of the bitcoin 0.13 project.

I installed Bash for Windows 10 and I'm able to build bitcoind, bitcoin-cli and bitcoin-xt binaries that can only run on the same Bash for Windows environment.   But, I could not figure out how to build executables that could run on Windows.  

I followed the instructions on the below document that tells you how to build Windows executables via cross-compilation in Ubuntu but, after the build was completed I got no .exe files (at least I couldn't find them).  
https://github.com/kryptohash/bitcoin/blob/master/doc/build-windows.md

Has anybody been successful with this cross-compiling method?   By the way, I do not want to hijack this old thread full of great info. Let me know if I should create a new thread instead.

Thanks
wr104

The OP hasn't been updated in over a year.  

Has anybody figure out how to build Bitcoin 0.12.1 or the 0.13 RC?

Bad news. We just lost the last Exchange that was trading KHC.  

Seeing how well this coin works and its great potential, it is very hard for me to decide whether or not to continue with this project.  If we don't get another Exchange on board within the next few weeks, I'll have no choice but to shutdown the servers.

wr104

Mandatory Upgrade due to Network Rule change starting at block 160,000

Changes since version 0.6.2

- Network rule change: At block 160,000 the PID algorithm will begin using a revised formula to calculate the Network Difficulty in order to prevent rounding differences between the 64-bit Wallets and the 32-bit Wallets.
- Added checkpoint for block 150,000.
- Updated OpenSSL to version 1.0.1s for the Windows Wallet.


Download version 0.7.0 from Github:
https://github.com/kryptohash/kryptohash/releases

Hi shintosai,

You don't have to wait for the new wallet 0.7.0 to begin trading KHC.  Current version 0.6.2 works just fine.

However, once wallet 0.7.0 is released, you are going to need to upgrade because, one of the fixes in 0.7.0 is a network rule change that starts at as soon as block 160,000 gets mined in the next few weeks.

Also, EmpoEX is the only exchange that trades KHC at the moment. I'm trying to get other exchanges interested in KHC.

I'm still testing the fixes in the new Wallet version 0.7.0.   I expect it will be released in the next few days.

You can see these changes in GitHub.  Let me know if you have any questions.

I forgot to mention that because Kryptohash network doesn't allow blocks with no transactions, the so-called "selfish mining" that affects Bitcoin and others altcoins is not possible with KHC.

I've been trying to debug this cgminer-khc issue but, I cannot duplicate it anymore. 

Happy new year guys.  I'm back from Holiday and ready to continue working on the coin.

The new features that I've been working on have required lots of risky changes to the KHC protocol so, more developer testing is required before I can release a version with all these changes.  
But, for the mean time, I'm preparing a Wallet version 0.70 that will only contain important bug fixes.  I'm planning to release this version after block 150,000 gets mined in the next few weeks.

Also, since most of the problems with KHC have been related to the PID algorithm to calculate the difficulty re-target time every 100 blocks, I'm seriously considering getting rid of the PID algo altogether and switch to a more standard approach to calculate the diff.  Don't get me wrong, the PID algorithm was a pretty neat addition to the crypto-world but, in my opinion (and after a lot of pain debugging every possible corner case), the PID algo has only added unnecessary complexity with no apparent benefits to the KHC protocol.


Finally, about the cgminer getting stuck issue.  I began experienced the same problem after I reinstalled Windows on one of my miners so, I'm going to debug what's going on.  

I don't have that problem. What OS do you have? You're using the latest cgminer-khc version, right?

Have you guys tried opening a ticket with EmpoEx support? 

The message "Waiting for work from Pool 0" in cgminer-khc means there are no transactions in the network.  Unlike other cryptocoins, Kryptohash protocol doesn't waste miner's electricity by providing 'dummy' work.

BTW, I just came back from vacations so, I'll get the main webpage updated and continue working on the coin.

On October 6th 2015, block 125,000 was mined which ended the random subsidy.  

The total number of mined KHC between blocks 1 and 125,000 was: 12,495,845

I'm not going away 

doomed

~12,000,000 KHCs

Random rewards will stop at block 125,000 so, after that I will scan all the entire blockchain and provide the exact number.

Hi Bosco,

Sorry, I couldn't answer yesterday.

With the latest codebase 0.6.x, you are no longer required to build Boost with c++11 support.   So, you can use all the standard libraries in your Linux distribution.  See updated instructions here: https://github.com/kryptohash/kryptohash/blob/master/doc/build-unix.md

cd kryptohash
./autogen.sh
CPPFLAGS="-Ikeccak -Ikeccak/SnP -Ikeccak/KeccakF-1600" ./configure --enable-upnp-default --with-gui=qt5
make

No news is good news 

I'm working on a new feature for the Android Wallet that I hope it is going to help make KHC more popular.  But, I'm not giving out anymore details today.   

After that, I'm going to work on enhancing KHC to handle the multiple region codes that are available today as one big 'happy' multi-blockchain coin.  The goal here is to increase the Transaction Per Seconds (TPS) to match or exceed Paypal, VISA or Mastercard.  This is a lot of work so, don't expect this new feature to be available on the next release. 



Other than that, the coin has been very stable. Wallets work fine but, unfortunately there aren't too many people mining the coin anymore. 

For Kryptohash, the thread concurrency is the combination of --shaders and --shaders-mul parameters.

Try something like this:

 -w 128 --shaders 448 --shaders-mul 2

Then, increase the shaders-mul value until you find the max Kh/s

Also, try with -w 64  and see if you get better performance.