[ANN][DCN] Deepcoin secure hashing (CPU/GPU) New algo/ No premine/ No IPO/ PoW

[captainbluff]

Has anyone compared  power consumption between x11 and deephash algo for 280x and 290 GPUs?

Anyone?

[1713923879]

1713923879

[1713923879]

1713923879

[1713923879]

1713923879

[1713923879]

1713923879

[xwebnetwork]

Has anyone compared  power consumption between x11 and deephash algo for 280x and 290 GPUs?

Anyone?

I'll see if I can get down to my office building later to get some readings but no promises. If I were to go off temperature and fan speed alone, I'd say its less, but to what degree I am unsure.

My rigs on the top shelf (most heat) are running at approximately 40% fan speed at an acceptable 68-70C.

[marada]

Hi dev, we have listed [DCN] Deepcoin in FobCoin.com, which is a fast, efficient and secure cryptocurrency exchange focusing on the newest and the most promising cryptocurrencies. Here is the link for DCN Coin http://www.fobcoin.com/index.php/Home/Trade/index/convertId/29 . We would appreciate it if you could add the link to your exchange list.

SCAM Exchange. Do not use.

I have successfully withdrawn coins from this exchange. Why do you think this is a scam??

people have lost coins

Could you give some more details?

[marada]

I see their thread here:

https://bitcointalk.org/index.php?topic=715524.0

People are waiting for their coins, but no scam accusations yet.

[Goldshredder]

Has anyone compared  power consumption between x11 and deephash algo for 280x and 290 GPUs?

Anyone?

Don't know about comparison with X11.

But I suspect the new Deepcoin algochain uses more power than the old Qubitcoin algochain. My cards fans are now having to run faster to keep the cards at the same temp as before the fork.

[peterw1234]

https://c-cex.com/?id=vote

Vote for deepcoin to get on exchange

[bushstar]

I am looking into the issue with the clients getting stuck. What is happening is that new blocks seen by the client that are in the correct chain are being labelled as having an incorrect proof-of-work. The initial blockchain sync seems to go through okay but once the client is restarted any new blocks are seen as having an incorrect proof-of-work. I though that this might be an issue between platforms over the floats used in NGW (Nite's Gravity Wave) but this is not the case as the Linux nodes have the same problem.

The old chain is stuck back at block 76,799 looking at the newer longer chain that it cannot join so that is not causing a problem. I imagine that we are going to have to hard fork again to resolve this PoW error. Right now blocks are being run through NGW and are being accepted on to the blockchain, that same block later on is failing when being run through NGW. It seems to me that we will need to move to a new

We could move to Feathercoin's solution which outperforms KGW in responding to multipools. It took months to develop and involved some top excellent people including academics. What we did was to create simulations to show how the multipools were virtually attacking us at the time. We then simulated using solutions like KGW. After several months Dr Tony Doyle and Wellenreiter came up with the best solution. It responded to multipools faster and allowed us to recover from their impact quicker as well. When we finally went ahead with the solution it behaved as the simulations predicted which was an extra credit to the work done.

The solution is simple enough and stays on the side of the better understood conventional difficulty adjust.

The specification for the Feathercoin's Difficulty Adjust are as follows.

• The average of three averages are used for the time, no actual time span of the period is used.
• The three averages are taken from 15, 120 and 480 blocks.
• The change to the difficulty is applied with .25 damping.

Interestingly with this solution a limit of the maximum difficulty swing appears to be redundant. The launch post for this change in Feathercoin can be found here.

Any which way it seems that we will have to change the difficulty adjust solution and development work will be required. I normally have to cover the cost of my time as I have bills to pay.



Right now I am resetting the blockchain in the DNS seeder and checkpointing node. I will report back here on any developments or progress made.

[Goldshredder]

Yet everything seems to be working fine for some people (including me). Why is that?

[xwebnetwork]

Furthermore, the most active node--the SuprNova pool--is working just fine as well.

OCMiner, I am assuming you upgraded your client promptly, well before the fork, correct?

It is unquestionably an interesting dilemma.

[bigc1984]

Relaunch?

[Goldshredder]

5k DCN donated to Bushstar, thanks for your work on this.

[bigc1984]

If we relaunch issue is fixed and we will probably get a lot more people interested in the coin. Another solution is to relaunch with a premine equal to the coins in existance and have everyone exchange coins ;/ I have a lot of coins and to lose them ALL would really suck. Maybe even a 50% exchange rate would be cool.

Otherwise dev tell us how much bitcoin/deepcoin to have you devote attention to fixing. How much time do you think it will take to fix it? I can send you deepcoin but I don't know how it will help you with no exchanges and the price being so low.

[a.i.a]

I don't know what you mean by relaunch, but what we see now is fixing bugs, they release a new build of the client likely

[Goldshredder]

If we relaunch issue is fixed and we will probably get a lot more people interested in the coin. Another solution is to relaunch with a premine equal to the coins in existance and have everyone exchange coins ;/ I have a lot of coins and to lose them ALL would really suck. Maybe even a 50% exchange rate would be cool.

Otherwise dev tell us how much bitcoin/deepcoin to have you devote attention to fixing. How much time do you think it will take to fix it? I can send you deepcoin but I don't know how it will help you with no exchanges and the price being so low.

You're thinking too hard about it, too early.    bushstar has much expertise and contacts to fix this.  He is one of the most experienced developers in crypto, and his involvement in any form is a big plus for Deepcoin.  I recommend donating some DCN as recognition for his time. The DCN will have value in future. Just my opinion

[Deepcoinbiz]

If we relaunch issue is fixed and we will probably get a lot more people interested in the coin. Another solution is to relaunch with a premine equal to the coins in existance and have everyone exchange coins ;/ I have a lot of coins and to lose them ALL would really suck. Maybe even a 50% exchange rate would be cool.

Otherwise dev tell us how much bitcoin/deepcoin to have you devote attention to fixing. How much time do you think it will take to fix it? I can send you deepcoin but I don't know how it will help you with no exchanges and the price being so low.

don't worry, all your coins will be yours, you will not lose your coins in any case, it would be strange if it were otherwise, we'll do an update soon

[bushstar]

The issue has been identified and a new 0.8.7.2 client has been released for PC and the source can be found on GitHub. The algo change went through and worked as expected but somehow the block time change upset the network, the block time change was applied before the as we moved back to a conventional difficulty adjust during the algo change. This was done as NGW does not like to have its difficulty forcibly set. Somehow this change did not permeate through the retarget changes back to a conventional difficulty adjust and then back to NGW. I am away on holiday at the moment but will be back in my office tomorrow so can create the Mac client and will work on the block time change again.

Apologies for all the trouble caused with this update but the most important part of this fork was successful. Keep an eye out for a newer version soon changing the blocktime.

[fnordian]

Compiled on Linux. Working smooth.

[noegzit]

The issue has been identified and a new 0.8.7.2 client has been released for PC and the source can be found on GitHub. The algo change went through and worked as expected but somehow the block time change upset the network, the block time change was applied before the as we moved back to a conventional difficulty adjust during the algo change. This was done as NGW does not like to have its difficulty forcibly set. Somehow this change did not permeate through the retarget changes back to a conventional difficulty adjust and then back to NGW. I am away on holiday at the moment but will be back in my office tomorrow so can create the Mac client and will work on the block time change again.

Apologies for all the trouble caused with this update but the most important part of this fork was successful. Keep an eye out for a newer version soon changing the blocktime.

Good job bushstar, you deserve another donation.

[marada]

And another 5k from me.
Good job!

[Timmy95]

And yet another 5k from me to dev!

We like what you are doing!