Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 73. (Read 149454 times)

Is this average?

I've got ~100kh/s (~20kh/s average) with HD7970
And GPU usage 0% (in MSI Afterburner)

What GPU do you have?

I have one R9 290x and one HD7970 running solo mining with

R9 290x (~180Kh/s)

 cgminer --kryptohash -o 127.0.0.1:38912 -u username -p password --shaders 2816 --shaders-mul 8

HD7970 (~140Kh/s)

 cgminer --kryptohash -o 127.0.0.1:38912 -u username -p password --shaders 2048 --shaders-mul 8

I have the same problem.

Edit: It seems to be working but I'm getting 30Kh/s per 7950.

Need to use cgminer.  CPU mining not good idea.

dev, a few graphics unsuccessful solo, but also what parameters it?

countdown pls

looks interesting, watching this !

Looks cool. I'll sesetup explorer, dice and faucet shshortly.

wow something new here... i will try

Looks interesting.  14-20 million coins mined over 260 days if my calculations are semi accurate.

The new specs are interesting as well.  I would be interested in hearing more about the Region Codes...

New algo, nice Will take a look

https://twitter.com/ThisWeeksCoin/status/539947679652929536

What is Kryptohash?
Kryptohash is a new cryptocurrency based on the Bitcoin protocol but, with a few significant changes.

Main features

320-bits long hash: Bitcoin and most alternative cryptocurrencies use 256-bits long hashes. With Kryptohash, all the main hashes are 320-bits long. The hashing algorithm is the Keccak-F 1600 Sponge Function that has been selected by the NIST to be the new SHA-3 standard. The Keccak Rate selected for Kryptohash is 960 and the Keccak Capacity is 640. These parameters provides significantly higher collision and preimage resistance than the old SHA-256 algorithm.


KSHAKE320: A brand new Proof-Of-Work algorithm (PoW) based on the Keccak but in a mode called Extendable-Output (a.k.a. SHAKE). SHAKE's variable output makes it ideal for a Proof-Of-Work algorithm, as it can easily be configured to require large amount of memory which increases the computing cost to those attempting to perform large-scale ASIC attacks.  In the case of the KSHAKE320 used by Kryptohash, each hash calculation requires 64Kb of RAM and it can be easily enhanced in the future to require 128Kb, 256Kb, 512Kb, 1Mb, etc.


Ed25519 Signatures: This is an Elliptic-Curve Cryptographic Algorithm that offers faster signature verification and better protection against side channel attacks than the ECDSA.


Difficulty: The block difficulty is adjusted every 100 blocks using a PID algorithm. The block time is 180 seconds.


64-bits Time Stamps: In order to avoid the upcoming Unix Time apocalypse (Jan 2038), Kryptohash implements *today* time stamps fields with 64-bits in the blockchain.


Region code: Kryptohash protocol includes a Region code field. The Region code is intended to solve the known scalability issues of the Bitcoin network. Each Region contains its own Blockchain and separate RPC/P2P port numbers to handle network traffic congestion. Having multiple regions allows for higher TPS (Transactions per Second) on the Kryptohash Network.  As of June 2016, only Region #0 exists. Other Region codes will come online as needed.    


Block Reward & Fee structure: In order to protect the Kryptohash network today and in the future against the 50%+ hash power attacks, the protocol includes a reward & fee structure that provides financial incentives to individual honest miners which helps reduce the likelihood of the Economic dilemma known as "The Tragedy of the Commons". The structure consists in the following:

 1) Every Kryptohash Coin (KHC) transaction carries a fixed fee of 0.2% that is paid to the miner who solves the block. Minimum fee is 10 Kryptoha-toshis or 0.00010 KHC.

 2) Just like with Bitcoin v0.9.4, there is a fee to discourage "dust" SPAM and a fee for transactions with high number of inputs and outputs. Finally, additional "voluntary" fees can be specified using the "paytxfee" parameter inside the kryptohash.conf file to increase the chance of getting your transaction included in generated blocks.

 3) Block reward (or subsidy) is paid to miners using the following schema:

• Blocks: 0 to 99 -> A fixed subsidy of 50 KHCs.
• Blocks: 100 to 999 -> A fixed subsidy of 50 KHCs plus a random subsidy of 0 to 399 KHCs.
• Blocks: 1,000 to 9,999 -> A fixed subsidy of 50 KHCs plus a random subsidy of 0 to 199 KHCs.
• Blocks: 10,000 to 99,999 -> A fixed subsidy of 50 KHCs plus a random subsidy of 0 to 99 KHCs.
• Blocks: 100,000 to 124,999 -> A fixed subsidy of 50 KHCs plus a random subsidy of 0 to 49 KHCs.
• Blocks: 125,000 to 249,999 -> A fixed subsidy of 50 KHCs.
• Blocks: 250,000+ -> A fixed subsidy of 25 KHCs.

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


Low inflation: Even though the KHC reward per block is never going to be zero, Kryptohash Coin is 1,000 times less inflationary than Bitcoin. Here is why:

