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

[a3860903]

cgminer still pool 0 slow/down?

[sologap]

wallet crash on windows and Linux once i hit setgenerate true 

[antonio8]

 Are stream processors the same as shaders on AMD cards?

Up and running finally on 280x and finding blocks.

Now just gotta get 750ti and 970 going (also 270x, having issues now).

[Truckfarmer]

Compiling the wallet on OS X & Linux, at ./configure I get an error:

checking whether byte ordering is bigendian... yes
configure: error: "Big Endian not supported"

antonio, can you post your kryptohash.conf for the 280x please?! thank you!!!

[wr104]

why cgminer still pool 0 slow/down?

That's what i'm getting still...

same here...

Go to the Debug console and type: getwork

What do you get?

+1



{
"data" : "010000000000000045169a200616cc763b3f9de957df29b906201a6ac585d6d0aa8fff11b62f05a 6a831b9f039000000a83b541f198ccc1a07e72c5619b1e8fa7473451ef4a120884f73c327086388 ca916fd37797896a172541480f4a010000000000000000000000000000ffff0026b640000000000 0000000000000000000",
"target" : "0000000000000000000000000000000000000000000000000000000000000000000000ffff00000 0"
}

Ok, now do the same but, with the kryptohash-cli.exe that is included in the daemon folder

From the Command Prompt type:  kryptohash-cli getwork



kryptohash-cli.exe its close it self after i click it

Don't click on it.  Open the Command Prompt, navigate to the folder where kryptohash-cli.exe is located and type:

kryptohash-cli getinfo
kryptohash-cli getwork

[antonio8]

Compiling the wallet on OS X & Linux, at ./configure I get an error:

checking whether byte ordering is bigendian... yes
configure: error: "Big Endian not supported"

antonio, can you post your kryptohash.conf for the 280x please?! thank you!!!

*Disclaimer*

My config file is not the safest way to solo mine. I solo mine from 3 computers into the same wallet.

Use this setup at your own risk. I would recommend to use the config in the OP.

rpcuser=YOURUSERNAMEHERE
rpcpassword=YOURPASSWORDHERE
rpcallowip=*
rpcport=38912
listen=1
daemon=1
server=1

[antonio8]

@ wr104

Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.

I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.

[wr104]

wallet crash on windows and Linux once i hit setgenerate true  

Don't use the setgenerate option. It won't work.

Mining using KSHAKE320 algo is waaaay too slow for CPUs.  The option is there only because Kryptohash code is based on Bitcoin 0.9.3.   It is in my ToDo list to clean up the code once we all believe we have a stable code base.

GPU mining is the way to go.  If you have a decent video card (AMD preferably), you need to use cgminer-khc to mine KHCs.

[bt_spectro]

cgminer still pool 0 slow/down?

I saw that error on cgminer when it could not rpc to kryptohashd. Check that RPC is enabled on kryptohashd (server=1) and that cgminer is reaching it on the correct port (default is 38912).

[Truckfarmer]

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

Ah! I'm so confused! I DO NOT HAVE A KRYPTOHASH.CONF ANYWHERE AFTER **FIRST** INSTALL. This conf is for the cgminer-khc, correct? Or is it for the wallet?

Do I need to make one? Where do I put it? Where should it be if I already have it?

Right now I have a PiMP/cgminer-khc pointed to a conf I made here: /opt/ifmi/cgminer.khc.conf

