Dogecoin is a cryptocurrency like Bitcoin

Related tags

dogecoin
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
  • 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
  • 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
  • Major issue causing lots of Orphaned Blocks due to compiling with boost v1.55

    Major issue causing lots of Orphaned Blocks due to compiling with boost v1.55

    here is the bug, the result is transactions taking very long to verify (even with a very well connected client) and a major increase in orphaned blocks since version 1.5 of dogecoin client, below is mostly a copy and paste but it seemed critical enough that i wanted to be sure it was brought to the attention of the dogecoin developers asap:

    (paste) There's a bug with the previous version of Litecoin where the client will randomly stop syncing. This results in your node basically being down until you restart the client. The way to know this is occurring is to check the resource monitor(go to task manager->performance tab). If Dogecoin isn't sending or receiving any data, it's likely down. When you restart the client, you will be several hours behind(whenever it stopped syncing) This was fixed in the newest version of Litecoin, but showed up in the 2nd most recent version(Dogecoin is based on Litecoin, and updating to the more recent codebase of Litecoin likely picked up the issue). This bug weakens the Dogecoin network a bit and can be very annoying. edit: If you aren't seeing transactions show up after you know they've been sent to you(IE mining pool withdrawal), then you are likely affected and need to simply restart the dogecoin-QT client to double check.

    This is due to the "boost" library used when building. We were previously on Boost 1.54 I've recompiled the binaries and you can download the latest (fixed) (/end paste)

    the issue is described in detail along with some user created patches / fixes:

    http://www.reddit.com/r/dogecoin/comments/1wfj2t/dogecoin_15_suffers_from_an_old_litecoin_bug/

    as you can see in these graphs the increase in orphaned blocks since version 1.5 release: http://bitinfocharts.com/comparison/orphaned-btc-ltc-ppc-doge-nmc.html

    opened by jo2jo 49
  • How to redeem doge coin back from output with private key

    How to redeem doge coin back from output with private key

    Hi, please help me to redeem the coins back. I have windows 10 (64bit) with Dogecoin Core QT 1.10 wallet After I made 2 transactions ( wallet was not entirely completed to sync ) 6 and 100000, wallet made other 2 transactions for no reason https://dogechain.info/address/DQeNuxSRGCHFLXGZG5nzo1RWBD9RnTW8cP transaction https://dogechain.info/tx/6f11ae8637c6b4232aee40e0a0f31d605c54c393ab53007fa744a97f8e2747b3 Amount I sent only 100000 6f11ae8637c6b4232aee40e0a0f31d605c54c393ab53007fa744a97f8e2747b3-001 How I got other amount-381,251.01927000 sent ?
    Please help me to retrieve it. Thank you

    PS: I Synchronized it completely and than re-index it with no luck to show balance correct. I did not do anything with wallet.dat except encrypted it with new passphrase since I restored it from unencrypted usb flash which I kept it as a back up. It is synchronized fully I do no have such address DF61X3Gn1H8zVeV2QoERgprKAivufsVkA4 after I did dumpwallet and printed to find it. This is really weird. Any other suggestions to reedem it? Thank you.

    opened by doge0901 41
  • rounding error in dogecoin value?

    rounding error in dogecoin value?

    I just tried creating a raw transaction that sends a single large input to a new address with 0 fee. It was rejected with:

    error: {"code":-22,"message":"TX rejected"}
    

    but the transaction was small enough, and with big enough value to qualify as free.

    Further investingation showed me that this line was failing:

        if (nFees < tx.GetMinFee(1000, true, GMF_RELAY))
            return error("CTxMemPool::accept() : not enough fees");
    

    because nFees was -1 and GetMinFee() was returning 0.

    Why did it think the included fee was negative? It turns out the raw transaction wasn't specifying the output value I asked for. Here's a minimal example:

    $ dogecoind decderawtransaction $(dogecoind createrawtransaction '[]' '{"DBwb7y87zGnvmZgnxXdxoVwjbevzNrpVtr":50000000.00000001}') | grep value
            "value" : 50000000.00000002,
    

    I ask for a single output with value 50000000.00000001, but get a single output one satoshi bigger than that. And so the fee is -1 satoshi.

    I thought dogecoind used integers for coin values, so am a little confused how this can be happening. Trying to send 1 satoshi more than 10, 20, 30, or 40 million doges works fine. It's only 50 million where the problem starts happening.

    bug 
    opened by dooglus 39
  • Reintroduce the cap

    Reintroduce the cap

    In light of recent events, this is a feature request on behalf of many people around the community.

    As things stand, the only thing that is keeping dogecoin from reaching extraordinary heights is the lack, or rather, deactivation of the cap that was originally imposed on the network.

    Dollar as a modern fiat currency, although similarly uncapped, is nonetheless periodically regulated and hence doesn't suffer the same consequences. Dogecoin on the other hand, is network-regulated and unfortunately its growth is way beyond its legitimate use-cases, and no I kid you not, dogecoin over the years has established many legitimate use-cases, thus, with all that taken into account, everyone might agree a new consensus should be in order. Let's simply reintroduce the cap and let dogecoin gain the glory that it deserves.

    opened by j4hangir 37
  • Compiled on centos

    Compiled on centos

    dogecoin-core can't compiled on centos.there are anyone to install it on centos6.5?

    question 
    opened by strengthening 34
  • Much improved logo. So moon.

    Much improved logo. So moon.

    Taken here : http://www.reddit.com/r/dogecoin/comments/1wph54/so_i_went_and_did_a_new_logo_for_our_beloved/ Direct URL : http://i.imgur.com/3Ptyvlw.png All credits go to /u/CitizenOlympic.

    opened by libcg 30
  • make command not working in Mac OS

    make command not working in Mac OS

    dogecoin % make

    make: *** No targets specified and no makefile found. Stop.

    Clone the dogecoin source code and cd into dogecoin

    git clone https://github.com/dogecoin/dogecoin cd dogecoin Build dogecoin:

    Configure and build the headless dogecoin binaries as well as the GUI (if Qt is found).

    You can disable the GUI build by passing --without-gui to configure.

    ./autogen.sh ./configure make

    I have used this steps

    make command not working ,I have try with macOS terminal.

    opened by jesuasir007 1
  • Refactor: fix typo in validation.cpp

    Refactor: fix typo in validation.cpp

    inadvertantly -> inadvertently

    opened by eltociear 0
  • Qt Add GUI wif import dialog

    Qt Add GUI wif import dialog

    Addresses #1808.

    opened by chromatic 0
  • need more pair for 1.14.3

    need more pair for 1.14.3

    hi, im looking for list of pair for 1.14.3

    my core wallet sync very slowly and my pair node have 20k ms

    anyone have à pair list ?

    opened by VeilleurTrytoFix 1
  • Can the DogeCoind work with a miner directly?

    Can the DogeCoind work with a miner directly?

    Hi,

    Can the DogeCoind work with a miner in solo? I want to mine the DogeCoin.

    My platform are: Ubuntu RTX 1080 CUDA 11.2

    If you can give me some help, I will appreciate you in DogeCoin.

    Thanks!

    Jacky Wang

    opened by jackynanshan 5
  • BUILDING error windows 64:

    BUILDING error windows 64: " configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality) "

    Describe the issue

    I get following error when building for win 64 after issuing this command: CONFIG_SITE=$PWD/depends/i686-w64-mingw32/share/config.site ./configure --prefix=/ All previous Building steps went without a hitch.

    output: ... checking for mallopt M_ARENA_MAX... yes checking for visibility attribute... yes checking for Berkeley DB C++ headers... no configure: error: libdb_cxx headers missing, Dogecoin Core requires this library for wallet functionality (--disable-wallet to disable wallet functionality)

    opened by fritol 1
  • 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/

    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.

    opened by GiverofMemory 33
  • 无法发送

    无法发送

    Screenshot_2021-04-22-20-23-14-563_de langerhans wallet

    opened by erhuodoudou 7
  • Trying to recover old wallet.dat

    Trying to recover old wallet.dat

    This issue tracker is only for technical issues related to Dogecoin Core.

    For general questions about Dogecoin please use one of the various communities, e.g. Reddit, IRC, Discord, etc.

    Describe the issue

    I got my old wallet.dat from an old hard drive from 2017. Whenever I try to have doge coin core use it, the wallet gets overwritten and has a new creation date, a balance of 0, and no transaction history. Is there a solution to this, is there a way to dump my keys from windows cmd? If it were encrypted, shouldn't prompt the passphrase (not sure if it is but I'm pretty sure I have the pass phrase)

    Can you reliably reproduce the issue?

    If so, please list the steps to reproduce below:

    1. Open folder of dogecoin core.
    2. Delete wallet.dat and paste old wallet.dat into it.
    3. Run dogecoin core.

    Expected behaviour

    Tell us what should happen It should load up the wallet

    Actual behaviour

    Tell us what happens instead I replaces the wallet with a fresh wallet.

    Screenshots.

    If the issue is related to the GUI, screenshots can be added to this issue via drag & drop.

    What version of Dogecoin Core are you using?

    List the version number/commit ID, and if it is an official binary, self compiled or a distribution package such as PPA. 1.14.2

    Machine specs:

    • OS: Windows
    • CPU: Intel i5 4690k
    • RAM: 16g
    • Disk size: 2 tb
    • Disk Type (HD/SDD): HD

    Any extra information that might be useful in the debugging process.

    This is normally the contents of a debug.log or config.log file. Raw text or a link to a pastebin type site are preferred.

    opened by SkivvyNivvy 1
  • Fixed typos and enhanced messages for Polish translation

    Fixed typos and enhanced messages for Polish translation

    Fixed multiple typos (duplicated spaces, misspelled words, etc.) and introduced new messages which were previously not translated to Polish. Also removed couple of redundant numerusforms.

    opened by pmzajaczkowski 0
