Go to Top

DuckDuckCoin (DUCK) | DuckDuckCoin Wallet | DuckDuckCoin Pool

About DuckDuckCoin

DuckDuckCoin DUCK

DuckDuckCoin DUCK

Everything from Binoculars to Camera Lenses is moved by the ton every year to satisfy this hobby. DuckDuckCoin [DUCK] is here to be the hobbyists best friend, a rare friend, a one of a kind unique trophy which only a select few will hold.

Duckduckcoin (DUCK) is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Duckduckcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network.

Algo: Scrypt
Block Reward: 0.000121
Max Coins: 121
Mined over: 12.1 months
Block time: 40 sec
Super DUCK blocks (WOW):
.00121 – every 1210th block up to 300000
Golden DUCK blocks (WOW^2):
.0121 – every 100000th block after 300000
Retargeting: 40 seconds through kimoto gravity well implementation

duckduckcoin

DuckduckCoin - scrypt based cryptocurrency

Copyright (c) 2009-2013 Bitcoin Developers Copyright (c) 2011-2013 Litecoin Developers Copyright (c) 2014 Duckduckcoin Developers

What is Duckduckcoin?

Duckduckcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Duckduckcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Duckduckcoin is also the name of the open source software which enables the use of this currency.

License

Duckduckcoin is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.

Duckduckcoin is based on Bitcoin. Its development tracks Bitcoin's, the following information applies to Bitcoin's developemnt.

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the Bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the mailing list.

The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if the code doesn't match the project's coding conventions (see doc/coding.md) or are controversial.

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test. Please be patient and help out, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code.

Unit tests for the core code are in src/test/. To compile and run them:

cd src; make -f makefile.unix test

Unit tests for the GUI code are in src/qt/test/. To compile and run them:

qmake BITCOIN_QT_TEST=1 -o Makefile.test bitcoin-qt.pro
make -f Makefile.test
./bitcoin-qt_test

Every pull request is built for both Windows and Linux on a dedicated server, and unit and sanity tests are automatically run. The binaries produced may be used for manual QA testing — a link to them will appear in a comment on the pull request posted by BitcoinPullTester. See https://github.com/TheBlueMatt/test-scripts for the build/test scripts.

Manual Quality Assurance (QA) Testing

Large changes should have a test plan, and should be tested by somebody other than the developer who wrote the code.

See https://github.com/bitcoin/QA/ for how to create a test plan.

, , ,

Leave a Reply

Your email address will not be published. Required fields are marked *