Topic: [ANN][DCN] Deepcoin secure hashing (CPU/GPU) New algo/ No premine/ No IPO/ PoW (Read 182630 times)

Se puede considerar posible encontrar diferentes pelucas Santiago en todas partes del mundo.

This is a calculated risk by the authors. 

Creating a higher level encryption hash 512 bits instead of the 256 bits commonly offered. 

Rigging the mast for early top heavy for insiders to cash out.  Bad distribution.



Instead of work dictating the value and distribution, it left no incentive to develop the real advancement of Blockchain Cryptography!




However I can't remember if this project had a 512 bit private key.  Or if only the hash was 512 bits.  But I think the private key was only 256 bits. 

   Syncing 

Active nodes:
167.86.96.154
209.126.5.237

Who wants to try, CPU mining is possible.
active node: 85.216.154.156

Where can trade?  Right here!  How many would you like to buy?    

Beware, demand is high!

where can trade?

Do you know, what are prerequisites for compiling or running downloaded wallet on linux? For example on Lubuntu 14.04

Hi Graham,

Glad you took an interest in this project...........it would be good to have a restart here.   

I think upgrading the private key encryption algo would be required also.  Probably easily done with enough of the right couple people to upgrade the Bitcoin code.


It is slightly dazed and confused reading (not reading anymore) projects hacked together to make vast sums I assume quickly before they cut and run the pyramid scheme and on down the line till joe smoe holds the bag at the exchange.

They have whore'd "anon" coin without much work.  Dash has had tremendous support but the buffed off their load at the start without restarting the Blockchain?  Was it a couple Million Dash in a couple days (can't honestly remember)

Nexus Sha3 at least updated the Private keys if you want to check their for some easy reference work on their code.  ( I however do not write code)

That's encouraging - and not just from a personal perspective but objectively. With apologies for brown-bagging, I'll include a previous post I made today on the Clams thread (hopefully save you a couple of clicks) ...

---

You might consider the general orientation inferrable from my declared interests as forming the material on which to base the preface of a treatise that I'm not going to actually write down (just have fully articulated in my mental model) which could plausibly be titled: "Understanding the why of Dogecoin's continued success."

Cheers

Graham

Hi Graham. I read your article about organisational structures and social groups.  It was interesting.  I can't call my passage a brisk canter, more of a wandering trot.  

One method of growing a small organisation is to innovate.  AKA meritocracy.

Another method is to somehow tether (excuse the unintended pun) it to a larger organisation, e.g. symbiotic, or parasitic.

I like the concept that the ideal crypto project is a highly functional collective intelligence.

I'm interested in your work and the conversation.

Hey,  I sold all my BTCs, someone showed me how to invest in this ICO, a super profitable coin, and we would be rich. We have no any other way!

There never has been "a dev" engaged in the project as such, at least not in the usual type of "resident dev/team" model that most altcoins follow. It might help if you think of deepcoinbiz as the equivalent of a movie producer - organises funding, logistsics and ad hoc commissions of specialists to perform specialised tasks as and when needed.

As far as I can make out, deepcoinbiz commissioned Peter Bushnell (https://github.com/Bushstar) to create the clone (https://github.com/Deepcoinbiz/Deepcoin/commit/66ef7fefe8da3cbebf0e7e48486877b2e45c5773) and do further development work, including implementing a change in algo (https://github.com/Deepcoinbiz/Deepcoin/commit/0b8c28067c210e5c54bb48b264f70c8739fc7d9e) and and subsequent revisions (https://github.com/Deepcoinbiz/Deepcoin/commit/1a926a7e7c41cfc01f60d3a3c7791c7316effe11). There's also a nearly-complete "stealth addresses" branch (https://github.com/Deepcoinbiz/Deepcoin/commits/new-sx-0.8.7).

I don't find it profitable to speculate about this past phase of development, I'm interested only in its impact on the here and now. I believe Peter is open to commissions but that doesn't offer a resolution to the question "we need dev?" That answer to that question lies in uncovering the group's collective understanding of the role fulfilled by "the dev".

I'm afraid that I'm prone to asking "difficult" questions such as "Exactly how much dicking about with the Bitcoin codebase do you think is actually needed to support your clone?" Okay, Dash's masternode system is complex enough to require a resident dev/team but it's a far less compelling argument when the clone is almost identical except for the algo and the emissions/reward schedule.

Hence: https://github.com/gjhiggins/deepcoincore, a work-in-progress of transplanting the Deepcoin-specific elements into a Core 0.16 codebase. The rebranding is trivial, the actual first step in the process of discovering the reality behind "well, just how hard can it be?" is to replicate the genesis block and then read the blockchain. I'm halfway at the moment. The genesis block is correctly replicated and the Core 0.16 client reads the blockchain up to the hard fork at 76800. Then there's a sequence of 10 blocks for which the difficulty is calculated differently in order to prime the backwards-looking NiteGravityWell difficulty modifier. And that's not happening, which is what I am currently investigating.

So, if you fancy a play, check out the sources - careful to git checkout deepcoin and compile it up. To generate yourself a readable bootstrap.dat of blocks 0-76800, apply the following changes to the current client's contrib/linearize/example-linearize.cfg to get yourself a linearize.cfg to use.

Then run ./linearize.py linearize.cfg, copy the resulting bootstrap.dat to the datadir of your choice and fire up the client. Wait while it reads the bootstrap then clean out the datadir and try it again with a bootstrap.dat of 0-76801. Check the debug log for the rejected, out-of-order block. That's where I'm at.

I'll post notes on further progress as and when I manage to make any, assuming no-one else figures it out in the interim.

As far as I'm concerned, the answer to "Exactly how much dicking about with the Bitcoin codebase do you think is actually needed to support your clone?" is ... "As little as possible."

I'll throw this is in, in case I haven't mentioned it before: A different perspective on cryptocurrency, with the challenge - if I do manage to upgrade Deepcoin to Core 0.16 - what comes after that?

Cheers

Graham

DEEPCoin (DCN) is a visual proof of the coin, a unique coin to use and positioning themselves with a solution. This increases energy efficiency is not easy to be miners. In my opinion, this is the most effective improvements that I ever knew. The project will undoubtedly successful

Hello, everyone.
Very nice project. Wish good luck to your ICO, folks! If you are interested in Russian translation, please, write to me in PM. Thank you so much and have a nice day!

Yes I agree.
But we need dev?

Deepcoin need block explorer. Then we have a chance for DCN/BTC market on freiexchange.com( for free)  Cassubian Detk from 2014 and ZERO technical development has market on that exchange.

The inclusion of the contextually irrelevant "deeponion" testifies to the above being the result of feeding sentiment analysis into a modern equivanent of a Markov chain generator. Another step along the road towards the Butlerian jihad.

Cheers

Graham

That's of such massive relevance, a123canz999888, and as such, it's extreme pertinence to this thread is eminently applicable.