Releases(v1.14.3)
  • 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.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-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.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)
  • 1.6(Mar 13, 2014)

    Note: This is a mandatory update as it involves a hard fork of the network. Please make sure you are running 1.6 to ensure that you're on the correct blockchain and not at risk of losing your DOGE

    As per block 145k, the network will hardfork to adopt a new difficulty retargeting algorithm.

    Update highlights:

    1. No longer a random block reward - we now only have static blocks. The current reward will be 250,000 Doge per block, with the halvening dropping us to 125,000 Doge per block, etc etc. This will prevent block cherry-picking; as we're seeing at the moment, with our community pools only seeing 100-200k blocks, while the multi's gaming the system are enjoying 300-500k blocks. From the 1.6 update, all blocks will be completely even.
    2. The DigiShield difficulty algorithm: again, developed and contributed by the very clever folks at reddit.com/r/DigiByte , this allows for rapid block retarget times, and rapid recovery from multipools suddenly hitting the network; meaning that our miners will no longer suffer from extremely long block times if a Multipool does decide to jump on board. This new algorithm will retarget our block times much faster - ensuring the hard-mining shibe is not left holding the bag after the multipool ransack.
    3. Coins mined must mature for 4 hours (previously 30 minutes) before being spent. This is a precautionary measure, to give everyone more time to communicate following any future fork of the network.

    For a complete history of all commits, please check the repository history. A big shout out to everyone who made this release possible, and happy digging shibes! :)

    Source code(tar.gz)
    Source code(zip)
    dogecoin-1.6.0.0-win32-setup.exe(7.68 MB)
    dogecoin-qt-1_6_0-mac.zip(12.45 MB)
    dogecoin-qt-1_6_0-win.zip(9.47 MB)
  • 1.5.2(Feb 17, 2014)

  • 1.5.1(Feb 8, 2014)

    We're happy to announce the release of Dogecoin version 1.5.1!

    This release incorporates a range of updates from community contributers, some much needed bug fixes, plus some cool treats brought down-stream from the recent Bitcoin 0.9 release candidate.

    Thanks to everyone who helped make this release possible, the entire community appreciates it. We recommend all users update to the latest version and please report any issues you may encounter. As always, backup your wallet.dat file before updating (just to be safe).

    Release highlights:

    • Switched to Boost 1.55 to fix network connectivity issues on Windows
    • Removal of reliance on IRC for discovering nodes
    • Support for URL protocol, eg. dogecoin:addr?amount=xxx&<additional_parameters> (see Bitcoin’s implementation)
    • Ability to automatically look up transactions on Dogechain from your client
    • Working Windows setup script and installer
    • Opt-in debug logging via -debuglog (to save disk space and stop constant writing)
    • Fixed Mac Splashscreen’s greedy desktop behavior
    • Reimplemented testnet, fixing RPC crash due to no genesis block being present
    • Allow user to load any wallet from data directory specified using -wallet=mywallet.dat
    • Updated to LevelDB 1.15 to address blockchain database corruption issues
    • Allow user to send change only to specified address(es) using -change=
      (one -change parameter per address)
    • Fixed RPC difficulty look up

    Enjoy!

    Source code(tar.gz)
    Source code(zip)
    dogecoin-qt-1_5_1-mac.zip(12.46 MB)
    dogecoin-qt-1_5_1-win-setup.exe(7.71 MB)
    dogecoin-qt-1_5_1-win.zip(9.49 MB)