{
  "pools": [
    {
      "url": "http://127.0.0.1:38912",
      "user": "truckfarmer",
      "pass": "x",
      "profile": "khc"
    }
  ],
  "profiles": [
    {
      "name": "khc",
      "algorithm": "kryptohash",

[antonio8]

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

Ah! I'm so confused! I DO NOT HAVE A KRYPTOHASH.CONF ANYWHERE AFTER **FIRST** INSTALL. This conf is for the cgminer-khc, correct? Or is it for the wallet?

Do I need to make one? Where do I put it? Where should it be if I already have it?

Right now I have a PiMP/cgminer-khc pointed here: /opt/ifmi/cgminer.khc.conf

{
  "pools": [
    {
      "url": "http://127.0.0.1:38912",
      "user": "truckfarmer",
      "pass": "x",
      "profile": "khc"
    }
  ],
  "profiles": [
    {
      "name": "khc",
      "algorithm": "kryptohash",

Yes you have to make your config file and place it in the KryptoHash appdata folder.

[sologap]

WTB 100,000 , any offers ?

[jasemoney]

im not having luck on my 7950.  Rejects.. Ive dumbed down the shader-mul from 8 to 4 and still getting rejects. 

[xinbinbin]

A computer can only use a graphics card mining? I inserted the 6 card is only one card!!

[wr104]

@ wr104

Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.

I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.

The two most important parameters for the cgminer-khc are the 'shaders' and the 'shaders_mul'.  The former is straightforward.  If you GPU has 2048 Stream Processors then, you need to use '--shaders 2048'.  The latter is a bit more complicated to as it depends on the GPU architecture and how much memory you have in your video card. Unfortunately, the best value for 'shaders_mul' must be found through trial and error.  

That said, with all the video cards that I tested, I found that the best value for 'shaders_mul' was always 8.  But, your mileage may vary, if you know what I'm saying.

When I developed the kshake320 opencl kernel and I was testing it using CodeXL, I did find somewhere a good explanation on how to best determine the number of threads per Stream Processor.  I'll try to find it.

[jasemoney]

im not having luck on my 7950.  Rejects.. Ive dumbed down the shader-mul from 8 to 4 and still getting rejects.  

@ wr104

Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.

I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.

The two most important parameters for the cgminer-khc are the 'shaders' and the 'shaders_mul'.  The former is straightforward.  If you GPU has 2048 Stream Processors then, you need to use '--shaders 2048'.  The latter is a bit more complicated to as it depends on the GPU architecture and how much memory you have in your video card. Unfortunately, the best value for 'shaders_mul' must be found through trial and error.  

That said, with all the video cards that I tested, I found that the best value for 'shaders_mul' was always 8.  But, your mileage may vary, if you know what I'm saying.

When I developed the kshake320 opencl kernel and I was testing it using CodeXL, I did find somewhere a good explanation on how to best determine the number of threads per Stream Processor.  I'll try to find it.

just solved one on -mul 10  so its anybodys guess. look forward to reading the explanation if you find it


*edit, awarded 6, 4 rejects. 3 awarded didnt show in wallet. 3 blocks solved..

[antonio8]

@ wr104

Can you tell me how I can find out to determine my threads per core? I tried to google but can't find the correct answer.

I might have got lucky on my 280x. It is up and running at 135 kh/s and finding blocks decently but I can't get my 270x going. I keep getting HW errors. From what I can determine I have 1280 shaders on the 270x.

The two most important parameters for the cgminer-khc are the 'shaders' and the 'shaders_mul'.  The former is straightforward.  If you GPU has 2048 Stream Processors then, you need to use '--shaders 2048'.  The latter is a bit more complicated to as it depends on the GPU architecture and how much memory you have in your video card. Unfortunately, the best value for 'shaders_mul' must be found through trial and error. 

That said, with all the video cards that I tested, I found that the best value for 'shaders_mul' was always 8.  But, your mileage may vary, if you know what I'm saying.

When I developed the kshake320 opencl kernel and I was testing it using CodeXL, I did find somewhere a good explanation on how to best determine the number of threads per Stream Processor.  I'll try to find it.

Thanks for the reply.

I am also guessing that cgminer shows 2 blocks for every 1 block found because of the block reward plus the random coins in there? Cgminer shows 30 blocks and the wallet 15 blocks. If I am correct you might want to add something in the OP so you don't get tons of questions about that. I seen someone has already questioned it.

EDIT: I like this coin. thanks

[wisnon]

Sell some KHC, if you are interested,
Please make an offer, PM me, thank you!

[xinbinbin]

Sell some KHC, if you are interested,
Please make an offer, PM me, thank you!

1000 Cong sell?

[wr104]

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

Ah! I'm so confused! I DO NOT HAVE A KRYPTOHASH.CONF ANYWHERE AFTER **FIRST** INSTALL. This conf is for the cgminer-khc, correct? Or is it for the wallet?

Do I need to make one? Where do I put it? Where should it be if I already have it?

Right now I have a PiMP/cgminer-khc pointed to a conf I made here: /opt/ifmi/cgminer.khc.conf

{
  "pools": [
    {
      "url": "http://127.0.0.1:38912",
      "user": "truckfarmer",
      "pass": "x",
      "profile": "khc"
    }
  ],
  "profiles": [
    {
      "name": "khc",
      "algorithm": "kryptohash",

Is this Windows or Linux?
A "sample" kryptohash.conf file should be included with the Windows installer.  If you can't find one, create your own kryptohash.conf file using a text editor, add the below parameters and save it to the roaming folder  C:\Users\{Your_User}\AppData\Roaming\Kryptohash\  or to the folder you specified when you executed Kryptohash-Qt.exe for the first time.

kryptohash.conf

region=0
addnode=104.131.54.248
addnode=178.62.96.79
server=1
rpcuser={Your_RPC_Username}
rpcpassword={Your_RPC_Secret_Password}
rpcconnect=127.0.0.1         <-- Note that if you are running cgminer-khc on a different computer, you need to specify its IP address here.
keypool=100
paytxfee=0.0