Since when Scrypt is CPU only?
or sha256, that i asked earlier.. 4 years ago?
|
|
|
I was initially trying to set up miner for this but i no longer think it worth it because it is 100% clone copy. so it seems.. move on more about algo if clone. Scrypt-jane(SCRYPT_SALSA64 SCRYPT_SKEIN512)+Argon2 PoW algorithm nothing serious on virustotal: Avast Win32:Malware-gen 20151224 Avira TR/BitCoinMiner.18699776 20151224 ESET-NOD32 a variant of Win32/BitCoinMiner.BJ potentially unsafe 20151224 Fortinet Riskware/BitCoinMiner 20151224 Ikarus Trojan.BitCoinMiner 20151224 K7AntiVirus Unwanted-Program ( 004b92471 ) 20151224 K7GW Unwanted-Program ( 004b92471 ) 20151224 Sophos Bitcoin Miner (PUA) 20151224
|
|
|
was there any info what base source builder would use? this is just what we need: "coins without code support" but who cares when it is pure scamming.
|
|
|
until someone makes takeover, i will keep these up
|
|
|
ok, premine...
more specs about algo?
|
|
|
norton show wallet Trojan.Gen.2 is this real ?? "Take it or leave it. Stop criticizing.- "
|
|
|
just to say: most stupid idea, ever. new shitcoin factory?
people, stay out of these things.
|
|
|
any news
yobit online for crave..
|
|
|
looks like there is a GPU miner
Are you kidding? It's a common scrypt algo. There are tons of GPU miners and even asics. something is wrong with this one... cpu only? ?? sha/scrypt.. is this a joke whole coin?
|
|
|
Regarding Cryptsy, its not only Crave but just about all of their coins. I will look up correct wallet version and upload it for all shortly, its the version before the failed takeover awhile ago..
IW
i see you have no idea about craves code. it can be fixed but it is no easy task. firstaid fix can be done, if you want to coin to be like that... shitcode
|
|
|
I was sent crave twice, two days tomorrow but they did not come so far.. I was written more than once message in support, but admin yobit not answers me. even when I sent, the coin purse was online and without delay, then bang and the "technical work", but then again worked with a delay and updated very slowly, and now, not working again...
i got my months old coins in and sold them \ Good for you lol. is there wallet still online? guess no. it is possible you maybe able to withdraw, not tested. maybe they did not get all the fullchain loaded. reason is known and it needs code update for the coin or yobit.
|
|
|
I was sent crave twice, two days tomorrow but they did not come so far.. I was written more than once message in support, but admin yobit not answers me. even when I sent, the coin purse was online and without delay, then bang and the "technical work", but then again worked with a delay and updated very slowly, and now, not working again...
i got my months old coins in and sold them
|
|
|
crave was online at yobit. and was uptodate at chain for a short time.
|
|
|
OK we are ok I have spoken with CryptoVote who is working on this piece of code whilst I work on the whitepaper. Once we implement 'getblockheaders' we wont have any issue because of that commit. However the per-peer block tracking, stalled block download detection and orphan pool limiting is a step in the right direction. yes, it is step in the right direction
|
|
|
there was some problem related to this commit but i cant remember what it was.. remember god damn you, lol Will also investigate. it was only some minor thing. maybe related headers first, cant remember
|
|
|
there was some problem related to this commit but i cant remember what it was.
|
|
|
My 7.5 million is stuck in cold storage forever lol... HDD won't click.
Edit: If I get the wallet off the cold HDD I will pour 3 million UFO for 2 satoshi
cold? put it into the oven. burning coins is in now
|
|
|
pay some attention to orphan rules. those blocktimes now without autosynch.. hexx will use way more different way when we swap. i would not remove it until hash is really up and big.
Applying some specific updates for orphans, this is in hand. i made also firstaid update commit to hexx code. much better now. still having the dub block issue..
|
|
|
pay some attention to orphan rules. those blocktimes now without autosynch.. hexx will use way more different way when we swap. i would not remove it until hash is really up and big.
|
|
|
what is the situation of current testing? same chain, forked when? current rules still same as testing git? hard to test without source or any info.. the client, i dont need.
Like I said before Cisa, I have taken the source to a private repo to stop other coins from poaching the DarkSilk work. you did not get my point.. btw. what parts of code are you still working with since last "public testing branch"? if yoy want, pm the test client link..
|
|
|
|