Dogecoin is a cryptocurrency like Bitcoin

Overview

Dogecoin Core [DOGE, Ð]

Dogecoin

Build Status

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

License – Much license ⚖️

Dogecoin Core is released under the terms of the MIT license. See COPYING for more information or see opensource.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 or bug 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. Planned releases will always have a development branch and pull requests should be submitted 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 to submit 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 running and extending unit tests can be found in /src/test/README.md.

There are also regression and integration tests of the RPC interface, written in 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 the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not 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 be approximately 100,000,000,000 coins. Each subsequent block will grant 10,000 coins to encourage miners to continue to secure the network and make up for lost wallets on hard drives/phones/lost encryption passwords/etc.

Such mining information

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

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

This was changed starting with block 145,000, to prevent large pools from gaming the system and mining only high reward blocks. At the same time, the difficulty retargeting was also changed from four hours to once per block (every minute), implementing an algorithm courtesy of the DigiByte Coin development team, to lessen 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.

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 with CXXFLAGS="-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 turn on 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=qt to see it.

testnet and regtest modes

Run with the -testnet option to run with "play dogecoins" on the test network, if you are 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 tests that run in -regtest mode.

DEBUG_LOCKORDER

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

Issues
  • Not actually capped at 100 billion?

    Not actually capped at 100 billion?

    Looking at getBlockValue (and nSubsidy), after the 600 000th block, it will forever be 10k a block. Once it hits 100 billion, it should be set to 0. However, this seems a bit difficult due to the randomness being brought in.

    Or rather, that this is intentional? But then the dogecoin thread should mention there is no theoretical cap, but will basically level out at 10 billion (for all intents and purposes)?

    Such confuse?

    opened by simondlr 241
  • URGENT : Dogecoin fork #2

    URGENT : Dogecoin fork #2

    Hello everyone :) Reddit is constantly going down so lets start a discussion here about what were going to do ? So far what we know is :

    1. Most of the pools are forked.
    2. 1.5 is having issues on RPC and thats why pools are using the 1.4x wallet for payouts
    3. Dogechain is running 1.4 for the exact same reason as 2. So far what we dont know is :
    4. Which fork is the correct fork ?
    opened by ghost 144
  • Consensus plan for next major release (1.21)

    Consensus plan for next major release (1.21)

    This issue describes the planned protocol features that need to be activated by consensus for the next major release (planned to be 1.21)

    Summary

    With the next major release, we plan to propose 2 protocol changes for activation at once: segwit and csv. Both have been deployed on Bitcoin's mainnet for a longer time and are considered non-contentious. As such it will save us all time when we do them at once instead of sequential. VersionBits / BIP9 will not be proposed at this time because of the conflict in the version with AuxPow, and this would be a much more dangerous, and possibly contentious change.

    A block versions 5 and protocol version 70016 will be proposed for this implementation.

    Details

    In scope

    • Segregated witness a.k.a. segwit
      • Functionality: Separates spending proofs (i.e. signatures) from transactions when embedded in blocks
      • Rationale: Further reduces transaction malleability.
      • Scope: BIP141, BIP143 and BIP147
      • Note: we will carefully consider P2W* addressing.
    • CheckSequenceVerify a.k.a. CSV
      • Functionality: Allows consensus-enforced locking of an output until a relative time and exposes the field to redeem scripts
      • Rationale: Allows for much more sophisticated redeem scripts, must-have feature for Lightning-like L2 networks.
      • Scope: BIP68, BIP112 and BIP113

    Not in scope

    • VersionBits - Needs another, more dangerous soft-fork, see #1340 and #1344. We deem this too risky to do at once with the features described above, especially for a meta-feature.
    • TapRoot - Not yet deployed on Bitcoin
    • Extension Blocks - Not yet deployed on Litecoin

    Deployment

    Deployment is planned to be proposed through a single soft fork, identified by block version 5 (full version: 0x00620104) and a protocol update to version 70016 (0x011180) through the usual 95% SuperMajority consensus rule (full activation with 1900 blocks having v5 in a 2000 block window) similar to the BIP65 soft fork that was proposed with Dogecoin Core 1.14.

    Comments / questions? Let us know here.

    consensus 
    opened by patricklodder 128
  • [feat] Radically improve Dogecoin by forking Nano: Zero fees, fastest cryptocurrency, no inflation, no mining

    [feat] Radically improve Dogecoin by forking Nano: Zero fees, fastest cryptocurrency, no inflation, no mining

    One idea to radically improve Dogecoin would be to fork Nano and implement its featureset in Doge:

    How is this accomplished?

    • A block-lattice ledger data structure (every account has its own blockchain that only the owner can modify)
    • Open Representative Voting for consensus instead of Proof of Work
    • https://docs.nano.org

    Describe Alternatives Banano is another meme coin that peeled (forked) Nano. It even has its own yellowpaper :)

    Related Code https://github.com/nanocurrency/nano-node

    Lowest latency + least error == Win

    opened by qwahzi 98
  • Peer-to-Peer Dogecoin Relay Network (based on Starlink)

    Peer-to-Peer Dogecoin Relay Network (based on Starlink)

    There exist several technical bottlenecks to scale Proof-of-Work (PoW) blockchains. Some of them are the CPU time for transaction validation, the hard disk space to store the chain, and many others.

    One of the most often overlooked bottlenecks is the communication latency and Internet speed between miners. The slower the Internet between the miners is, the less synchronized they become, and the more the blockchain security degrades. That is one of the fundamental reasons why it’s not trivial to scale Doge- or Bitcoin by simply increasing the block-time frequency and the block size. You can find empirical results for blockchain network simulations here.

    Dogecoin on Starlink?

    Now, one way to speed up a blockchain without any protocol change is to simply improve the network connectivity between the miners! This is where Starlink, the satellite-based Internet from SpaceX could help Dogecoin to be closer to the moon.

    Starlink latency between London and Singapore is expected to be much lower than current Internet round trip times (RTT). Starlink could hence speed up Dogecoin’s block and transaction propagation, effectively scaling its blockchain substantially.

    1_xjFd6c4GylHPlSh9s9VO2Q

    Mark Handley beautifully simulated how much lower the latency of Starlink would be, when compared to the current terrestrial Internet. For example, he estimates that the round trip time (RTT) between London and Singapore would be about 108ms on Starlink, while Fiber optic Internet currently yields 159ms.

    Starlink is certainly already highly anticipated by traditional financial institutions to perform lower latency arbitrage across the major financial exchanges. Using Starlink as a network to propagate blockchain peer-to-peer data among miners would equally help speed up substantially the current blockchain throughput, without deteriorating its security. Naturally, a possible risk here would be for a single for-profit company to effectively own the entire blockchain relay network, a risk that may be mitigated with future orthogonal satellite Internet services.

    Blockchain Relay Network

    Analogous to the FIBRE network, Erlay, and other prior relay networks, Dogecoin could very well scale its transaction throughput by orders of magnitude, if its miners were to engage in a dedicated Starlink relay network. Naturally, this relay network propagation protocol should be optimized for the Starlink characteristics to fully take advantage of its topology.

    Quantifying the optimal protocol, and parameters is certainly a very exciting avenue towards scaling Dogecoin! What do you think?

    external 
    opened by arthurgervais 72
  • much crash to encrypt moneybag

    much crash to encrypt moneybag

    crash on win7 64bit when trying to encrypt wallet. someone on forum also reported this. other wallets do not crash.

    NOTE: Only on certain windows platforms and not on others

    Other Manifestations: Cannot import private key Cannot run console commands

    bug 
    opened by dethica 69
  • Proposed Dogecoin Scaling Roadmap

    Proposed Dogecoin Scaling Roadmap

    So seeing as how rnicoll said they would like a Dogecoin CTO, (EDIT: I am not proposing roles and do NOT want to be the "Dogecoin CTO"! I am merely saying I can help with those sorts of functions, as can many others here) I can help out with some tech planning as someone who has thought deeply about blockchain and other forms of crypto since Feathercoin came out and has dozens of inventions in the crypto space, and am the CTO of my own crypto (non-blockchain) project. I also have been around the Dogecoin community since 2017 and have always been a huge supporter of tail emission, of which Dogecoin is the most prominent example.

    Based on this post to reddit with tons of community support: https://www.reddit.com/r/dogecoindev/comments/nfabqm/im_not_elon_but_i_do_understand_him_a_deep_dive/

    And also this github issue for segwit2x: https://github.com/dogecoin/dogecoin/issues/1849

    Galaxy Digital Analysis: https://docsend.com/view/vutymtgqjf99yrpu

    Ross on "Working with Elon": https://decrypt.co/71264/dogecoin-dev-what-its-like-working-with-elon-musk

    Satoshi Nakamoto on Scaling: https://www.reddit.com/r/btc/comments/6cb4ey/bitcoin_can_already_scale_much_larger_than_that/

    2021 -Scale 2x current-

    1. Reduce min tx fees to below 1 cent in 1.14.4 update. Elon suggests 100x reduction, I suggest 200x (which would put us at half a cent when we hit $1)

    2. Once fee is reduced, monitor blocksize for 3 months. See if the blocksize increases significantly and we have any spam issues. I anticipate blocksize will not change significantly and there will be no spam issues.

    3. If blocksize is stable, implement segwit and double max blocksize to 2mb at the same time in 1.21 update.

    2022 -Scale 8x current-

    1. Address any issues with segwit and monitor that blocksize is stable.

    2. Once everything is stable, reduce blocktime by one-half to 30 seconds. Monitor syncing and orphan rate. Orphan rate should always stay below 10%.

    3. Once everything is stable double blocksize again (to 4mb). Monitor for spam and adjust min tx fee accordingly. Implement lightning code as needed.

    2023 -Scale 16x current-

    1. Once everything is stable reduce blocktime by one-half to 15 seconds. Monitor syncing and orphan rate.

    2024 -Scale 40x current-

    1. Once everything is stable Increase max blocksize to 10mb (10x bitcoin and our current blocksize). Adjust min tx fee as needed to keep blockchain growth under control and in-line with our recommended full node specifications *.

    Beyond -Scale potentially 100x + current-

    1. As orphan rate approaches 5% consider future incremental blocktime decreases to eventually 6-7 seconds or faster depending on how we can stay synced and maintain orphan rate below 10%.

    2. If we get to the point that block space is limited and fees are increasing, consider increasing max blocksize while keeping to parameters of node syncing and orphan rate.

    *Notes:

    • Of course we will need to change block reward every time blocktime is updated to maintain a constant emission of 10,000 coins per minute.

    • We need to develop metrics and measures for orphan rate and syncing rate.

    • We need to develop suggested specifications for full nodes and required specifications for full nodes. RAM, processor speed/cores, and storage space should be specified. We need to consider that each full node does the job of the entire paypal server farm and therefore a rudimentary server will be required if we progress beyond a hobby project. In light of this we need to make running a "pruning node" easily selected from the core wallet.

    • If energy usage / asic unavailability due to chip shortage becomes a serious issue and is causing potential centralization, consider change of PoW algorithm to ProgPoW which is a well developed ASIC resistant GPU friendly hashing algorithm. If energy use or GPU availability becomes a major concern, there is always the CPU algo Yespower.

    • If Proof of Work proves way too slow or other serious problems with PoW arise (in other words; "if all else fails"), we can consider a change to PoS or Proof of Rest https://github.com/dogecoin/dogecoin/issues/1942 or some other solution. Or PoS as a layer 2 https://github.com/dogecoin/dogecoin/issues/1924.

    • We should also do research into how our nodes sync with having our nonce in other chains' (we are merge mined with all scrypt coins, not just Litecoin) blockchain and how that effects our syncing, if at all.

    • Consider improving/tweaking payout protocols for development contributions with the goal that someone can quit their job and work full time on dogecoin development with minimal risk.

    opened by GiverofMemory 63
  • Fixed Block Sizes & Block re-targetting

    Fixed Block Sizes & Block re-targetting

    Implemented Digishield on 1min retarget, and Fixed Block Sizes after the 150k block mark, in order to prevent multipool's gaming the random block algorithm, and distorting the hash rates.

    NB: UNTESTED ON TESTNET. Do not deploy.

    11/03/14 : Release Candidate

    • /u/lleti
    opened by lleti 61
  • Doge Chain Balance amout not showing up in Doge Core Wallet

    Doge Chain Balance amout not showing up in Doge Core Wallet

    Describe the issue

    Transfer of my first mining payout shows in dogechain but hasn't went to dogecore wallet

    Expected behaviour

    Balance from dogechain should show in dogecore wallet

    Actual behaviour

    Correct amount shows in dogechain

    Screenshots.

    Lost

    What version of Dogecoin Core are you using?

    Dogecoin Core version v1.14.3 (64-bit)

    Machine specs:

    • OS: Windows 8.1 Pro
    • CPU: i7 4980HQ
    • RAM: 32 G
    • Disk size: 500 G
    • Disk Type (HD/SDD): SSD
    opened by ghmac 54
  • Can we double blocksize at the same time as we introduce Segwit?

    Can we double blocksize at the same time as we introduce Segwit?

    Example code pull https://github.com/bitcoin/bitcoin/pull/6451

    This topic has received massive upvotes with 97% up for doubling blocksize when introducing segwit: https://www.reddit.com/r/dogecoindev/comments/mvdzls/transaction_speed_and_fees_hyper_doge/

    And this topic describes it also: https://www.reddit.com/r/dogecoindev/comments/muvl1t/scaling_bitcoin_was_supposed_to_implement_segwit/

    Sporkin posts that relate to this: (Thanks u/jamiereeno) https://www.reddit.com/r/dogecoin/comments/be8pe8/fully_exited_all_positions_in_doge/el4v0bj/?utm_source=share&utm_medium=ios_app&utm_name=iossmf&context=3

    Sporklin post with an acknowledgment from langer_hans: (Thanks u/jamiereeno) https://www.reddit.com/r/dogecoin/comments/2hdjuj/dogecoin_is_an_independent_codebase/?utm_source=share&utm_medium=ios_app&utm_name=iossmf

    See comments for a proposal by @rnicoll to reduce blocktime to achieve the same goal

    Even supposing Segwit leads to a fully functional lightning network, still a transaction pair needs to be completed before a lightning channel can be opened. So it makes sense to scale blocksize to accommodate for mass adoption so that fees and congestion stay low - and high value transactions can be settled on-chain. Also I strongly suggest that segwit addresses always remain optional, like in Bitcoin. My suggestion is to double blocksize whenever needed, perhaps every 7 years. I think doing this at the same time as the addition of segwit can help set a culture that we will increase blocksize as needed to scale to be money for the world. Currently we never fill up blocks which also shows that increasing the blocksize isn't going to magically make the blocks bigger in the near term and there would be no difference to running a node. As a global payments network, we will eventually need to settle (on-chain) hundreds or more transactions per second (even if there are thousands of lightning per second) and we can only accommodate 33 with a 1mb block size. If we doubled blocksize every 7 years on average, this stays well below moore's law and running a node will never become burdensome to someone willing to invest in a reasonable server. Again each server is hosting a global payments network so we shouldn't assume a full node will always be able to be run from a smartphone, so I think slowly increasing blocksize would be the way to go to make sure we are able to scale properly.

    I understand this will take a hard fork, but it keeps with the core of Dogecoin so it will get full adoption and will not lead to a chain split. I think the biggest risk to a chain split is refusing to increase blocksize, and that is what led to the creation of Bitcoin Cash. So a hard fork to double blocksize will not lead to a chain split and can help unify the community and show the world that we indeed will scale to be money for the world and can increase mainstream adoption even more. ETH hardforks regularly and this does not lead to chain splits, so it is a very viable strategy especially if planned long in advance.

    referred to discussions 
    opened by GiverofMemory 49
  • Dogecoin not syncing

    Dogecoin not syncing

    Dogecoin not syncing

    ./dogecoin-cli getinfo { "version": 1140200, "protocolversion": 70015, "walletversion": 130000, "balance": 0.00000000, "blocks": 0, "timeoffset": 0, "connections": 0, "proxy": "", "difficulty": 0.000244140625, "testnet": false, "keypoololdest": 1604517534, "keypoolsize": 100, "paytxfee": 0.00000000, "relayfee": 1.00000000,

    Server: Ubuntu 18 RAM 30GB SSD 800 GB

    debug.log 2020-11-04 19:35:34 init message: Loading addresses... 2020-11-04 19:35:34 Loaded 0 addresses from peers.dat 0ms 2020-11-04 19:35:34 init message: Loading banlist... 2020-11-04 19:35:34 Imported mempool transactions from disk: 0 successes, 0 failed, 0 expired 2020-11-04 19:35:34 init message: Starting network threads... 2020-11-04 19:35:34 torcontrol thread start 2020-11-04 19:35:34 net thread start 2020-11-04 19:35:34 dnsseed thread start 2020-11-04 19:35:34 Loading addresses from DNS seeds (could take a while) 2020-11-04 19:35:34 init message: Done loading 2020-11-04 19:35:34 addcon thread start 2020-11-04 19:35:34 msghand thread start 2020-11-04 19:35:34 opencon thread start 2020-11-04 19:35:44 0 addresses found from DNS seeds 2020-11-04 19:35:44 dnsseed thread exit 2020-11-04 19:36:35 Adding fixed seed nodes as DNS doesn't seem to be available.

    Why is the node not syncing? i have tried on multiple servers. The other coins are fine. Only problem with DOGE...

    opened by ExchangeAssetsGraphs 49
  • [qa] improve fee parametrization testing

    [qa] improve fee parametrization testing

    To prevent situations like #3087 consistently, I think we should make parameter interactions explicit to help reviewing when introducing new parameters and build a parameter interaction test - probably both on top of #1313 - and then backport whatever is there on top of what we got from Bitcoin Core into 1.21.

    However - #1313 may take a longer time to complete. Perhaps in the interim we can build a test that tests all the fee parametrization we have, either in a new test, or as an extension of p2p-policy

    QA 
    opened by patricklodder 0
  • [bug] maxTxFee is not set to -maxtxfee if -disablewallet is also active

    [bug] maxTxFee is not set to -maxtxfee if -disablewallet is also active

    Bug Report

    Current behavior: Setting -maxtxfee=1000.00 has no effect when -disablewallet is also active.

    Expected behavior Since sendrawtransaction RPC endpoint is also affected by maxtxfee, it should take effect even when CWallet is never initialized.

    Steps to reproduce:

    1. Start dogecoind with -maxtxfee=1000.00 and -disablewallet
    2. Use an external wallet to create a valid batch transaction with an absolute fee > 100 DOGE
    3. Send it using the sendrawtransaction RPC
    4. Get the absurd-high-fee error

    Screenshots None

    Dogecoin Core version v1.14.6

    Machine specs

    • OS: Ubuntu 20.04
    • CPU: AWS vCPU (EC2)
    • RAM: 8GB
    • Disk size: 1000GB
    • Disk Type (HD/SDD): HD

    Extra information The only place in the source that checks the -maxtxfee runtime arg is here, but at the top of the function it does an early return true if -disablewallet is active.

    bug 
    opened by junderw 1
  • ci: Added sse2 scrypt option to Win64 experimental build

    ci: Added sse2 scrypt option to Win64 experimental build

    bench_dogecoin on Windows 10 (Intel i7 w/AVX2 SHAs)

    c:\dogecoin>avx2\bin\bench_dogecoin.exe
    #Benchmark,count,min,max,average,min_cycles,max_cycles,average_cycles
    ...
    SHA1,768,0.001311466097832,0.001372124999762,0.001338852879902,2766443,2906564,2828688
    SHA256,384,0.002561874687672,0.002745762467384,0.002618161961436,5426619,5756365,5530148
    SHA256_32b,6,0.189843535423279,0.195170998573303,0.192108511924744,401013412,412416121,405702898
    SHA512,640,0.001647468656301,0.001767069101334,0.001697367057204,3499345,3715532,3583560
    Scrypt,4608,0.000224933493882,0.000230658333749,0.000226830753187,473877,485739,479228
    SipHash_32b,48,0.020995736122131,0.022479534149170,0.021513854463895,44609869,48099245,45437085
    Sleep100ms,10,0.100115895271301,0.100720047950745,0.100514984130859,211440027,212718901,212244756
    Trig,27262976,0.000000035440735,0.000000040950454,0.000000038092909,76,84,80
    

    bench_dogecoin on Windows 10 (Intel i7 w/AVX2 SHAs and SSE2 Scrypt)

    c:\dogecoin>avx2_sse_scrypt\bin\bench_dogecoin.exe
    #Benchmark,count,min,max,average,min_cycles,max_cycles,average_cycles
    ...
    SHA1,768,0.001281008124352,0.001342564821243,0.001314044309159,2742723,2839084,2774571
    SHA256,384,0.002562001347542,0.002837650477886,0.002622580155730,5418986,5976710,5536936
    SHA256_32b,6,0.189343571662903,0.206030011177063,0.200109998385111,399318005,435111878,422554670
    SHA512,640,0.001646999269724,0.001733690500259,0.001676921918988,3494553,3679962,3544248
    Scrypt,5632,0.000175375025719,0.000182999297976,0.000178022013808,371993,387787,375935
    SipHash_32b,48,0.020983994007111,0.024076461791992,0.021306956807772,44129880,50467834,44999032
    Sleep100ms,10,0.100460052490234,0.100820541381836,0.100678014755249,212059922,212909643,212461765
    Trig,27262976,0.000000035372068,0.000000041885414,0.000000038290505,74,89,80
    
    c:\dogecoin>
    
    opened by edtubbs 0
  • Wallet error when loading 1.14.5 wallet in 1.21 qt

    Wallet error when loading 1.14.5 wallet in 1.21 qt

    Just a quick note, I am getting "noncritical" error "All keys read correctly, but transaction data or address book entries might be missing or incorrect." when loading wallet from 1.14.5:

    image

    But after re-scanning it (and synchronizing), it shows correct information:

    image

    I was thinking of trying to fix this error but it says somewhere in the comments that trying to fix it could make things ~~works~~ worse and so I didn't want to do that 😇

    Originally posted by @victorsk2019 in https://github.com/dogecoin/dogecoin/issues/2977#issuecomment-1200479543

    bug 
    opened by patricklodder 0
  • Update secp256k1 subtree

    Update secp256k1 subtree

    WARNING: CONSENSUS CRITICAL -> so be careful!

    This is the subtree we haven't updated since 1.14.0. I have been reluctant mostly because this is consensus critical code and risky because of that, and late last year after we updated the other ones I didn't think we could get enough eyes on it for this to go through. I think now we do. Additionally, the problem of not updating this grows the longer we wait, so this is the lets-bite-the-bullet proposal.

    I picked bitcoin-core/[email protected] as the target because:

    1. This is at the time of writing the latest merged into Bitcoin Core's master branch, and
    2. I didn't find any commits between this commit and bitcoin-core/secp256k1's master branch at the time of writing that were significant enough to take on more exposure than Bitcoin Core does. (I have not seen any related issues opened on Bitcoin Core's GitHub repo about this so far, but will continue to monitor.)

    Additionally, because of that last commit, 44c2452fd3, we will break ASLR on Windows (as we already do for dogecoin-cli - bad, but now also for dogecoin-qt - really bad) so I have backported a workaround from bitcoin/[email protected] into this PR as well.

    Since the squash is huge, I think we need to do 3 things:

    1. Review - or at least glance over - the changes done upstream
    2. If we're satisfied with the results, merge this into 1.14.7-dev
    3. Assess fitness for release before we push out 1.14.7: if we would push that out after a week or 2, we'll probably have to revert, but if we can incorporate this into a month or more of testing, CI runs and gitian builds, I think we're fine.

    Open to change the approach.

    consensus backport dependencies gitian check needed 
    opened by patricklodder 4
Releases(v1.14.6)
  • v1.14.6(Jul 20, 2022)

    This is a new minor version release, including important security updates and changes to network efficiency.

    All Dogecoin Core users - miners, services, relay operators and wallet users - are strongly recommended to upgrade.

    A full description of all changes is available in the release notes

    Security-related fixes

    This release contains multiple security related fixes:

    • The alert system has been removed and processing of alert messages has been disabled
    • The transaction download system has been made more reliable
    • The protocol implementation has been amended to reject buggy or malformed messages
    • Memory management in events of high network traffic or when connected to extremely slow peers has been improved

    Fee Recommendation

    This release changes the recommended dust limit for all participants on the Dogecoin network from 1 DOGE to 0.01 DOGE. The full recommendation can be found in the documentation.

    Breaking changes

    • The behavior of the dumpwallet and backupwallet RPC methods, to exclusively write to the directory specified by -backupdir and no longer overwrite files
    • The maximum number of addnode records that a node will track has been limited to 800

    New features

    • A new RPC method, liststucktransactions has been added to help wallet operators identify if any transactions are stuck (have not been mined and are not in the mempool) and enable resolution. This helps in cases where node-local fee or dust policies change, to prevent the node from sending out old transactions that got lost.
    • Pruning configuration has been added to the UI, to make it easier to save diskspace for users of graphical (wallet) installations.
    • A new RPC method, setmaxconnections, has been introduced that enables wallet and node operators to change the maximum number of connections their node allows without needing to restart allowing for more fine-grained control of the node's network capacities.
    • The graph in the UI's traffic monitor has been significantly improved by keeping track of the traffic we see in the background and then rendering it on demand, at any desired scale.
    • A new RPC method, rescan, has been added to allow node operators to rescan the chain for wallet transactions from a certain height. This can help speed up the rescan process for keys that are known to be generated after a certain date or block height.
    • A new endpoint has been added to the REST server to find the current best known block at a certain height, without having to do RPC calls. This is useful for service implementations that need to track or query blocks.

    Translation updates

    • Bulgarian
    • Dutch
    • French
    • Italian
    • Korean
    • Persian
    • Portuguese (pt_PT)
    • Tamil

    RPC API Changes

    • The verifychain RPC command no longer accepts negative values
    • addnode will now return error -32 when the address provided is too long
    • getpeerinfo provides 2 new fields per peer, addr_processed and addr_rate_limited

    Dependency updates

    • Updated zlib to 1.2.12.
    • Updated libevent to 2.1.12-stable.
    • Update the LevelDB subtree to use the same version as Bitcoin 22.0, from the bitcoin-core maintained fork.
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.6-aarch64-linux-gnu.tar.gz(11.35 MB)
    dogecoin-1.14.6-arm-linux-gnueabihf.tar.gz(10.15 MB)
    dogecoin-1.14.6-i686-pc-linux-gnu.tar.gz(29.20 MB)
    dogecoin-1.14.6-osx-signed.dmg(12.95 MB)
    dogecoin-1.14.6-osx-unsigned.dmg(13.38 MB)
    dogecoin-1.14.6-win32-setup-unsigned.exe(14.36 MB)
    dogecoin-1.14.6-win32.zip(25.37 MB)
    dogecoin-1.14.6-win64-setup-unsigned.exe(14.69 MB)
    dogecoin-1.14.6-win64.zip(25.95 MB)
    dogecoin-1.14.6-x86_64-linux-gnu.tar.gz(27.76 MB)
    SHA256SUMS.asc(1.52 KB)
  • v1.14.5(Nov 8, 2021)

    This is a new minor version release, including important security updates and changes to network policies. All Dogecoin Core users, miners, services, relay operators and wallet users are strongly recommended to upgrade.

    This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

    Important Security Updates

    This release contains fixes for 2 high severity vulnerabilities that affect most Dogecoin Core users:

    • Remote Code Execution in Dogecoin QT (CVE-2021-3401)
    • Sensitive Information Exposure on Unix platforms (CVE-2019-15947)

    Dogecoin QT (Graphical User Interface) users on all platforms and wallet users on the Linux platform are urged to please update their installations to this version immediately, to prevent malicious actors from exploiting these vulnerabilities.

    Fee Reductions

    This release finalizes a new minimum fee recommendation for all participants on the Dogecoin network, following the reduction of relay and mining defaults in 1.14.4. With this release, the minimum fees when creating transactions are recommended to be as follows:

    • the recommended minimum transaction fee is 0.01 DOGE/kb, and
    • the recommended dust limit is 1 DOGE, and
    • the recommended RBF increment is 0.001 DOGE.

    See the full recommendation here

    RPC API Changes

    • Added softdustlimit and harddustlimit fields to getnetworkinfo
    • Added createauxblock and submitauxblock methods
    • Added -rpcnamecoinapi that allows miners to use Namecoin-compatible AuxPoW APIs, for both getauxblock and createauxblock methods.

    Other notable changes

    • Updated Berkely DB to 5.3 and OpenSSL to 1.0.2u.
    • The version displayed on QT's overview page has been changed to display the full version
    • Updated the HD wallet derivation path to be compliant with SLIP44
    • Updated the FreeBSD build.
    • Added xkbcommon 0.8.4 as a separate dependency to fix keyboard compatibility issues
    • Added a getting started guide

    See the release notes for a full description of this release.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.5-aarch64-linux-gnu.tar.gz(11.36 MB)
    dogecoin-1.14.5-arm-linux-gnueabihf.tar.gz(10.16 MB)
    dogecoin-1.14.5-i686-pc-linux-gnu.tar.gz(29.15 MB)
    dogecoin-1.14.5-osx.dmg(12.84 MB)
    dogecoin-1.14.5-win32-setup-unsigned.exe(14.24 MB)
    dogecoin-1.14.5-win32.zip(25.31 MB)
    dogecoin-1.14.5-win64-setup-unsigned.exe(14.56 MB)
    dogecoin-1.14.5-win64.zip(25.88 MB)
    dogecoin-1.14.5-x86_64-linux-gnu.tar.gz(27.70 MB)
  • v1.14.4(Aug 21, 2021)

    This is a new minor version release, including various bugfixes and performance improvements. It is a recommended update for all users.

    This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

    Enabling Future Fee Reductions

    Prepares the network for a reduction of the recommended fees by reducing the default fee requirement 1000x for transaction relay and 100x for mining. At the same time it increases freedom for miner, wallet and node operators to agree on fees regardless of defaults coded into the Dogecoin Core software by solidifying fine-grained controls for operators to deviate from built-in defaults.

    This realizes the first part of a two-stage update to lower the fee recommendation - a followup release will implement the lower fee recommendation, once the network has adapted to the relay defaults introduced with this version of Dogecoin Core.

    Synchronization Improvements

    Removes a bug in the network layer where a 1.14 node would open many parallel requests for headers to its peers, increasing the total data transferred during initial block download up to 50 times the required data, per peer, unnecessarily. As a result, synchronization time has been reduced by around 2.5 times.

    RPC Improvements

    getpeerinfo now includes feefilter value for each peer, to be able to diagnose transaction relay issues.

    Other notable changes

    • Proactively disconnect peers sending block headers which would build on an invalid chain.
    • Improve handling and logging of invalid blocks and their descendants
    • Add menu option to import a private key
    • Add column to peers table showing bytes sent/received, accessible via "Debug Window" from the "Help" menu.
    • Add GUI for adding peers manually, accessible from the peers table of the Debug Window.
    • Regtest network can now generate AuxPoW blocks.
    • Corrections to French Canadian, Chinese, German, Indonesian, Korean, Polish and Portuguese translations
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.4-aarch64-linux-gnu.tar.gz(9.72 MB)
    dogecoin-1.14.4-arm-linux-gnueabihf.tar.gz(9.07 MB)
    dogecoin-1.14.4-i686-pc-linux-gnu.tar.gz(24.90 MB)
    dogecoin-1.14.4-osx.dmg(12.50 MB)
    dogecoin-1.14.4-win32-setup-unsigned.exe(13.60 MB)
    dogecoin-1.14.4-win32.zip(23.47 MB)
    dogecoin-1.14.4-win64-setup-unsigned.exe(14.24 MB)
    dogecoin-1.14.4-win64.zip(24.91 MB)
    dogecoin-1.14.4-x86_64-linux-gnu.tar.gz(24.49 MB)
  • v1.14.3(Feb 28, 2021)

    This is a new minor update that includes important performance improvements. It is a strongly recommended update for everyone.

    This release can be installed over an existing 1.14 installation seamlessly, without the need for uninstallation, re-indexation or re-download. Simply shut down your running Dogecoin-QT or dogecoind, perform the installation and restart your node.

    Improve synchronization speed

    Significantly improves the speed at which a node can upload blocks, by removing expensive integrity checks that were performed each time a block is sent to another node. When a block is received and during rescans of the locally stored blockchain, the checks are still performed.

    Reduce default mempool expiry time

    Reduces the default time that transactions are cached in the mempool from 336 hours to 24 hours. This default setting can be overridden with the -mempoolexpiry parameter by individual node operators to a value (expressed in hours) that makes the most sense for the use cases the node serves.

    Other changes and improvements

    • Increase block download timeouts
    • Add size_on_disk, prune_target_size, automatic_pruning to getblockchaininfo
    • Add query options to listunspent RPC call
    • Set BIP65 softfork heights in chainparams.cpp.
    • Update package links for OSX cross compilation.
    • Change IPC prefix from bitcoin: to dogecoin:.
    • Locale independent sorting.
    • Corrections to Italian translation.
    • Refresh main and test network checkpoints and seeds.
    • Do not print an error on connection timeouts through proxy.
    • Numerous fixes to automated tests.
    • Numerous fixes to documentation.
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.3-aarch64-linux-gnu.tar.gz(9.62 MB)
    dogecoin-1.14.3-arm-linux-gnueabihf.tar.gz(8.99 MB)
    dogecoin-1.14.3-i686-pc-linux-gnu.tar.gz(24.68 MB)
    dogecoin-1.14.3-osx.dmg(12.35 MB)
    dogecoin-1.14.3-win32-setup-unsigned.exe(13.45 MB)
    dogecoin-1.14.3-win32.zip(23.26 MB)
    dogecoin-1.14.3-win64-setup-unsigned.exe(14.03 MB)
    dogecoin-1.14.3-win64.zip(24.65 MB)
    dogecoin-1.14.3-x86_64-linux-gnu.tar.gz(24.26 MB)
  • v1.14.2(Nov 8, 2019)

    All users are encouraged to upgrade to this version, it includes an important bugfix to 1.14.0, and enables support for OP_CHECKLOCKTIMEVERIFY compared to pre-1.14.0.

    This is a bugfix release which:

    • Reverts a change of behaviour in the getauxblock command. The target field was renamed to _target in Namecoin and this change should not have appeared in Dogecoin, for compatibility with previous mining pool configurations. This has now been corrected.
    • Fix description of supermajority based forks in getblockchaininfo - the full block version number was used instead of just the last byte, which made it appear forks were triggered early.
    • Change references to "Bitcoin" to "Dogecoin" - these weren't user visible, but are done for consistency.
    • Corrects the handling of so-called dust outputs in regards to calculating fees. This fixes an issue where a change output smaller than 1 DOGE would create a transaction that was not going to be relayed.

    Note: We have skipped 1.14.1 as the last bug and its fix were found after 1.14.1 was tagged already.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.2-aarch64-linux-gnu.tar.gz(9.62 MB)
    dogecoin-1.14.2-arm-linux-gnueabihf.tar.gz(8.98 MB)
    dogecoin-1.14.2-i686-pc-linux-gnu.tar.gz(24.67 MB)
    dogecoin-1.14.2-osx.dmg(12.35 MB)
    dogecoin-1.14.2-win32-setup-unsigned.exe(13.46 MB)
    dogecoin-1.14.2-win32.zip(23.24 MB)
    dogecoin-1.14.2-win64-setup-unsigned.exe(14.01 MB)
    dogecoin-1.14.2-win64.zip(24.64 MB)
    dogecoin-1.14.2-x86_64-linux-gnu.tar.gz(24.25 MB)
  • v1.14.0(Jun 22, 2019)

    This is the long awaited Dogecoin Core 1.14!

    Please make sure, if you upgrade an existing version, to make a (current!) backup of your wallet.dat file! We have successfully upgraded existing wallets in our testing, but you should always keep a backup of that file regardless.

    This version contains a soft fork to enable BIP-65 (OP_CHECKLOCKTIMEVERIFY). The fork is locked in at 750 of the previous 1000 blocks. At 950 of the previous 1000 blocks with base version 4, the client will start to reject blocks with a base version of <= 3. For pool operates this means that they should update to the final 1.14 version once it is released asap, but at least before the fork is activated to not risk mining invalid blocks after 95% of the mined blocks are on base version 4. While this is not very relevant to end users you should still make sure to update to 1.14 final sooner than later.

    Updating will also enable us to continue testing with the 1.17 client, so please do so.

    Please note that getinfo is deprecated and will be removed in the next Dogecoin release. There are now several different commands that contain parts of that data instead. Please see the release notes for detail.

    Full release notes are available at https://github.com/dogecoin/dogecoin/blob/master/doc/release-notes.md

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.0-aarch64-linux-gnu.tar.gz(9.62 MB)
    dogecoin-1.14.0-arm-linux-gnueabihf.tar.gz(8.98 MB)
    dogecoin-1.14.0-i686-pc-linux-gnu.tar.gz(24.67 MB)
    dogecoin-1.14.0-osx.dmg(12.34 MB)
    dogecoin-1.14.0-win32-setup-unsigned.exe(13.43 MB)
    dogecoin-1.14.0-win32.zip(23.25 MB)
    dogecoin-1.14.0-win64-setup-unsigned.exe(14.02 MB)
    dogecoin-1.14.0-win64.zip(24.64 MB)
    dogecoin-1.14.0-x86_64-linux-gnu.tar.gz(24.25 MB)
  • v1.14-rc-1(Apr 18, 2019)

    This is the first release candidate of Dogecoin Core 1.14.

    There have been only slight improvements compared to Beta 1, mainly fixing verification progress display and the fee calculation for transactions. Please make sure, if you upgrade an existing version, to make a (current!) backup of your wallet.dat file! We have successfully upgraded existing wallets in our testing, but you should always keep a backup of that file regardless.

    This version contains a soft fork to enable BIP-65 (OP_CHECKLOCKTIMEVERIFY). The fork is locked in at 750 of the previous 1000 blocks. At 950 of the previous 1000 blocks with base version 4, the client will start to reject blocks with a base version of <= 3. For pool operates this means that they should update to the final 1.14 version once it is released asap, but at least before the fork is activated to not risk mining invalid blocks after 95% of the mined blocks are on base version 4. While this is not very relevant to end users you should still make sure to update to 1.14 final sooner than later.

    Important notes:

    Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.0-aarch64-linux-gnu.tar.gz(9.62 MB)
    dogecoin-1.14.0-arm-linux-gnueabihf.tar.gz(8.98 MB)
    dogecoin-1.14.0-i686-pc-linux-gnu.tar.gz(24.67 MB)
    dogecoin-1.14.0-osx.dmg(12.35 MB)
    dogecoin-1.14.0-win32-setup-unsigned.exe(13.46 MB)
    dogecoin-1.14.0-win32.zip(23.24 MB)
    dogecoin-1.14.0-win64-setup-unsigned.exe(14.03 MB)
    dogecoin-1.14.0-win64.zip(24.64 MB)
    dogecoin-1.14.0-x86_64-linux-gnu.tar.gz(24.25 MB)
  • v1.14-beta-1(Nov 16, 2018)

    This is the first beta release of Dogecoin Core 1.14.

    The main changes since Alpha 4 include fixes for the macOS version and some branding issues we encountered while testing. This also marks the first binary release of Dogecoin Core 1.14. You will be able to download binaries and installer packages down below. Please make sure, if you upgrade an existing version, to make a (current!) backup of your wallet.dat file! We have successfully upgraded existing wallets in our testing, but you should always keep a backup of that file regardless.

    This version contains a soft fork to enable BIP-65 (OP_CHECKLOCKTIMEVERIFY). The fork is locked in at 750 of the previous 1000 blocks. At 950 of the previous 1000 blocks with base version 4, the client will start to reject blocks with a base version of <= 3. For pool operates this means that they should update to the final 1.14 version once it is released asap, but at least before the fork is activated to not risk mining invalid blocks after 95% of the mined blocks are on base version 4. While this is not very relevant to end users you should still make sure to update to 1.14 final sooner than later.

    Important notes:

    • Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.14.2-aarch64-linux-gnu.tar.gz(9.62 MB)
    dogecoin-1.14.2-arm-linux-gnueabihf.tar.gz(8.98 MB)
    dogecoin-1.14.2-i686-pc-linux-gnu.tar.gz(24.67 MB)
    dogecoin-1.14.2-osx.dmg(12.34 MB)
    dogecoin-1.14.2-win32-setup-unsigned.exe(13.45 MB)
    dogecoin-1.14.2-win32.zip(23.25 MB)
    dogecoin-1.14.2-win64-setup-unsigned.exe(14.01 MB)
    dogecoin-1.14.2-win64.zip(24.64 MB)
    dogecoin-1.14.2-x86_64-linux-gnu.tar.gz(24.25 MB)
  • v1.14-alpha-4(Sep 23, 2018)

    This is the fourth alpha release of Dogecoin Core 1.14! It contains an important fix for https://nvd.nist.gov/vuln/detail/CVE-2018-17144 and anyone running an earlier alpha must upgrade. This also includes other changes from Bitcoin Core 0.14.0 to 0.14.3 and some tweaks to parameters for BIP0009 version bits.

    In theory we have an OS X build ready to go, and are waiting for a pull request to merge the fixes, and we can then build the beta/release candidate (TBD) of 1.14.

    Important notes:

    • This is not a binary release, you must be comfortable compiling it yourself.
    • Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.
    Source code(tar.gz)
    Source code(zip)
  • v1.14-alpha-3(Apr 23, 2018)

    This is the third alpha release of Dogecoin Core 1.14! It contains an important bugfix from the previous alpha, and you are recommended to upgrade. This update changes the default transaction version generated from 2 to 1, so that they are understood by 1.10 clients. Previously the transactions were ignored by old clients and therefore never mined on the production network. We'll update to version 2 transactions in a later release.

    The alert system has also been re-added to this version, and live money tests have started with this version. It's essentially a beta candidate, although further cleanup is expected before there is a formal beta.

    Important notes:

    • This is not a binary release, you must be comfortable compiling it yourself.
    • Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

    The key tasks before the final 1.14 release include:

    • Update Gitian builds to support OS X.
    • Stress test the release on the test network.
    • Hard disable (i.e. rip out) upgrading via version bits as it poses a risk to AuxPoW if there's any mistakes in it being disabled currently.
    Source code(tar.gz)
    Source code(zip)
  • v1.14-alpha-2(Feb 18, 2018)

    This is the second alpha release of Dogecoin Core 1.14! It contains two important bugfixes compared to the first alpha, and anyone on 1.14-alpha-1 should upgrade immediately. The major changes are:

    • Fee rounding is now applied consistently across the code base by applying it in the fee rate rather than in the calling code (which had lead to some calls being missed).
    • Coinbase maturity checks are now enforced correctly.

    Important notes:

    • This is not a binary release, you must be comfortable compiling it yourself.
    • At the moment we expect to re-introduce the alert system into 1.14 before release, please disregard the release notes that discuss its deprecation/removal.
    • Don't use this with money you aren't willing to lose. This is the version the developers will start doing mainnet currency tests with, however we'll be keeping amounts very small until there's a beta.
    • Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

    The key tasks before the final 1.14 release include:

    • Update Gitian builds to support OS X.
    • Re-introduce and test the alert system.
    • Stress test the release on the test network.
    • Hard disable (i.e. rip out) upgrading via version bits as it poses a risk to AuxPoW if there's any mistakes in it being disabled currently.
    Source code(tar.gz)
    Source code(zip)
  • v1.14-alpha-1(Feb 4, 2018)

    This is the first alpha release of Dogecoin Core 1.14! It has known limitations that need to be addressed before a release version, in particular around the fee calculations, however it is ready for testing by a wider audience than the Dogecoin developers.

    Important notes:

    • This is not a binary release, you must be comfortable compiling it yourself.
    • At the moment we expect to re-introduce the alert system into 1.14 before release, please disregard the release notes that discuss its deprecation/removal.
    • You should not use this with Dogecoin on the main network; it is intended for transactions on the testnet, and block verification/relaying on production. Please wait for a beta before using with real money.
    • Please do not mine on the production network with this release, as it would trigger a soft fork earlier than expected.

    The key tasks before the final 1.14 release include:

    • Complete an audit of the RPC tests to identify why the remaining tests fail, and correct the test or code as applicable.
    • Update Gitian builds to support OS X
    • Re-introduce and test the alert system
    • Stress test the release on the test network
    Source code(tar.gz)
    Source code(zip)
  • v1.10.0-dogeparty(Nov 10, 2015)

    This is an alternative version of Dogecoin Core 1.10 with modifications to make it compatible with Dogeparty. Specifically, this adds support for address indexing and the "searchrawtransactions" RPC command. You should use Dogecoin Core 1.10 unless you need these extensions, as it has undergone further testing.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.10.0-linux32.tar.gz(32.55 MB)
    dogecoin-1.10.0-linux64.tar.gz(32.20 MB)
    dogecoin-1.10.0-win32-setup-unsigned.exe(12.45 MB)
    dogecoin-1.10.0-win32.zip(30.69 MB)
    dogecoin-1.10.0-win64-setup-unsigned.exe(12.92 MB)
    dogecoin-1.10.0-win64.zip(32.34 MB)
  • v1.10.0(Nov 10, 2015)

    Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
    We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11. 1.10 is a recommended update for all users, and if you cannot update to 1.10 for whatever reason, you must update to 1.8.3 which is a critical security fix to 1.8.2.

    Upgrading

    To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

    IMPORTANT: During reindex transactions will be "replayed" by the wallet as they're indexed, meaning that your balance will not necessarily be accurate until the end of the reindex process. Do not send transactions during reindex, as this may result in conflicted transactions once the reindex is complete.

    Notable changes

    For further explanation of these, see the above mentioned Bitcoin release notes.

    Faster synchronization

    Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Watch only address support

    It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

    Strict signature encoding (BIP66)

    This release activates BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

    Block file pruning

    It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

    General comments

    Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.10.0-linux32.tar.gz(32.52 MB)
    dogecoin-1.10.0-linux64.tar.gz(32.17 MB)
    dogecoin-1.10.0-osx-signed.dmg(11.80 MB)
    dogecoin-1.10.0-win32-setup-unsigned.exe(12.43 MB)
    dogecoin-1.10.0-win32.zip(30.65 MB)
    dogecoin-1.10.0-win64-setup-unsigned.exe(12.91 MB)
    dogecoin-1.10.0-win64.zip(32.30 MB)
  • v1.8.3(Nov 10, 2015)

    Dogecoin Core 1.8.3 is a security release for those who cannot upgrade to Dogecoin Core 1.10 ONLY. It fixes a remote security hole in miniupnpnc, as well as issues in regards to an upcoming announcement of possible DoS vulnerabilities. See the announcement on the bitcoin-dev mailing list for reference. It is strongly recommended to upgrade your installation in case you run a node open to inbound connections from the internet.

    If you cannot upgrade to Dogecoin Core 1.10, you MUST update to 1.8.3 to remain secure.

    Dogecoin Core Release Notes

    Pull in patches from upstream to mitigate the risk of a DoS attack. Update the DNS seeds for more reliable bootstrapping of the initial peer discovery. Update the list of fixed nodes, in case all other means of peer discovery fail. Update to latest miniupnpc, which fixes a security hole

    Credits

    Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into this Dogecoin Core release:

    P. Kaufmann Max K. Ross Nicoll Wladimir J. van der Laan Pieter Wuille

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.3-mac.zip(23.61 MB)
    dogecoin-1.8.3-win32-setup.exe(11.93 MB)
    dogecoin-1.8.3-win64-setup.exe(12.63 MB)
    dogecoin-1.8.3.tar.gz(32.19 MB)
  • v1.10.0-RC-1(Oct 19, 2015)

    Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
    We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11. 1.10 is a recommended update for all users, and if you cannot update to 1.10 for whatever reason, you must update to 1.8.3 which is a critical security fix to 1.8.2.

    This first release candidate introduces a number of bug fixes and improvements since beta 2:

    • Correct icon in Help menu for About option
    • Enforce low-S encoding on transactions to be relayed, to eliminate that form of transaction malleability
    • Correct some regressions in operation of AuxPoW mining
    • Update to latest version of miniupnpc (critical security fix!)
    • Switch available units to Doge, kDoge and mDoge.

    Upgrading

    To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

    Notable changes

    For further explanation of these, see the above mentioned Bitcoin release notes.

    Faster synchronization

    Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Watch only address support

    It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

    Strict signature encoding (BIP66)

    One of the reasons why mining is disabled on this release is the introduction of BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. To not let this happen too early, mining is disabled for now. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

    Block file pruning

    It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

    General comments

    Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.10-RC-1-osx.dmg(11.80 MB)
    dogecoin-1.10.0-linux32.tar.gz(32.52 MB)
    dogecoin-1.10.0-linux64.tar.gz(32.17 MB)
    dogecoin-1.10.0-win32-setup-unsigned.exe(12.43 MB)
    dogecoin-1.10.0-win32.zip(30.65 MB)
    dogecoin-1.10.0-win64-setup-unsigned.exe(12.91 MB)
    dogecoin-1.10.0-win64.zip(32.30 MB)
  • v1.8.3-RC-1(Oct 19, 2015)

    Dogecoin Core 1.8.3

    Dogecoin Core 1.8.3 is a security release. It fixes a remote security hole in miniupnpnc, as well as issues in regards to an upcoming announcement of possible DoS vulnerabilities. See the announcement on the bitcoin-dev mailing list for reference. It is strongly recommended to upgrade your installation in case you run a node open to inbound connections from the internet.
    If your installation is not open to incoming connections this update is not mandatory, but we still recommend keeping your client up to date.

    Dogecoin Core Release Notes

    • Pull in patches from upstream to mitigate the risk of a DoS attack.
    • Update the DNS seeds for more reliable bootstrapping of the initial peer discovery.
    • Update the list of fixed nodes, in case all other means of peer discovery fail.
    • Update to latest miniupnpc, which fixes a security hole

    Credits

    Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into this Dogecoin Core release:

    • P. Kaufmann
    • Max K.
    • Ross Nicoll
    • Wladimir J. van der Laan
    • Pieter Wuille
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.3-rc-1-linux32.zip(9.36 MB)
    dogecoin-1.8.3-rc-1-linux64.zip(9.21 MB)
    dogecoin-1.8.3-rc-1-win32-setup.exe(11.92 MB)
    dogecoin-1.8.3-rc-1-win32.zip(15.42 MB)
    dogecoin-1.8.3-rc-1-win64-setup.exe(12.62 MB)
    dogecoin-1.8.3-rc-1-win64.zip(16.42 MB)
  • v1.10-beta-2(Sep 11, 2015)

    Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
    We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11

    Beta 2 introduces a number of bug fixes and improvements since beta 1:

    • Correct AuxPoW support checks to match Dogecoin Core 1.8 rather than Namecoin
    • Correct and expand RPC unit tests
    • Add NODE_BLOOM service bit
    • Fix missing new line in error messages
    • Update testnet checkpoints so syncing is smoother, and add DNS seed
    • Correct incompatibilities in fee calculation code compared to Dogecoin Core 1.8
    • Remove old Bitcoin release notes
    • Replace further references to Bitcoin with Dogecoin where user-facing
    • Use locale-specific number formatting instead of thin spaces as thousand-separator in numbers

    Upgrading

    To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

    Mining

    For this beta release, we decided to disable AuxPoW mining, while further testing is completed. The functionality will be re-enabled in a later release candidate.

    Notable changes

    For further explanation of these, see the above mentioned Bitcoin release notes.

    Faster synchronization

    Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Watch only address support

    It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

    Strict signature encoding (BIP66)

    One of the reasons why mining is disabled on this release is the introduction of BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. To not let this happen too early, mining is disabled for now. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

    Block file pruning

    It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

    General comments

    Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.10-beta-2-osx.dmg(11.80 MB)
    dogecoin-1.10.0-linux32.tar.gz(32.52 MB)
    dogecoin-1.10.0-linux64.tar.gz(32.17 MB)
    dogecoin-1.10.0-win32-setup-unsigned.exe(12.44 MB)
    dogecoin-1.10.0-win32.zip(30.64 MB)
    dogecoin-1.10.0-win64-setup-unsigned.exe(12.91 MB)
    dogecoin-1.10.0-win64.zip(32.30 MB)
  • v1.10-beta-1(Aug 16, 2015)

    Dogecoin Core 1.10 Beta 1

    Dogecoin 1.10 is a complete rebuild based on Bitcoin 0.11. This means in terms of the code-base we introduced all the changes between Bitcoin 0.9 and 0.11 into this version of Dogecoin Core.
    We therefore suggest to read the release notes of both Bitcoin 0.10 and Bitcoin 0.11

    Upgrading

    To upgrade from any version below 1.10 you will need to re-index once, as the block database format has changed. If you run the Qt GUI client, it will prompt you to do so on the first start after the update. If you run a dogecoind daemon, you will need to start it with the parameter -reindex once after you updated. This process can take a few hours, depending on the performance of your machine.

    Mining

    For this beta release, we decided to disable AuxPoW mining, while further testing is completed. The functionality will be re-enabled in a later release candidate.

    Notable changes

    For further explanation of these, see the above mentioned Bitcoin release notes.

    Faster synchronization

    Dogecoin Core 1.10 introduces headers-first and parallel block synchronization to greatly reduce the initial blockchain synchronization time.

    Watch only address support

    It is now possible to add public keys to your wallet that will be held in a "watch only" state. This means you will get information about incoming/outgoing transactions and resulting balance changes. Especially useful to keep track of your paper wallets.

    Strict signature encoding (BIP66)

    One of the reasons why mining is disabled on this release is the introduction of BIP66 which enforces strict rules about how transaction signatures are encoded and therefore will introduce a new block version (3). These rules will only activate once a certain number of blocks are mined with this new version. To not let this happen too early, mining is disabled for now. NOTE: This is not a hard fork, as all existing wallets will accept version 3 blocks, although they'll fail to enforce the new requirements.

    Block file pruning

    It is possible to run a Dogecoin node without keeping the full blockchain on your disk. This is currently incompatible with having a wallet on that client due to the fact that some actions regarding a wallet require the full block data. The minimum amount of kept blocks has been changed from Bitcoin to reflect our shorter block times.

    General comments

    Please backup your wallet regularly and especially before performing this upgrade. Do not copy your wallet.dat while Dogecoin Core is open. Instead you should either use the backup feature you find in the "File" menu or shut down Dogecoin Core completely before you make a copy of your wallet.dat.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.10.0-linux32.tar.gz(32.47 MB)
    dogecoin-1.10.0-linux64.tar.gz(32.13 MB)
    dogecoin-1.10.0-win32-setup-unsigned.exe(12.47 MB)
    dogecoin-1.10.0-win32.zip(30.63 MB)
    dogecoin-1.10.0-win64-setup-unsigned.exe(12.94 MB)
    dogecoin-1.10.0-win64.zip(32.28 MB)
    dogecoin-v1.10-beta-1-osx.dmg(11.80 MB)
  • v1.8.2(Jan 20, 2015)

    Dogecoin Core 1.8.2

    Dogecoin Core 1.8.2 is a bugfix release. It updates OpenSSL to 1.0.1l, mainly fixing security issues.

    Dogecoin Core Release Notes

    • Update to OpenSSL 1.0.1l

    OpenSSL Warning

    The main takeaway is that builds from http://dogecoin.com are not affected. But if you build your own version, please make sure you update to 1.8.2 before updating your OpenSSL!

    Please refer to this section in the Bitcoin Core release notes for further info: https://github.com/bitcoin/bitcoin/blob/0.9/doc/release-notes.md#openssl-warning

    Credits

    Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into Dogecoin Core:

    • Cory Fields
    • langerhans
    • Patrick Lodder
    • Gregory Maxwell
    • Ross Nicoll
    • Wladimir J. van der Laan
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.2-linux32.zip(9.36 MB)
    dogecoin-1.8.2-linux64.zip(9.21 MB)
    dogecoin-1.8.2-mac.zip(24.11 MB)
    dogecoin-1.8.2-win32-setup.exe(11.92 MB)
    dogecoin-1.8.2-win32.zip(15.42 MB)
    dogecoin-1.8.2-win64-setup.exe(12.63 MB)
    dogecoin-1.8.2-win64.zip(16.43 MB)
  • v1.8.1(Dec 20, 2014)

    Dogecoin Core 1.8.1

    Dogecoin Core 1.8.1 is primarily a bugfix release, bringing Dogecoin Core in line with Bitcoin 0.9.3. Dogecoin Core 1.8.1 also adds in support for printing paper wallets, and disables connections to pre-1.8 clients. This is a RECOMMENDED upgrade due to the large number of bug fixes, but is not a required one.

    Paper wallet support has been developed by AndyMeows (IRC username), and can be accessed via the "File" menu. It's intended for two purposes; to generate small value paper wallets to hand out, and more permanent deposit paper wallets for keeping balances offline.

    IMPORTANT: If you are producing offline paper wallets, you should do so on a computer that's disconnected from the Internet. While the wallet generator does not save the keys it generates, this ensures there is no risk of a virus or similar capturing the key from memory or interfering with its generation.

    Dogecoin Core Release Notes

    • Translation improvements and corrections
    • Disable Transifex based translation process (not used by Dogecoin Core)
    • Add checkpoints around AuxPoW switchover block (371,337)
    • Disable connections from pre-1.8 Dogecoin Core clients
    • Use HTTPS with dogechain.info
    • Remove unreachable code introduced with AuxPoW support
    • "blocknotify" option now supports %i as a format parameter, which is replaced by block height
    • New option "maxoutconnections" to set the maximum number of outbound peer connections. Defaults to 8, minimum is 2, maximum is whatever "maxconnections" is set to (default 125).

    Bitcoin Core Release Notes

    Full release notes for Bitcoin Core 0.9.3 are available from https://bitcoin.org/en/release/v0.9.3 , but highlights are included below:

    • Better orphan transaction handling
    • Add -maxorphantx= and -maxorphanblocks= options for control over the maximum orphan transactions and blocks
    • key.cpp: fail with a friendlier message on missing ssl EC support
    • Upgrade OpenSSL to 1.0.1i (see https://www.openssl.org/news/secadv_20140806.txt - just to be sure, no critical issues for Bitcoin Core)

    Known Issues

    There is a known issue with quantities in JSON used by the RPC interface (https://github.com/dogecoin/dogecoin/issues/134). This stems from the use of a floating point precision number to hold fixed precision data. Currently looking at solutions, which primarily either involve JSON which is not compliant to the specification, or making the RPC layer slightly incompatible with the conventional Bitcoin API.

    This only affects values significantly below 1 Doge, however merchants may wish to round to the nearest Doge on all transactions for now.

    Credits

    Listed in strictly alphabetical order, using name listed in Github. This includes those whose contributions to Bitcoin Core have been merged into Dogecoin Core:

    • Abderraouf Adjal
    • Andymeows
    • Daniel Kraft
    • Gavin Andresen
    • langerhans
    • michilumin
    • nameEO
    • Patrick Lodder
    • Ross Nicoll
    • Wladimir J. van der Laan
    • Whit J
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.1-linux32.zip(9.36 MB)
    dogecoin-1.8.1-linux64.zip(9.21 MB)
    dogecoin-1.8.1-mac.zip(24.11 MB)
    dogecoin-1.8.1-win32-setup.exe(11.92 MB)
    dogecoin-1.8.1-win32.zip(15.42 MB)
    dogecoin-1.8.1-win64-setup.exe(12.63 MB)
    dogecoin-1.8.1-win64.zip(16.43 MB)
  • v1.8.1-beta-1(Oct 6, 2014)

    Dogecoin Core 1.8.1 Beta 1

    Dogecoin Core 1.8.1 is a non-mandatory update. It includes patches introduced by upstream Bitcoin 0.9.3 (see release notes here https://bitcoin.org/en/release/v0.9.3) and as a new feature integrated paper wallet printing support. It also blocks clients older than version 1.8 from connecting as these wouldn't be able to sync anymore anyway due to the introduction of AuxPoW. Several translations have been updated.

    About paper wallet printing It is advised to print paper wallet on an offline computer. The client will warn you about that in case you are connected to the network.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.0-mac.zip(23.63 MB)
    dogecoin-1.8.1-beta-1-linux32.zip(9.35 MB)
    dogecoin-1.8.1-beta-1-linux64.zip(9.20 MB)
    dogecoin-1.8.1-beta-1-win32.zip(15.41 MB)
    dogecoin-1.8.1-beta-1-win64.zip(16.42 MB)
    dogecoin-1.8.1-win32-setup.exe(11.92 MB)
    dogecoin-1.8.1-win64-setup.exe(12.63 MB)
  • v1.8.0(Aug 24, 2014)

    Dogecoin Core 1.8

    Dogecoin Core 1.8 introduces AuxPoW from block 371,337. AuxPoW is a technology which enables miners to submit work done while mining other coins, as work on the Dogecoin block chain. Dogecoin Core 1.8 also enables payment protocol support for Dogecoin (note that Dogecoin's implementation of payment protocol is not compatible with Bitcoin's protocol). Lastly, 1.8 also includes all fixes from Bitcoin Core 0.9.2, whose release notes you can read at https://bitcoin.org/en/release/v0.9.2 (this is a summary, and the release includes around 150 bugfixes from Bitcoin Core).

    Note that all users MUST upgrade to 1.8. If you're unable to update before the switchover block (371,337, expected around 12 September 2014), you MUST update as soon as possible afterwards in order to be able to continue to use Dogecoin. Users remaining on the previous client will not be able to receive or spend Dogecoin (with the exception of with other nodes who have not upgraded).

    Upgrading

    Before upgrading, back up your wallet.dat file just in case of any problems; you can back up the wallet.dat file by using the "Backup Wallet" option from the "File" menu. Ensure your existing wallet software is closed before upgrading.

    Note that a full reindex is required as part of the upgrade to 1.8, and this will typically take around an hour to complete. If you are running the Qt client you will be prompted to reindex when first running the software, while if you use "dogecoind" you must run it the first time with the "-reindex" command line option.

    To ensure a smooth switchover to AuxPoW, 1.8 has safe mode disabled 1 hour before until 24 hours after the switch block. This ensures the actually legit fork will not trigger safe mode and halt mining. If you don't want to have this behavior, then refer to the 1.8-safemode branch. This one doesn't include the patch to disable safe mode.

    Downgrading

    As 1.8 includes a substantial change to the mining protocol, downgrading to previous clients is not possible.

    AuxPoW

    AuxPoW is enabled from block 371,337. Until that block the RPC commands for using AuxPoW will not function, and AuxPoW blocks will be rejected.

    AuxPoW benefits Dogecoin in two ways; firstly, the effective hashrate of the coin is increased by these additional miners, making it harder to perform a 51% attack against the coin, and secondly it reduces conflict for resources (Scrypt miners), demotivating multipools from switching between Dogecoin and other Scrypt coins.

    AuxPoW blocks are mined using the "getauxblock" and "getworkaux" RPC commands. Support for AuxPoW mining is included in Powerpool ( https://github.com/simplecrypto/powerpool/ ) and p2pool ( http://p2pool.in/ ).

    In comparison to the AuxPoW implementation in United Scrypt Coin, Dogecoin uses a different coinbase transaction input script format which includes block height in compliance with BIP0034.

    Payment Protocol

    Dogecoin Core 1.8 adds payment protocol support, which is used to streamline payments being made to merchants.

    This protocol is defined in DIP0070-DIP0072, based on the BIP standards with the same assigned numbers. DIP standards can be found at https://github.com/dogecoin/dips/ . The key differencs between the Bitcoin and Dogecoin payment protocols are that the Dogecoin payment request uses a "genesis" field containing the hash of the network's genesis block to identify networks instead of the "network" field. Further, MIME types for the request, payment and response are modified to identify the files as distinct types from the Bitcoin files.

    Transaction Fees

    As of 1.8 all transactions have fees applied by defaults, with no exemptions made for "old" coins. This ensures fees are consistent, while remaining extremely competitive (typically 1 Doge, or around $0.00012 per transaction).

    RPC Allow IP

    The format of IP masks supplied to the "rpcallowip" command line option has changed. It no longer accepts subnets like '192.168..', and the format '192.168/16" should be used instead.

    Other Changes

    The Chinese and Korean translations have been updated.

    Protocol version has been updated to 70003, meaning that a later release of the client can block access to all old clients (70002 and below).

    In case of an error reading the block database from disk, the database cursor could be left open, which caused an assertion error later. The database cursor is now correctly disposed of in all cases.

    Tweaked trigger conditions for safe mode to take into account the much faster block time of Dogecoin compared to Bitcoin. This should lead to less false positives.

    A problem in parsing mangled dogecoin: URIs under Windows has been resolved, and as part of this work network detection for dogecoin: URIs is now more robust.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.0-linux32.zip(9.10 MB)
    dogecoin-1.8.0-linux64.zip(8.94 MB)
    dogecoin-1.8.0-mac.zip(23.51 MB)
    dogecoin-1.8.0-win32-setup.exe(11.57 MB)
    dogecoin-1.8.0-win32.zip(15.06 MB)
    dogecoin-1.8.0-win64-setup.exe(12.31 MB)
    dogecoin-1.8.0-win64.zip(16.07 MB)
  • v1.8.0-beta-1(Aug 19, 2014)

    Dogecoin Core 1.8 beta 1


    This is the first beta of Dogecoin Core 1.8.

    It already has AuxPoW functionality built in. Starting block for testnet was 158,100, for mainnet it will be 371,337.

    Blockchain reindex

    After you updated your client and start 1.8 the first time, the Qt client will prompt you for a reindex of the block data. It is important to accept this, as the format has changed. This takes, depending on your machine, somehwere around 15-30 minutes. It will not re-download the chain, just reindex your local copy. If you are running a daemon (dogecoind), then you need to manually start it with the -reindex parameter once!

    Testnet

    Since the testnet already has AuxPoW enabled, you can start the client with the -testnet flasg and play around on it. You can mine directly into your wallet by pointing your miner to the IP of the wallet and port 44555. You may need to start it with -server and set a RPC user and password in the dogecoin.conf file.

    Safe mode

    If you are using the client on the testnet you might see fork warnings. In case your client goes into safe mode while playing on the testnet you can run it with -disablesafemode. We are working on making the transition on mainnet as smooth as possible for the final version.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.8.0-beta-1-linux32.zip(9.10 MB)
    dogecoin-1.8.0-beta-1-linux64.zip(8.94 MB)
    dogecoin-1.8.0-beta-1-mac.zip(23.50 MB)
    dogecoin-1.8.0-beta-1-win32-setup.exe(11.32 MB)
    dogecoin-1.8.0-beta-1-win32.zip(15.06 MB)
    dogecoin-1.8.0-beta-1-win64-setup.exe(12.12 MB)
    dogecoin-1.8.0-beta-1-win64.zip(16.07 MB)
  • v1.7.1(Jun 15, 2014)

    This is a security release.

    Dogecoin Core 1.7.1 is built against OpenSSL 1.0.1h, released to close recently disclosed vulnerabilities, which could have an impact on the usage of RPC over SSL. If you use this feature, it is advised that you upgrade to 1.7.1 and OpenSSL 1.0.1h.

    If you do not use RPC over SSL, you don't need to upgrade.

    No other changes where made in this release.

    If you are still using Dogecoin Core 1.6 and also use RPC over SSL in a publicly accessible manner, we advise you to upgrade to 1.7.1 or restrict the usage of RPC to your local controlled network.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.7.1-linux32.zip(13.56 MB)
    dogecoin-1.7.1-linux64.zip(13.57 MB)
    dogecoin-1.7.1-win32-setup.exe(11.05 MB)
    dogecoin-1.7.1-win32.zip(14.70 MB)
    dogecoin-1.7.1-win64-setup.exe(11.81 MB)
    dogecoin-1.7.1-win64.zip(15.67 MB)
    dogecoin-core-1.7.1-mac.zip(23.32 MB)
  • v1.7.0(May 17, 2014)

    Dogecoin 1.7.0

    Dogecoin 1.7 is a complete re-architecture of the Dogecoin client, changing from using the Litecoin client as its base, to Bitcoin 0.9. It's still Dogecoin, same Scrypt PoW algorithm, same reward schedule, but there's a lot of changes under the hood.

    For the full Bitcoin 0.9 changelog, please see https://bitcointalk.org/index.php?topic=522014

    Downgrading

    First and foremost, please note that downgrading from 1.7 to 1.6 is not trivial. 1.7 now uses Berkeley DB 5.1 as its default database (in place of 4.8), and as such may create database files which are incompatible with previous versions.

    Rebranding to Dogecoin Core

    Following in the footsteps of Bitcoin (Core), the Dogecoin reference client has been rebranded as "Dogecoin Core". This helps separate its identity from Dogecoin (the network).

    dogecoin-cli

    Where previously commands were sent to dogecoind by running "dogecoind ", 1.7 adopts the model from Bitcoin Core 0.9 where there is a separate "dogecoin-cli" executable which us used instead. This avoids the risk of accidentally trying to start two daemons at the same time, for example.

    Fork detection

    This version is able to detect forks and warn about them both in the GUI and through calling the alertnotify script when a sufficiently long or invalid fork occurs.

    Changes from RC1

    • Change the amount input field step value to 1 DOGE
    • Update the splash screen
    • Update Chinese translation

    General comments

    For anyone running an exchange, please also note that in light of the 51% attack against Reddcoin last night, the Dogecoin developers now recommend a minimum of 10 confirmations for payments into an exchange.

    Source code(tar.gz)
    Source code(zip)
    dogecoin-core-1.7.0-linux32.zip(13.56 MB)
    dogecoin-core-1.7.0-linux64.zip(13.69 MB)
    dogecoin-core-1.7.0-mac.zip(21.47 MB)
    dogecoin-core-1.7.0-win32-setup.exe(11.05 MB)
    dogecoin-core-1.7.0-win32.zip(14.70 MB)
    dogecoin-core-1.7.0-win64-setup.exe(11.80 MB)
    dogecoin-core-1.7.0-win64.zip(15.67 MB)
  • v1.7.0-RC-1(May 4, 2014)

    This is Dogecoin 1.7.0 RC1. Following a run down of the changes since Beta 2:

    • Ship Windows installers
    • Ship statically linked Linux binaries
    • New icon for OS X with retina resultions
    • Payment protocol has been disabled for 1.7 and will be reworked for a future release
    • Require 3 instead of 6 confirmations again in the Qt wallet
    • Added new checkpoints
    • Add and update a few more unit tests
    • Small cleanups and tweaks
    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.7.0-RC1-win32-setup.exe(11.03 MB)
    dogecoin-1.7.0-RC1-win64-setup.exe(11.80 MB)
    dogecoin-core-1.7.0-RC1-linux32.zip(13.55 MB)
    dogecoin-core-1.7.0-RC1-linux64.zip(13.56 MB)
    dogecoin-core-1.7.0-RC1-mac-Qt5.zip(20.85 MB)
    dogecoin-core-1.7.0-RC1-mac.zip(14.38 MB)
    dogecoin-core-1.7.0-RC1-win32.zip(14.69 MB)
    dogecoin-core-1.7.0-RC1-win64.zip(15.66 MB)
  • v1.7.0-Beta-2(Apr 22, 2014)

    This release mainly fixes a bug which could cause problems with spending coinbase (mined) transactions in Beta 1.

    Changes:

    • Fixed coinbase maturity calculation
    • Added dogecoind and dogecoin-cli binaries for Windows
    • Use Qt4 for Mac
    • Updated most of the unit tests to reflect Dogecoin
    • Removed remaining references to Bitcoin in the UI
    • Updated documentation

    Thanks to everyone who contributed!

    For more information about the changes in 1.7, check the Alpha 1 release notes: https://github.com/dogecoin/dogecoin/releases/tag/v1.7.0-Alpha-1

    Source code(tar.gz)
    Source code(zip)
    dogecoin-core-1.7.0-Beta-2-linux32.zip(8.83 MB)
    dogecoin-core-1.7.0-Beta-2-linux64.zip(8.66 MB)
    dogecoin-core-1.7.0-Beta-2-mac.zip(28.23 MB)
    dogecoin-core-1.7.0-Beta-2-win32.zip(14.69 MB)
    dogecoin-core-1.7.0-Beta-2-win64.zip(15.65 MB)
  • v1.7.0-Beta-1(Apr 12, 2014)

    This is Beta 1 of the all new Dogecoin Core 1.7.0 client.

    This client runs on the production network by default. As always, please backup your wallet.dat.

    Changes since Alpha 1:

    • Translation fixes
    • Fix payment URI prefix
    • Added testnet seeds
    • Added back the "-change" option
    • Added back context menu entry to show transaction on dogechain.info
    • Upgrade to OpenSSL 1.0.1g
    • Added back the logo in the wallet. With custom option by putting a dogecoin.png into the data directory

    For more information about the changes in 1.7, check the Alpha 1 release notes: https://github.com/dogecoin/dogecoin/releases/tag/v1.7.0-Alpha-1

    Source code(tar.gz)
    Source code(zip)
    dogecoin-qt-1.7.0-Beta-1-linux32.zip(8.83 MB)
    dogecoin-qt-1.7.0-Beta-1-linux64.zip(8.66 MB)
    dogecoin-qt-1.7.0-Beta-1-mac.zip(28.44 MB)
    dogecoin-qt-1.7.0-Beta-1-win32.zip(10.77 MB)
    dogecoin-qt-1.7.0-Beta-1-win64.zip(11.43 MB)
  • v1.7.0-Alpha-1(Apr 3, 2014)

    Dogecoin Core 1.7 Alpha

    Dogecoin Core 1.7 is a complete re-architecture of Dogecoin, changing from using the Litecoin client as its base, to Bitcoin 0.9. It's still Dogecoin, same Scrypt PoW algorithm, same reward schedule, but there's a lot of changes under the hood.

    For the full Bitcoin 0.9 changelog, please see https://bitcointalk.org/index.php?topic=522014

    Please note that this is a very early release, and a full audit of the code is still in progress. The client has been hard-coded to only work with testnet for now, to avoid risks of damaging real wallets.

    Downgrading

    First and foremost, please note that downgrading from 1.7 to 1.6 is not trivial. 1.7 now uses Berkeley DB 5.1 as its default database (in place of 4.8), and as such may create database files which are incompatible with previous versions.

    Rebranding to Dogecoin Core

    Following in the footsteps of Bitcoin (Core), the Dogecoin reference client has been rebranded as "Dogecoin Core". This helps separate its identity from Dogecoin (the network).

    dogecoin-cli

    Where previously commands were sent to dogecoind by running "dogecoind ", 1.7 adopts the model from Bitcoin Core 0.9 where there is a separate "dogecoin-cli" executable which us used instead. This avoids the risk of accidentally trying to start two daemons at the same time, for example.

    Transaction malleability-related fixes

    Fixes for risk-cases involving transaction malleability have been added; this is particularly important for any merchants or exchanges using the built-in wallet system.

    Testnet

    As mentioned at the start of this document, the alpha-client is for use on the Dogecoin testnet only. This is an alternative Dogecoin blockchain which is not used for real transactions, and instead is intended for testing of experimental clients. Wallets and addresses are incompatible with the normal Dogecoin network, in order to isolate the two.

    As "test Doge" is essentially valueless, it can be acquired easily for testing, either by mining, or from a faucet such as http://testdoge.lionservers.de/

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.7.0-Alpha1-linux32.zip(8.76 MB)
    dogecoin-1.7.0-Alpha1-linux64.zip(8.59 MB)
    dogecoin-qt-1.7.0-Alpha1-win32.zip(10.71 MB)
    dogecoin-qt-1.7.0-Alpha1-win64.zip(11.37 MB)
    dogecoin.conf(84 bytes)
Owner
Dogecoin
Dogecoin
Upbit(업비트) Cryptocurrency Exchange Open API Client of Multi-Programming Language Support

Upbit Client Documents Support Upbit Client Upbit(업비트) Cryptocurrency Exchange API Client Description Upbit(업비트) Cryptocurrency Exchange Open API Clie

Yu Jhin 38 Jun 2, 2022
Monero: the secure, private, untraceable cryptocurrency

Monero: the secure, private, untraceable cryptocurrency

The Monero Project 7.2k Aug 3, 2022
NanoSwift: A Swift Library for the Nano cryptocurrency

Nano is an instant, feeless and eco-friendly cryptocurrency that is also super easy to use. This library lets you create wallets, accounts and blocks as well as manage Nano amounts, interact with a node and more.

Christian 23 Mar 1, 2022
Simple C++ implementation of a blockchain based cryptocurrency

Welcome to PandaCoin! PandaCoin is a minimalist implementation of a layer 1 cryptocurrency similar to Bitcoin. It is designed with utmost simplicity a

null 13 Jul 4, 2022
A basic C++ cryptocurrency/block-chain. Includes a basic wallet system. See README.md for all the inclusions and future additions.

Cryptocurrency Project C++ cryptocurrency/block-chain. Mostly basic blockchain for now. New Additions are in the works(see below). This file details w

null 2 Dec 23, 2021
BTCU Wallet is the original Bitcoin Ultimatum client and it builds the backbone of the network.

The concept of BTCU is similar to the concept of the second cryptocurrency by capitalization - Ethereum.

Bitcoin Ultimatum (BTCU) 31 Jul 1, 2022
Bitcoin Core integration/staging tree

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

Bitcoin 65.5k Jul 29, 2022
A high-performance distributed Bitcoin mining pool server.

Viabtc Mining Server ViaBTC Mining Server is a high-performance distributed Bitcoin mining pool server. We have made a lot of optimizations for Bitcoi

ViaBTC 91 Jul 11, 2022
Bitcoin Point of Sale

LNPoS Hardware https://shop.pimoroni.com/products/m5stack-faces-kit-pocket-computer-with-keyboard-game-calculator Installation Install Arduino IDE: ht

Arc 115 Aug 5, 2022
Bitcoin and Altcoins Publickey subtracter

keysubtracter Bitcoin and Altcoins Publickey subtracter Generate multiple but different "copies" of a publickey, Actually Added and substracted public

Luis Alberto 18 Jun 17, 2022
Bitcoin Core integration/staging tree

Bitcoin Core integration/staging tree https://bitcoincore.org For an immediately usable, binary version of the Bitcoin Core software, see https://bitc

Bitcoin Core 36 Jul 6, 2022
Brute Force Bitcoin Private keys, Public keys

Rotor-Cuda This is a modified version of KeyHunt v1.7 by kanhavishva. A lot of gratitude to all the developers whose codes has been used here. Feature

LostCoins 74 Jul 23, 2022
Onix is a decentralized blockchain project built on Bitcoin's UTXO model

What is Onix? Onix is a decentralized blockchain project built on Bitcoin's UTXO model, with support for Ethereum Virtual Machine based smart contract

Onix CryptoCurrency Development 4 Dec 16, 2021
mako - full bitcoin implementation in C

mako - full bitcoin implementation in C

Christopher Jeffrey (JJ) 528 Jul 30, 2022
Small collection of tools written in C for ECC and bitcoin

ecctools Small collection of tools written in C for ECC and bitcoin Why this programs are written in C language? Well i like C language because compil

Luis Alberto 19 Jul 27, 2022
Open-source, airgapped bitcoin hardware signer for the M5StickV.

Krux ✝ Krux is an open-source DIY hardware signer for Bitcoin that can sign for multisignature and single-key wallets. It is a low-cost airgapped devi

Jeff 42 Jul 29, 2022
FCracker is a command line tool designed to brute force encrypted files like zip, 7z, rar, pdf etc.

FCrack is a command-line tool designed to brute force encrypted files like zip, 7z, rar, pdf, gpg etc.

null 17 Apr 27, 2022
A Key Calculation Based Program For Data Confidentiality Over A Steganography-Like Technique

The Key Calculation Process : The Program Work By Calculating a Decryption Key For The Target File Based On Another File To Reproduce Again The Target

Mahmoud Osman (MLT) 17 Jul 17, 2022
Dogecoin is a cryptocurrency like Bitcoin

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

Dogecoin 14.2k Aug 6, 2022
This project shows how to interface Nokia 5110 LCD with Esp32 module to show current prices of any cryptocurrency like Bitcoin, Dogecoin, etc

ESP32 Cryptocurreny Ticker Introduction This project shows how to interface Nokia 5110 LCD with Esp32 module to show current prices of any cryptocurre

Aniket Katkar 20 Jun 16, 2022
Upbit(업비트) Cryptocurrency Exchange Open API Client of Multi-Programming Language Support

Upbit Client Documents Support Upbit Client Upbit(업비트) Cryptocurrency Exchange API Client Description Upbit(업비트) Cryptocurrency Exchange Open API Clie

Yu Jhin 38 Jun 2, 2022
Monero: the secure, private, untraceable cryptocurrency

Monero: the secure, private, untraceable cryptocurrency

The Monero Project 7.2k Aug 3, 2022
NanoSwift: A Swift Library for the Nano cryptocurrency

Nano is an instant, feeless and eco-friendly cryptocurrency that is also super easy to use. This library lets you create wallets, accounts and blocks as well as manage Nano amounts, interact with a node and more.

Christian 23 Mar 1, 2022
Simple C++ implementation of a blockchain based cryptocurrency

Welcome to PandaCoin! PandaCoin is a minimalist implementation of a layer 1 cryptocurrency similar to Bitcoin. It is designed with utmost simplicity a

null 13 Jul 4, 2022
A basic C++ cryptocurrency/block-chain. Includes a basic wallet system. See README.md for all the inclusions and future additions.

Cryptocurrency Project C++ cryptocurrency/block-chain. Mostly basic blockchain for now. New Additions are in the works(see below). This file details w

null 2 Dec 23, 2021
Monero: the secure, private, untraceable cryptocurrency

Monero GUI Copyright (c) 2014-2019, The Monero Project Table of Contents Development resources Vulnerability response Introduction About this project

The Monero Project 1.2k Jul 27, 2022
BTCU Wallet is the original Bitcoin Ultimatum client and it builds the backbone of the network.

The concept of BTCU is similar to the concept of the second cryptocurrency by capitalization - Ethereum.

Bitcoin Ultimatum (BTCU) 31 Jul 1, 2022
Bitcoin Core integration/staging tree

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

Bitcoin 65.5k Jul 29, 2022
The Game Boy ROM of the Game Boy bitcoin miner!

game-boy-bitcoin-miner The Game Boy ROM of the Game Boy bitcoin miner! To build this, currently this patch needs to be applied to GBDK: https://gist.g

Ghidra Ninja 79 Jul 17, 2022