Current version of KSHAKE320 algorithm requires 64Kb per hash. I could change it to require 128Kb+ on a dime.
But, what limits the speed of the algorithm is not the amount of RAM but, the speed you can store/read data to/from RAM. If in the future, new RAM technology allows for very fast memory that is also affordable then, the KSHAKE320 algorithm may no longer offer an advantage over regular hashing algorithms.
Topic: [ANN] Kryptohash | Brand new PoW algo | 320bit hash | ed25519 | PID algo for dif - page 26. (Read 149446 times)
January 06, 2015, 08:49:46 PM
January 06, 2015, 08:44:42 PM
I like the name of this coin 
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. 
Nothing is ASIC resistant - if it gets big enough - ASICS will come
Thank You,
Viz.
I am looking forward to that day when ASICs come.
Pretty sure dev is too, I'm sure he would rather enjoy being tested when he just releases a mandatory wallet update with the algo modified.
January 06, 2015, 08:39:38 PM
I like the name of this coin
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. Nothing is ASIC resistant - if it gets big enough - ASICS will come
Thank You,
Viz.
I am looking forward to that day when ASICs come.
Pretty sure dev is too, I'm sure he would rather enjoy being tested when he just releases a mandatory wallet update with the algo modified.
You're right, that's the only way to do it.
Regards,
Viz.
January 06, 2015, 08:20:52 PM
I like the name of this coin
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. Nothing is ASIC resistant - if it gets big enough - ASICS will come
Thank You,
Viz.
I am looking forward to that day when ASICs come.
Pretty sure dev is too, I'm sure he would rather enjoy being tested when he just releases a mandatory wallet update with the algo modified.
January 06, 2015, 07:48:25 PM
I like the name of this coin
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. Nothing is ASIC resistant - if it gets big enough - ASICS will come
Thank You,
Viz.
I am looking forward to that day when ASICs come.
January 06, 2015, 07:41:22 PM
Help me please I have GTX 650 Ti video and Intel Core i5 4570 cpu. Is It possible to mine this currency? Will it be profitably?
I have GTX 650 Ti video and Intel Core i5 4570 cpu. Is It possible to mine this currency? Will it be profitably? January 06, 2015, 07:36:37 PM
if it gets big enough - ASICS will come
So the best ASIC protection is a new algo and complete absence of adoption
I.e. to be an Evasive Joe of crypto world. January 06, 2015, 07:32:42 PM
I like the name of this coin
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. Nothing is ASIC resistant - if it gets big enough - ASICS will come
Thank You,
Viz.
January 06, 2015, 06:42:39 PM
Quote from KryptoKash
I like the name of this coin
Now, THAT is a good name
I like the name of this coin
Now, THAT is a good name
January 06, 2015, 06:26:55 PM
I like the name of this coin
no doubt that KHC is good coin with brand new ASIC resistant aglo,devoted Dev,but weak marketing and weak promotion. 
January 06, 2015, 06:20:06 PM
I like the name of this coin
January 06, 2015, 05:42:43 PM
Here is a guesstimate:
Monetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
some wallet getinfo command supports moneysupply infoMonetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
Dev,could you implement that?
Interesting, seems like it might be a bit of work for the wallet to get the result. Exactly which wallet does this? Rather than have the wallet support this I think I'd rather have a MySQL query parse the database for display on a webpage at time of install of the proggy and track new blocks after rather than burn cpu cycles on the wallet.
If the block reward follows a strict standard that it is easy to calculate by current block height. KHC wallet would have to parse the entire blockchain in order to come up with an accurate result.
Honestly, I don't see the value of adding this feature to the Wallet.
January 06, 2015, 04:58:25 PM
My suggestion for Dev is to contact more pool operators and exchanges.
time to make this coin bigger now.
time to make this coin bigger now.
January 06, 2015, 04:56:35 PM
The net hashrate has never surpassed 30MS/s to this day,perphas no more than 25 miners.
January 06, 2015, 04:54:46 PM
Just looked at exchange volumes - almost no trades at all. It is sad that such an interesting project gets so little attention.
Probably there are not many geeks on this forum who can appreciate such complex innovations
1.People dont trust that buggy exchange.Probably there are not many geeks on this forum who can appreciate such complex innovations
2.Since the launch day till now,the wallet and miner are updated every several days.
January 06, 2015, 03:21:42 PM
Just looked at exchange volumes - almost no trades at all. It is sad that such an interesting project gets so little attention.
Probably there are not many geeks on this forum who can appreciate such complex innovations
Probably there are not many geeks on this forum who can appreciate such complex innovations
January 06, 2015, 02:47:15 PM
I have a question,each time I transfer KHC from the pool to local wallet,no fee need to pay?
January 06, 2015, 01:49:17 PM
From the OP.
Block reward (or subisidy) is paid to miners using the following schema:
That said, we are almost at block 20,000. You can expect around 1,000,000 new KHCs every 10,000 blocks until we reach the block number 120,000th. At block 125,000th there will be aprox. 12,800,000 KHCs.
After that it will be straight forward to calculate. 50 KHCs per block unless the community votes to lower the rewards starting at block 250,000 and beyond.
Block reward (or subisidy) is paid to miners using the following schema:
Code:
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+ -> A fixed subsidy of 50 KHCs.
That said, we are almost at block 20,000. You can expect around 1,000,000 new KHCs every 10,000 blocks until we reach the block number 120,000th. At block 125,000th there will be aprox. 12,800,000 KHCs.
After that it will be straight forward to calculate. 50 KHCs per block unless the community votes to lower the rewards starting at block 250,000 and beyond.
January 06, 2015, 01:35:56 PM
Here is a guesstimate:
Monetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
some wallet getinfo command supports moneysupply infoMonetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
Dev,could you implement that?
Interesting, seems like it might be a bit of work for the wallet to get the result. Exactly which wallet does this? Rather than have the wallet support this I think I'd rather have a MySQL query parse the database for display on a webpage at time of install of the proggy and track new blocks after rather than burn cpu cycles on the wallet.
If the block reward follows a strict standard that it is easy to calculate by current block height. KHC wallet would have to parse the entire blockchain in order to come up with an accurate result.
Honestly, I don't see the value of adding this feature to the Wallet.
I already built this as a Feature for Coinshield: you don't need to parse the entire blockchain. Best way is to make # of blocks not influence the supply - by utilizing reserves that fill every time-span and have block value determined by reserve supply. This will make the supply exactly regulated by time - with no way to inflate.
Viz.
KHC doesn't follow a strict block reward, it is quasi random based on transaction fee's + block reward based on block height.
January 06, 2015, 01:26:18 PM
Here is a guesstimate:
Monetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
some wallet getinfo command supports moneysupply infoMonetary Mass after 1,000 blocks: ~232,353 KHCs
Monetary Mass after 10,000 blocks: ~1,587,326 KHCs
Monetary Mass after 20,000 blocks : ~2,577,861 KHCs
To know for sure, we'd need a tool that scans the blockchain looking at the coinbase and then substrating the flat fee from it.
Dev,could you implement that?
Interesting, seems like it might be a bit of work for the wallet to get the result. Exactly which wallet does this? Rather than have the wallet support this I think I'd rather have a MySQL query parse the database for display on a webpage at time of install of the proggy and track new blocks after rather than burn cpu cycles on the wallet.
If the block reward follows a strict standard that it is easy to calculate by current block height. KHC wallet would have to parse the entire blockchain in order to come up with an accurate result.
Honestly, I don't see the value of adding this feature to the Wallet.
I already built this as a Feature for Coinshield: you don't need to parse the entire blockchain. Best way is to make # of blocks not influence the supply - by utilizing reserves that fill every time-span and have block value determined by reserve supply. This will make the supply exactly regulated by time - with no way to inflate.
Viz.
Jump to: