Dogecoin Core [DOGE, Ð]

Dogecoin is a cryptocurrency like Bitcoin, although it does not use SHA256 asits proof of work (POW). Taking development cues from Tenebrix and Litecoin,Dogecoin currently employs a simplified variant of scrypt.- Website: dogecoin.com.

License – Much license ⚖️

Dogecoin Core is released under the terms of the MIT license. SeeCOPYING for more information or seeopensource.org

Development and contributions – omg developers

Development is ongoing, and the development team, as well as other volunteers,can freely work in their own trees and submit pull requests when features orbug fixes are ready.

Version strategy

Version numbers are following major.minor.patch semantics.

Branches

There are 3 types of branches in this repository:

• master: Stable, contains the latest version of the latest major.minor release.
• maintenance: Stable, contains the latest version of previous releases, which are still under active maintenance. Format: -maint
• development: Unstable, contains new code for planned releases. Format: -dev

Master and maintenance branches are exclusively mutable by release. Plannedreleases will always have a development branch and pull requests should besubmitted against those. Maintenance branches are there for bug fixes only,please submit new features against the development branch with the highest version.

Contributions ✍️

Developers are strongly encouraged to write unit tests for new code, and tosubmit new unit tests for old code. Unit tests can be compiled and run(assuming they weren't disabled in configure) with: make check. Further details on runningand extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, writtenin Python, that are run automatically on the build server.These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

Changes should be tested by somebody other than the developer who wrote thecode. This is especially important for large or high-risk changes. It is usefulto add a test plan to the pull request description if testing the changes isnot straightforward.

Very Much Frequently Asked Questions ❓

How much doge can exist? – So many puppies! 🐕

Early 2015 (approximately a year and a half after release) there will beapproximately 100,000,000,000 coins.Each subsequent block will grant 10,000 coins to encourage miners to continue tosecure the network and make up for lost wallets on hard drives/phones/lostencryption passwords/etc.

Such mining information ⛏

Dogecoin uses a simplified variant of the scrypt key derivation function as itsproof of work with a target time of one minute per block and difficultyreadjustment after every block. The block rewards are fixed and halve every100,000 blocks. Starting with the 600,000th block, a permanent reward of10,000 Dogecoin per block will be issued.

Originally, a different payout scheme was envisioned with block rewards beingdetermined by taking the maximum reward as per the block schedule and applyingthe result of a Mersenne Twister pseudo-random number generator to arrive at anumber between 0 and the maximum reward.

This was changed starting with block 145,000, to prevent large pools from gamingthe system and mining only high reward blocks. At the same time, the difficultyretargeting was also changed from four hours to once per block (every minute),implementing an algorithm courtesy of the DigiByte Coin development team, tolessen the impact of sudden increases and decreases of network hashing rate.

The current block reward schedule:

1–99,999: 0–1,000,000 Dogecoin

100,000–144,999: 0–500,000 Dogecoin

145,000–199,999: 250,000 Dogecoin

200,000–299,999: 125,000 Dogecoin

300,000–399,999: 62,500 Dogecoin

400,000–499,999: 31,250 Dogecoin

500,000–599,999: 15,625 Dogecoin

600,000+: 10,000 Dogecoin

The original block reward schedule, with one-minute block targets and four-hour difficulty readjustment:

1–99,999: 0–1,000,000 Dogecoin

100,000–199,999: 0–500,000 Dogecoin

200,000–299,999: 0–250,000 Dogecoin

300,000–399,999: 0–125,000 Dogecoin

400,000–499,999: 0–62,500 Dogecoin

500,000–599,999: 0–31,250 Dogecoin

600,000+: 10,000 Dogecoin

Wow plz make dogecoind/dogecoin-cli/dogecoin-qt

The following are developer notes on how to build Dogecoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.

• OSX Build Notes
• Unix Build Notes
• Windows Build Notes

Such ports

• RPC 22555
• P2P 22556

Development tips and tricks

compiling for debugging

Run configure with the --enable-debug option, then make. Or run configure withCXXFLAGS="-g -ggdb -O0" or whatever debug flags you need.

debug.log

If the code is behaving strangely, take a look in the debug.log file in the data directory;error and debugging messages are written there.

The -debug=... command-line option controls debugging; running with just -debug will turnon all categories (and give you a very large debug.log file).

The Qt code routes qDebug() output to debug.log under category "qt": run with -debug=qtto see it.

testnet and regtest modes

Run with the -testnet option to run with "play dogecoins" on the test network, if youare testing multi-machine code that needs to operate across the internet.

If you are testing something that can run on one machine, run with the -regtest option.In regression test mode, blocks can be created on-demand; see qa/rpc-tests/ for teststhat run in -regtest mode.

DEBUG_LOCKORDER

Dogecoin Core is a multithreaded application, and deadlocks or other multithreading bugscan be very difficult to track down. Compiling with -DDEBUG_LOCKORDER (configureCXXFLAGS="-DDEBUG_LOCKORDER -g") inserts run-time checks to keep track of which locksare held, and adds warnings to the debug.log file if inconsistencies are detected.

wget https://archive.org/download/github.com-dogecoin-dogecoin_-_2021-04-16_21-21-23/dogecoin-dogecoin_-_2021-04-16_21-21-23.bundle

 git clone dogecoin-dogecoin_-_2021-04-16_21-21-23.bundle 

plus-circle Add Review

comment

Reviews