Topic: [ANN][DCN] Deepcoin secure hashing (CPU/GPU) New algo/ No premine/ No IPO/ PoW - page 64. (Read 182581 times)

I think they will restore it soon.

Block explorer is not working.

yes, diff is low at this time

"difficulty" : 7.76517341

wow  difficulty is low

it is an interesting idea , we can work on it.


I think Yes, but in any case it is difficult to set specific deadlines.

exactly, We are working in this direction now, but first we want to do technical work.

So, will there be any update this week?

you're right.. anonymity would probably be under specifications

By the services I understand rather what you can get for your coins.

first q2c algo coin with anonymity +1

I think the key important for Deepcoin future are services.
This part of the announcement is still empty.

We need to start thinking how to fill it up.

{
"blocks" : 38311,
"currentblocksize" : 1000,
"currentblocktx" : 0,
"difficulty" : 5.47783328,
"errors" : "",
"generate" : false,
"genproclimit" : -1,
"hashespersec" : 0,
"networkhashps" : 396671290,
"pooledtx" : 0,
"testnet" : false
}

Hello

thank you for being interested in my coin and showing bugs.

Yes, I did fork the Deepcoin (and I've written it in "credits" section on github). I've mined it before, too. I've chosen it because it has a new algo, has secure hashing etc, is GPU-friendly, resistant to ASICs, FPGAs and big farms. Its sources were clean, I've compiled it without errors etc, and I really liked it. Pure POW is much appreciated by my friends from Detk Team and me. I think that coins based on this algo are future. That's why I've decided to fork Deep but not Litecoin, Darkcoin or BTC. And that's why I am sponsoring the "Qubit Algo Wiki".

I've been thinking about creating Cassubian Detk since April, and making preparations. It was planned to be a keccak coin (yes!), forked from Copperlark. But when Deep has been launched, I've looked through it, started mining and using it, and I've changed my mind in few days.

I needed a coin to my concrete applications, not "any coin to fork". I could choose a better or worse coin to be forked, but I've chosen Deep, and I think it was a good decision. Only great, innovative and decent coins are cloned/forked. You should be proud that I've chosen You.

But I'm not so perfect, and I've omitted to replace Deep with Detk in the dialog box that was linked above. Sure there're some more things that could be made better - thanks in advance for pointing them!

Detk is not an enemy to Deep or to anybody. Detk is to make some sectors of business grow and have a well named currency. Detk's idea is to be a currency for some specific applications: like eco-business (look at my roadmap or website). Maybe Deepcoinbiz remembers our short conversations some days before launching Detk?

We are opening the new period of coins together. After SHA-256 domination period, and Scrypt domination period, we have now X11/X13/X15/Xn period. The Qubit-domination period is coming, because this is the future. Thanks to the Qubit Coin to be the first, thank You to be second. I am the third.

I wish You all the best

My rationale was jokingly favourable, actually your initial assessment was quite correct, all the examples are oversights. I'm confident that the one you spotted will be corrected shortly.

Cheers

Graham

I didn't know about it, always it is useful to expand the knowledge,
and to learn something new , thanks

Not at all, there's a long-standing tradition of devs acknowledging the upstream contributors by leaving small clues dotted around the source code for alert others to spot and share.

Dogecoin's debt to Bells :

https://github.com/dogecoin/dogecoin/blob/25d26b4848267372ef5b9f6f91480d244afd6884/src/qt/forms/sendcoinsdialog.ui#L122

Bells' debt to Luckycoin --- and, by inference, Luckycoin's debt to Alphacoin

https://github.com/bellscoin/bellscoin/blob/2af0908c5a12bac881207ae41805e5b2e1893308/src/base58.h#L13

QubitCoin's debt to Sifcoin:

https://github.com/qubitcoin/QubitCoin/blob/master/src/main.cpp#L3

The list goes on, I'll spare you the rest of it.

Cheers

Graham

Edited: punctuation

in my opinion there is something wrong 

Sorry I thought I saw the premine is % 0.3 but its % 0.03

It's not strictly necessary, all the relevant code is Open Source - qubit_hash for the Python-C interface library and a fork  of Abe that includes a general “QubitChain” class suitable for use with qubit-using coins such as the Cassubian Detk, Deepcoin and, allegedly, other new coins currently in development.

Details:

qubit-hash: https://github.com/qubitcoin-project/qubit-hash - Python interface to C sources of sph lib

Abe: https://github.com/qubitcoin-project/bitcoin-abe - (fork of) Abe, Python web app, with a QubitChain class


Commanding Abe to read the blockchain into the db:


and, for the information required to create a suitable abe-dcn.conf ....

$ grep 'pchMessageStart\[4]\' Deepcoin/src/main.cpp
unsigned char pchMessageStart[4] = { 0xae, 0xbf, 0xc0, 0xd1 };
$ grep -e 'PUBKEY_ADDRESS =' Deepcoin/src/base58.h
        PUBKEY_ADDRESS = 30, // Deepcoin addresses start with D


resulting, eventually in ....

(In this instance, user is “vagrant” because I'm developing a flexible Vagrant+ansible deployment script that should cater for most variations: ranging from creating a fully-provisioned, cloud-hosted coin daemon+Abe instance to installing just Abe on an existing machine.)

That said, I'm still trying to figure out why I can't seem to persuade Abe to synch Deepcoin completely up to date, which is why I haven't previously advertised the URL - http://minkiz.co/abe/chain/DeepCoin

Getting it working is only part of the process,  there's stuff like process monitoring and disaster recovery to consider, reflecting Abe's new importance as facilitator of exchange listings. My view is that a coin should have several block explorers - they can act as nodes, bringing some much-needed decentralisation to the otherwise centrally-oriented DNSSeed and checkpoint nodes, known to cause problems:


There's a thread for another coin that basically tells the story of when the dev of that particular coin hadn't commissioned enough resources to support the coin's single DNSSeed node, it got effectively DDOSd on launch, just like Mooncoin did, running on deacon boogie's home ADSL connection.

I've concluded that for a variety of well-supported reasons, a handful of explorers is a Good Thing(tm) to strive after as it tends to enhance stability of coin operations in the face of adverse conditions.

Cheers

Graham