Releasing 20th October 2015 @ 00:00:00 GMT

Official Finalized OP:

Name: DarkCash
Ticker: DSK
RPC Port: 10085
P2P Port: 10058
Block Time: 30 Seconds
PoS Reward: 0.025 DSK
PoW Reward: 0.25 DSK to 5 DSK to 2.5 DSK
Signing Algorithm: NIST5 + Schnorr Signatures

This sounds like a decent experiment, and there's no ICO or premine going on.

If your windows wallet doesn't contain a RAT, trojan, or other malicious code, this could be pretty cool to mine. Just know that lately all the CPU-only mineable coins have been released for the purposes of getting infected wallets onto miners' machines with the intention of clearing out their stashes.

I will set up a VM and mine this. If anyone else decides to mine this, do so in a virtual machine or on a secure machine with no cryptocurrency wallets or browsers logged into exchanges on that machine.

I'll remove the above warning once the coin becomes a little less new and the dev's honourable intentions bear out.

Um, just to make it clear, my post wasn't intended as an endorsement or a recommendation. I would appreciate it if you remove that quote from the OP in case it turns out you have some bad intentions.

I will edit the post you quoted, too.

Get your coin to succeed on its own honesty and strengths. I very much resent the fact that you used my quote as an "endorsement" without my knowledge or permission.

Very Sorry to do that, I will remove it ASAP

Quote from: Wolf0 on October 17, 2015, 06:29:43 PM

Quote from: Artificially Intelligent on October 16, 2015, 04:37:12 PM

Quote from: elbandi on October 16, 2015, 04:12:40 PM

Quote from: Artificially Intelligent on October 09, 2015, 01:37:58 PM

Finalized Version of the Algorithm is released (without dependancies):

https://github.com/sightisanillusion/stackhash/blob/master/stack.h

Just a note. This will crash:

Code:

int bytes = mpz_sizeinbase(product, 512);

512 is too high, docs say: base can vary from 2 to 62. but other algo (m7m) is using 256, so i think thats works too.

Elbandi

Thank you so much

doesn't that actually tell you how many 512-bit chunks the result needs? NOT how many bytes?

Played around and modded the algo again...