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

[wr104]

Quick update.  I'm working on a new Wallet version 0.3.3 that will allow the PID algo to adjust the Difficulty a bit faster. 

Please consider to fix this :

genesis.cpp:15: error: function definition does not declare parameters
genesis.cpp:20: error: function definition does not declare parameters
genesis.cpp:25: error: function definition does not declare parameters
genesis.cpp: In function ‘const Genesis::MapGenesis& Genesis::Genesis()’:
genesis.cpp:32: error: ‘mapGenesisTestnet’ was not declared in this scope
genesis.cpp:34: error: ‘mapGenesis’ was not declared in this scope
genesis.cpp:36: error: ‘mapGenesisRegtest’ was not declared in this scope

for osx and linux platform

Compiler doesn't support C++11 ?

[xinbinbin]

Where to download 0.3.3?

[karimdr2]

Quick update.  I'm working on a new Wallet version 0.3.3 that will allow the PID algo to adjust the Difficulty a bit faster. 

Please consider to fix this :

genesis.cpp:15: error: function definition does not declare parameters
genesis.cpp:20: error: function definition does not declare parameters
genesis.cpp:25: error: function definition does not declare parameters
genesis.cpp: In function ‘const Genesis::MapGenesis& Genesis::Genesis()’:
genesis.cpp:32: error: ‘mapGenesisTestnet’ was not declared in this scope
genesis.cpp:34: error: ‘mapGenesis’ was not declared in this scope
genesis.cpp:36: error: ‘mapGenesisRegtest’ was not declared in this scope

for osx and linux platform

Compiler doesn't support C++11 ?

I got error: "Big Endian not supported" with C++11 flag on osx.
I'll try again

[xinbinbin]

Quick update.  I'm working on a new Wallet version 0.3.3 that will allow the PID algo to adjust the Difficulty a bit faster. 

Please consider to fix this :

genesis.cpp:15: error: function definition does not declare parameters
genesis.cpp:20: error: function definition does not declare parameters
genesis.cpp:25: error: function definition does not declare parameters
genesis.cpp: In function ‘const Genesis::MapGenesis& Genesis::Genesis()’:
genesis.cpp:32: error: ‘mapGenesisTestnet’ was not declared in this scope
genesis.cpp:34: error: ‘mapGenesis’ was not declared in this scope
genesis.cpp:36: error: ‘mapGenesisRegtest’ was not declared in this scope

for osx and linux platform

Compiler doesn't support C++11 ?

Development can provide a new purse the download link?

[wr104]

Update.  I'm compiling the new Wallet 0.3.3 but, this new version will require everybody to be running it when the blockchain hits the 5000 blocks

I've stopped generating TX every 10 seconds in order to give time for miners to upgrade the new Wallet.

ETA for the new Wallet v0.3.3 is 3 hours from now.  Around 4:00AM GMT    

Thanks for your patience.

[mrmanager]

Update.  I'm compiling the new Wallet 0.3.3 but, this new version will require everybody to be running it when the blockchain hits the 5000 blocks

I've stopped generating TX every 10 seconds in order to give time for miners to upgrade the new Wallet.

ETA for the new Wallet v0.3.3 is 3 hours from now.  Around 4:00AM GMT    

Thanks for your patience.

Sounds good. The transaction fees seem quite high. Is there reasoning behind this?

Also, every time I encrypt a wallet I need to use the --salvagewallet flag. The qt never seems to quit cleanly. This is the 3rd time it's happened.

[jasemoney]

sorry wont be able to update for 10 hrs. but im just one 7950..

[xinbinbin]

Block card in 3474, 2 hours, the coin to die?

[z38630610]

0.3.3 where ?dev

[wr104]

Wallet 0.3.3 has been released

https://github.com/kryptohash/kryptohash/releases/tag/v0.3.3

Everybody needs to upgrade their Wallet to version 0.3.3 before the block 5000 mark

[bt_spectro]

Block card in 3474, 2 hours, the coin to die?

There were no transactions, the dev stopped a process which was generating a new 0.02 transaction every 10 seconds. All you needed to get more blocks mined was to send some coins between wallets

[jasemoney]

wait whats this transaction thing, i thought its new POW algo, not new pow style is there a velocity associated with transactions or something?

[WORE]

Wallet 0.3.3 has been released

https://github.com/kryptohash/kryptohash/releases/tag/v0.3.3

Everybody needs to upgrade their Wallet to version 0.3.3 before the block 5000 mark

On the HW errors for multi GPU rigs, it produces HW errors even if you use the "device" : "0", and "1" building separate conf files and running two sessions.  Maybe sph-sgminer? 

[antonio8]

With the new wallet 0.3.3 I get a lot of gpu throttling down due to the "Waiting for work from pool 0".

I did not notice that before.

And same as everyone else who has replied still get HW errors on any other cards that I try and mine. Even tried putting the wallet on another computer and solo into that with a different port and no go.

[ocminer]

Test post from mobile.

Works

[hero18688]

3*270x+3*280x solo for half an hour without luck,no block found.I noticed the cards stop and resume mining quite often. Is 3 minute block time too much?

[xinbinbin]

Do you have any plan to develop this coin?

[ocminer]

i'm working on a python module for this coin but i'm having difficulties getting the hashing itself done, it is no longer doublesha rather its single keccak when I look at the hashblock.cpp - if someone else has got it running or want to cooperate, feel free to contact me.

[jasemoney]

With the new wallet 0.3.3 I get a lot of gpu throttling down due to the "Waiting for work from pool 0".

I did not notice that before.

And same as everyone else who has replied still get HW errors on any other cards that I try and mine. Even tried putting the wallet on another computer and solo into that with a different port and no go.

I had a few slowdown errors with the previous wallet.

[bt_spectro]

With the new wallet 0.3.3 I get a lot of gpu throttling down due to the "Waiting for work from pool 0".

I did not notice that before.

And same as everyone else who has replied still get HW errors on any other cards that I try and mine. Even tried putting the wallet on another computer and solo into that with a different port and no go.

dev said something about this wallet not generating "dummy work" like bitcoin does. I think if there are no new transactions to put in a block, the whole network goes idle. Right now he seems to be generating a 0.0011 transfer every 1 minute and blocks are getting resolved in around 30 seconds, so miners go idle for the rest of the minute.

I guess setting a cron job sending a small transaction back and forth between 2 wallets will keep miners busy.