• 1 BTC = 100,000,000 satoshis
• 1 KHC =      100,000 kryptoha-toshis

 Current BTC reward per block is 25 BTC or 2,500,000,000 satoshis. On the other hand, KHC reward per block (after block 250,000 is mined) will be 25 KHC or 2,500,000 kryptoha-toshis.  

 On April 2015, Bitcoin reached a milestone. Two third of all 21 Millions BTCs that will ever exist have been mined. This amounts to more than 1,400,000,000,000,000 satoshis in circulation.  For the Kryptohash Coin, it is going to take almost 3,000 years to reach this same amount of satoshis.



Low pre-mine: Only 100,000 KHCs have been pre-mined in Block #1. These KHCs will be used to kick start the blockchain and to pay for bounties, development and support.


Parameters (Region #0):

• P2P port: 39168
• RPC port: 38912
• addnode: 104.131.54.248
• addnode: 178.62.96.79

Download Kryptohash Core from GitHub

Binaries for Windows/Linux/OSX: https://github.com/kryptohash/kryptohash/releases
 
Kryptohash at GitHub: https://github.com/kryptohash/kryptohash



Download cgminer-khc from GitHub

Binaries for Windows/Linux: https://github.com/kryptohash/cgminer-khc/releases



Download Kryptohash Mobile App for Android

https://play.google.com/store/apps/details?id=org.kryptohash.wallet

https://github.com/kryptohash/kryptohash-android/releases



Kryptohash Block Chain Explorer

http://www.kryptohash.org/khcbc.php



How to mine KHC

GPU mining using cgminer-khc v3.7.8 is currently the only viable option.


How to setup KHC for Solo Mining:

Solo mining using cgminer-khc

Edit the kryptohash.conf file and ensure the following parameters are uncommented:

• server=1
• rpcuser={RPC_username}
• rpcpassword={RPC_password}
• rpcport=38912
• rpcconnect=127.0.0.1

Then, execute cgminer with the following parameters:

    cgminer --kryptohash -o http://127.0.0.1:38912 -u {RPC_username} -p {RPC_password} --shaders {xxxx} --shaders-mul {yy}

Where:
   {RPC_username} : The user name you used for the 'rpcuser' parameter in kryptohash.conf
   {RPC_password} : The password you used for the 'rpcpassword' parameter in kryptohash.conf
                {xxxx} : Number of Shaders in your GPU (Default 256 )
                   {yy} : Number of Threads per Shader (Default 8 )

Note:
With AMD GCN architecture GPUs, running the AMD 14.12 Omega drivers and later, you can use an option called --cl-opt-disable.  For some reason, high end GCN architecture GPUs can execute the KSHAKE320 OpenCL Kernel much faster when you disable OpenCL optimizations.  However, if you have older AMD GPUs (HD 5xxx/6xxx series) and nVidia GPUs, do not use this option as the hashing performance would likely be reduced.

Important: Using the --cl-opt-disable can make your GPU run very hot.  Be sure you monitor the temperature and adjust the Intensity accordingly.




Enabling Secure mode for Solo mining (cgminer-khc v3.7.8 and later only):

Note: This should only be used if cgminer-khc runs on a different computer than the Wallet.

1. Follow the steps above to enable Solo mining

2. Download OpenSSL for Windows ( https://www.openssl.org/related/binaries.html )

3. Use openSSL command lines below to create a Self-Signed SSL Certificate for the Computer running the Wallet.

  openssl genrsa -out server.pem 2048
  openssl req -new -x509 -nodes -sha256 -days 3650 -key server.pem > server.cert

  Note: When asked to provide the Common Name, you could type the IP address of the computer running the Wallet, if your IP address is static. If your IP address is not static, specify the Computer Host name instead.

4. Copy the server.pem and server.cert to your kryptohash/region0 folder

5. Enable SSL/TLS in the Wallet

  rpcssl=1
  rpcsslciphers=TLSv1.2+HIGH:!SSLv2:!EXP:!aNULL:!eNULL:!AH:!3DES:@STRENGTH
  rpcsslcertificatechainfile=server.cert
  rpcsslprivatekeyfile=server.pem

6. Specify the IP address of the Computer where cgminer-khc will connect from.

  rpcallowip=192.168.1.1

7. Ensure the line below is commented out:

  #rpcconnect=127.0.0.1

8. Copy the server.cert file to the computer where cgminer-khc will run. Place the cert file inside the cgminer-khc-3.7.8 folder

9. Rename the server.cert file to cacert.pem or, append the content of server.cert at the end of the existing cacert.pem file.

10. Execute cgminer-khc using:

    cgminer --kryptohash --secure -o https://:38912 -u {RPC_username} -p {RPC_password} --shaders {xxxx} --shaders-mul {yy}



Exchanges


Vote to get KHC added to these Exchanges:

BTER:  https://bter.com/voting/
C-CEX: https://c-cex.com/?id=vote

If you have Twitter account, ask Bittrex to add KHC.  https://twitter.com/bittrexexchange


To Do List

• Wallet for MAC
• Wallet for Android
• Wallet for iPhone
• A new logo?

Visit Kryptohash Website: http://www.kryptohash.org

Follow us on Twitter: https://twitter.com/kryptohash

My personal Twitter is: https://twitter.com/Wolf_Rayet_104