Owner
Dogecoin
Dogecoin
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 51.1k Mar 29, 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) 30 Apr 27, 2021
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 36 Apr 2, 2021
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 22 Feb 27, 2021
Monero: the secure, private, untraceable cryptocurrency

Monero: the secure, private, untraceable cryptocurrency

The Monero Project 5.6k Mar 28, 2021
SHA256 Compute Shader (Kernel) Written in Rust

SHA256 Compute Shader (Kernel) Written in Rust ... with application to Validating the Bitcoin Blockchain Abstract The project consists of two primary

Daniel 26 Apr 28, 2021
Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies.

Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions.

Nano 3k Mar 28, 2021
Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies.

Nano is a digital payment protocol designed to be accessible and lightweight, with a focus on removing inefficiencies present in other cryptocurrencies. With ultrafast transactions and zero fees on a secure, green and decentralized network, this makes Nano ideal for everyday transactions.

Nano 3.1k May 5, 2021
:lock: Don't use this repo, use the new monorepo instead:

trezor-crypto Heavily optimized cryptography algorithms for embedded devices. These include: AES/Rijndael encryption/decryption Big Number (256 bit) A

TREZOR 458 Feb 15, 2021
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 11 Apr 24, 2021
free C++ class library of cryptographic schemes

Crypto++: free C++ Class Library of Cryptographic Schemes Version 8.4 - TBD Crypto++ Library is a free C++ class library of cryptographic schemes. Cu

null 2.7k Feb 19, 2021
Tink is a multi-language, cross-platform, open source library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse.

Tink A multi-language, cross-platform library that provides cryptographic APIs that are secure, easy to use correctly, and hard(er) to misuse. Ubuntu

Google 11.1k Feb 19, 2021
Ncurses TCP Chat

NCURSES Encrypted TCP Chat This is an encrypted chat via the command line! It was done using ncurses to build the whole user interface. I wanted to do

Edgar Hernandez 47 Mar 27, 2021
Easy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.

Themis provides strong, usable cryptography for busy people General purpose cryptographic library for storage and messaging for iOS (Swift, Obj-C), An

Cossack Labs 1.2k Feb 18, 2021