Skip to content

Releases: decred/decred-binaries

v1.3.0

21 Sep 19:46
@dajohi dajohi
v1.3.0
fe826d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.3.0

2018-09-21

Install

To install the command line tools, please see dcrinstaller.

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or decrediton Windows.

See manifest-v1.3.0.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

Contents

dcrd v1.3.0

This release of dcrd contains significant performance enhancements for startup speed, validation, and network operations that directly benefit lightweight clients, such as SPV (Simplified Payment Verification) wallets, a policy change to reduce the default minimum transaction fee rate, a new public test network version, removal of bloom filter support, infrastructure improvements, and other quality assurance changes.

It is highly recommended that everyone upgrade to this latest release as it contains many important scalability improvements and is required to be able to use the new public test network.

Downgrade Warning

The database format in v1.3.0 is not compatible with previous versions of the software. This only affects downgrades as users upgrading from previous versions will see a one time database migration.

Once this migration has been completed, it will no longer be possible to downgrade to a previous version of the software without having to delete the database and redownload the chain.

Notable Changes

Reduction of Default Minimum Transaction Fee Rate Policy

The default setting for the policy which specifies the minimum transaction fee rate that will be accepted and relayed to the rest of the network has been reduced to 0.0001 DCR/kB (10,000 atoms/kB) from the previous value of 0.001 DCR/kB (100,000 atoms/kB).

Transactions should not attempt to use the reduced fee rate until the majority of the network has upgraded to this release as otherwise the transactions will likely have issues relaying through the network since old nodes that have not updated their policy will reject them due to not paying a high enough fee.

Several Speed Optimizations

This release contains several enhancements to improve speed for startup, the initial sync process, validation, and network operations.

In order to achieve these speedups, there is a one time database migration, as previously mentioned, that typically only takes a few seconds to complete on most hardware.

Further Improved Startup Speed

The startup time has been improved by roughly 2x on both slower hard disk drives (HDDs) and solid state drives (SSDs) as compared to v1.2.0.

Significantly Faster Network Operations

The ability to serve information to other peers on the network has received several optimizations which, in addition to generally improving the overall scalability and throughput of the network, also directly benefits SPV (Simplified Payment Verification) clients by delivering the block headers they require roughly 3x to 4x faster.

Signature Hash Calculation Optimization

Part of validating that transactions are only spending coins that the owner has authorized involves ensuring the validity of cryptographic signatures. This release provides a speedup of about 75% to a key portion of that validation which results in a roughly 20% faster initial sync process.

Bloom Filters Removal

Bloom filters were deprecated as of the last release in favor of the more recent privacy-preserving GCS committed filters. Consequently, this release removes support for bloom filters completely. There are no known clients which use bloom filters, however, if there are any unknown clients which use them, those clients will need to be updated to use the GCS committed filters accordingly.

Public Test Network Version 3

The public test network has been reset and bumped to version 3. All of the new consensus rules voted in by version 2 of the public test network have been retained and are therefore active on the new version 3 test network without having to vote them in again.

Changelog

All commits since the last release may be viewed on GitHub here.

Protocol and network:

Transaction relay (memory pool):

RPC:

Read more

Contributors

kyleFirethought
Loading

v1.3.0-rc2

04 Sep 20:14
@dajohi dajohi
v1.3.0-rc2
fe826d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.3.0-rc2 Pre-release
Pre-release

dcrd v1.3.0-rc2

This release of dcrd contains significant performance enhancements for startup speed, validation, and network operations that directly benefit lightweight clients, such as SPV (Simplified Payment Verification) wallets, a policy change to reduce the default minimum transaction fee rate, a new public test network version, removal of bloom filter support, infrastructure improvements, and other quality assurance changes.

It is highly recommended that everyone upgrade to this latest release as it contains many important scalability improvements and is required to be able to use the new public test network.

Downgrade Warning

The database format in v1.3.0 is not compatible with previous versions of the software. This only affects downgrades as users upgrading from previous versions will see a one time database migration.

Once this migration has been completed, it will no longer be possible to downgrade to a previous version of the software without having to delete the database and redownload the chain.

Notable Changes

Reduction of Default Minimum Transaction Fee Rate Policy

The default setting for the policy which specifies the minimum transaction fee rate that will be accepted and relayed to the rest of the network has been reduced to 0.0001 DCR/kB (10,000 atoms/kB) from the previous value of 0.001 DCR/kB (100,000 atoms/kB).

Transactions should not attempt to use the reduced fee rate until the majority of the network has upgraded to this release as otherwise the transactions will likely have issues relaying through the network since old nodes that have not updated their policy will reject them due to not paying a high enough fee.

Several Speed Optimizations

This release contains several enhancements to improve speed for startup, the initial sync process, validation, and network operations.

In order to achieve these speedups, there is a one time database migration, as previously mentioned, that typically only takes a few seconds to complete on most hardware.

Further Improved Startup Speed

The startup time has been improved by roughly 2x on both slower hard disk drives (HDDs) and solid state drives (SSDs) as compared to v1.2.0.

Significantly Faster Network Operations

The ability to serve information to other peers on the network has received several optimizations which, in addition to generally improving the overall scalability and throughput of the network, also directly benefits SPV (Simplified Payment Verification) clients by delivering the block headers they require roughly 3x to 4x faster.

Signature Hash Calculation Optimization

Part of validating that transactions are only spending coins that the owner has authorized involves ensuring the validity of cryptographic signatures. This release provides a speedup of about 75% to a key portion of that validation which results in a roughly 20% faster initial sync process.

Bloom Filters Removal

Bloom filters were deprecated as of the last release in favor of the more recent privacy-preserving GCS committed filters. Consequently, this release removes support for bloom filters completely. There are no known clients which use bloom filters, however, if there are any unknown clients which use them, those clients will need to be updated to use the GCS committed filters accordingly.

Public Test Network Version 3

The public test network has been reset and bumped to version 3. All of the new consensus rules voted in by version 2 of the public test network have been retained and are therefore active on the new version 3 test network without having to vote them in again.

Changelog

All commits since the last release may be viewed on GitHub here.

Protocol and network:

Transaction relay (memory pool):

RPC:

dcrd command-line flags and configuration:

dcrctl utility changes:

Documentation:

Read more
Loading

v1.3.0-rc1

10 Aug 20:15
@dajohi dajohi
v1.3.0-rc1
fe826d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.3.0-rc1 Pre-release
Pre-release

2018-08-10

Install

To install the command line tools, please see dcrinstaller.

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or decrediton Windows.

See manifest-v1.3.0-rc1.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

Contents

dcrd v1.3.0-rc1

This release of dcrd contains significant performance enhancements for startup speed, validation, and network operations that directly benefit lightweight clients, such as SPV (Simplified Payment Verification) wallets, a policy change to reduce the default minimum transaction fee rate, a new public test network version, removal of bloom filter support, infrastructure improvements, and other quality assurance changes.

It is highly recommended that everyone upgrade to this latest release as it contains many important scalability improvements and is required to be able to use the new public test network.

Downgrade Warning

The database format in v1.3.0 is not compatible with previous versions of the software. This only affects downgrades as users upgrading from previous versions will see a one time database migration.

Once this migration has been completed, it will no longer be possible to downgrade to a previous version of the software without having to delete the database and redownload the chain.

Notable Changes

Reduction of Default Minimum Transaction Fee Rate Policy

The default setting for the policy which specifies the minimum transaction fee rate that will be accepted and relayed to the rest of the network has been reduced to 0.0001 DCR/kB (10,000 atoms/kB) from the previous value of 0.001 DCR/kB (100,000 atoms/kB).

Transactions should not attempt to use the reduced fee rate until the majority of the network has upgraded to this release as otherwise the transactions will likely have issues relaying through the network since old nodes that have not updated their policy will reject them due to not paying a high enough fee.

Several Speed Optimizations

This release contains several enhancements to improve speed for startup, the initial sync process, validation, and network operations.

In order to achieve these speedups, there is a one time database migration, as previously mentioned, that typically only takes a few seconds to complete on most hardware.

Further Improved Startup Speed

The startup time has been improved by roughly 2x on both slower hard disk drives (HDDs) and solid state drives (SSDs) as compared to v1.2.0.

Significantly Faster Network Operations

The ability to serve information to other peers on the network has received several optimizations which, in addition to generally improving the overall scalability and throughput of the network, also directly benefits SPV (Simplified Payment Verification) clients by delivering the block headers they require roughly 3x to 4x faster.

Signature Hash Calculation Optimization

Part of validating that transactions are only spending coins that the owner has authorized involves ensuring the validity of cryptographic signatures. This release provides a speedup of about 75% to a key portion of that validation which results in a roughly 20% faster initial sync process.

Bloom Filters Removal

Bloom filters were deprecated as of the last release in favor of the more recent privacy-preserving GCS committed filters. Consequently, this release removes support for bloom filters completely. There are no known clients which use bloom filters, however, if there are any unknown clients which use them, those clients will need to be updated to use the GCS committed filters accordingly.

Public Test Network Version 3

The public test network has been reset and bumped to version 3. All of the new consensus rules voted in by version 2 of the public test network have been retained and are therefore active on the new version 3 test network without having to vote them in again.

Changelog

All commits since the last release may be viewed on GitHub here.

Protocol and network:

Transaction relay (memory pool):

RPC:

Read more

Contributors

kyleFirethought
Loading

v1.2.1

01 May 19:43
@dajohi dajohi
v1.2.1
fe826d0
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.2.1

2018-05-01

Install

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or decrediton Windows.

See manifest-decrediton-v1.2.1.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

decrediton v1.2.1

This decrediton patch release covers a few commonly reported issues shortly after v1.2.0 was released. Most importantly this fixes an issue causing balances to show 0 after new blocks connect.

Bug Fixes

  • Fix an issue that was causing non-dirs to be discovered as valid legacy wallets. This would cause "config.json" incompletely setup wallet on first load of v1.2.0

  • Fix balance showing 0 after ticket/votes calculated for maturity.

  • Seed pasting was not showing errors and would just blank out the words. Now an error is shown when that occurs.

  • Fix various PT-Br translation errors.

  • Due to dcrd v1.2.0 database upgrade, users would be shown "Waiting for RPC..." for a very long time with no other information. Now the first lines of both dcrd and dcrwallet logs are shown to hopefully give the user more information about the current state of the daemon upgrade.

Changelog

All commits since the last release may be viewed on GitHub here.

Loading

v1.2.0

26 Apr 17:07
@dajohi dajohi
v1.2.0
6415bd7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.2.0

2018-04-26

Install

To install the command line tools, please see dcrinstaller.

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or decrediton Windows.

See manifest-v1.2.0.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

Contents

dcrd v1.2.0

This release of dcrd contains significant performance enhancements, infrastructure improvements, improved access to chain-related information for providing better SPV (Simplified Payment Verification) support, and other quality assurance changes.

A significant amount of infrastructure work has also been done this release cycle towards being able to support several planned scalability optimizations.

Downgrade Warning

The database format in v1.2.0 is not compatible with previous versions of the software. This only affects downgrades as users upgrading from previous versions will see a one time database migration.

Once this migration has been completed, it will no longer be possible to downgrade to a previous version of the software without having to delete the database and redownload the chain.

Notable Changes

Significantly Faster Startup

The startup time has been improved by roughly 17x on slower hard disk drives (HDDs) and 8x on solid state drives (SSDs).

In order to achieve these speedups, there is a one time database migration, as previously mentioned, that will likely take a while to complete (typically around 5 to 6 minutes on HDDs and 2 to 3 minutes on SSDs).

Support For DNS Seed Filtering

In order to better support the forthcoming SPV wallets, support for finding other peers based upon their enabled services has been added. This is useful for both SPV wallets and full nodes since SPV wallets will require access to full nodes in order to retrieve the necessary proofs and full nodes are generally not interested in making outgoing connections to SPV wallets.

Committed Filters

With the intention of supporting light clients, such as SPV wallets, in a privacy-preserving way while still minimizing the amount of data that needs to be downloaded, this release adds support for committed filters. A committed filter is a combination of a probalistic data structure that is used to test whether an element is a member of a set with a predetermined collision probability along with a commitment by consensus-validating full nodes to that data.

A committed filter is created for every block which allows light clients to download the filters and match against them locally rather than uploading personal data to other nodes.

A new service flag is also provided to allow clients to discover nodes that provide access to filters.

There is a one time database update to build and store the filters for all existing historical blocks which will likely take a while to complete (typically around 2 to 3 minutes on HDDs and 1 to 1.5 minutes on SSDs).

Updated Atomic Swap Contracts

The standard checks for atomic swap contracts have been updated to ensure the contracts enforce the secret size for safer support between chains with disparate script rules.

RPC Server Changes

New getchaintips RPC

A new RPC named getchaintips has been added which allows callers to query information about the status of known side chains and their branch lengths. It currently only provides support for side chains that have been seen while the current instance of the process is running. This will be further improved in future releases.

Changelog

All commits since the last release may be viewed on GitHub here.

Protocol and network:

Transaction relay (memory pool):

RPC:

dcrd command-line flags and configuration:

checkdevpremine utility changes:

Documentation:

Developer-related package changes:

  • chaingen: Add revocation...
Read more
Loading

v1.2.0-rc2

16 Apr 21:36
@dajohi dajohi
v1.2.0-rc2
6415bd7
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
Compare
Choose a tag to compare
v1.2.0-rc2 Pre-release
Pre-release 
v1.2.0-rc1 (#72)
Loading

v1.2.0-rc1

03 Apr 23:28
@dajohi dajohi
v1.2.0-rc1
d407601
Compare
Choose a tag to compare
v1.2.0-rc1 Pre-release
Pre-release 
v1.1.3 - decrediton (#69)
Loading

v1.1.3

21 Dec 17:26
@dajohi dajohi
v1.1.3
355c28f
Compare
Choose a tag to compare
v1.1.3

2017-12-21

Install

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or decrediton Windows.

See manifest-decrediton-v1.1.3.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

decrediton v1.1.3

This decrediton patch release covers a few commonly reported issues shortly after v1.1.2 was released. Most importantly this fixes a random issue on the Windows version that was causing an unavoidable crash on startup.

Bug Fixes

  • Rollback electron-store/conf version to avoid asar/json Windows issue.

  • Remove "Revoke tickets..." alert from Overview. Due to a deeper issue in dcrwallet the notification whether there are tickets to revoke is being incorrectly announced. Until that fix is available, it seems better to avoid showing the alert which confuses the user.

  • Fix errors on adding Stakepool API. On failed Stakepool API requests, the Stakey bounce animation would remain and the user would be unable to proceed.

  • Fix sorting of voted/revoked tickets in My Tickets.

  • Fix Account Key display

  • Fix issue with using "Enter" to complete any Get Started form. Doing so would previously make Decrediton shut down instead of submitting the action.

  • Hide Paginator when <= 1 page

Changelog

All commits since the last release may be viewed on GitHub here.

Loading

v1.1.2

15 Dec 16:03
@dajohi dajohi
v1.1.2
de399cc
Compare
Choose a tag to compare
v1.1.2

2017-12-14

Install

To install the command line tools, please see dcrinstaller.

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or
decrediton Windows.

See manifest-v1.1.2.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

Contents

dcrd v1.1.2

This release of dcrd primarily contains performance enhancements, infrastructure improvements, and other quality assurance changes.

While it is not visible in this release, significant infrastructure work has also been done this release cycle towards porting the Lightning Network (LN) daemon which will ultimately allow LN payments to be backed by Decred.

Notable Changes

Faster Block Validation

A significant portion of block validation involves handling the stake tickets which form an integral part of Decred's hybrid proof-of-work and proof-of-stake system. The code which handles this portion of validation has been significantly optimized in this release such that overall block validation is up to approximately 3 times faster depending on the specific underlying hardware configuration. This also has a noticeable impact on the speed of the initial block download process as well as how quickly votes for winning tickets are submitted to the network.

Data Carrier Transaction Standardness Policy

The standard policy for transaction relay of data carrier transaction outputs has been modified to support canonically-encoded small data pushes. These outputs are also known as OP_RETURN or nulldata outputs. In particular, single byte small integers data pushes (0-16) are now supported.

Changelog

All commits since the last release may be viewed on GitHub here.

Protocol and network:

Transaction relay (memory pool):

RPC:

dcrd command-line flags:

Documentation

Developer-related package changes:

Testing and Quality Assurance:

Misc:

Code Contributors (alphabetical order):

  • Alex Yocom-Piatt
  • Dave Collins
  • David Hill
  • detailyang
  • Donald Adu-Poku
  • Federico Gimenez
  • Jason Zavaglia
  • John C. Vernaleo
  • Jonathan Chappelow
  • Jolan Luff
  • Josh Rickmar
  • Maninder Lall
  • Matheus Degiovani
  • Nicola Larosa
  • Samarth Hattangady
  • Ugwueze Onyekachi Michael

dcrwallet v1.1.2

This release focuses on internal improvements to the wallet to increase code quality, thereby making it easier to add optional support for SPV syncing in a future release. As always, it also comes with bug fixes, new features and other improvements, which are detailed below.

Bug fixes

  • Vote transactions that become invalid when the main chain tip block changes are now removed from the wallet. This allows the invalid vote to be double spent by another vote later if the ticket is picked again on a different chain.

  • Ticket buyer now attempts to avoid purchasing tickets for old blocks if it is enabled while the wallet is catching up to the network.

  • The application now exits cleanly if an interrupt signal (e.g. ^C or SIGINT) is received while at a prompt (such as during wallet creation, or with --promptpass) instead of hanging at the prompt.

  • The application no longer refuses to start when duplicate RPC listener addresses which bind to port 0 are specified in the config.

  • The listtransactions JSON-RPC has been fixed so that the order and amount values of all results match the results returned by Bitcoin Core.

  • The gettransaction JSON-RPC has been fixed to return fees as negative numbers instead of positive, which matches the behavior of Bitcoin Core.

New features

  • A new gRPC method WalletService.GetTickets has been introduced to return all wallet ticket purchases between a block...
Read more
Loading

v1.1.1

29 Sep 21:32
@dajohi dajohi
v1.1.1
879921c
Compare
Choose a tag to compare
v1.1.1

Install

To install decrediton download, uncompress, and run decrediton Linux or decrediton OSX or
decrediton Windows.

See manifest-decrediton-v1.1.1.txt, and the package specific manifest files for sha256 sums and the associated .asc files to confirm those shas.

See README.md for more info on verifying the files.

decrediton v1.1.1

This patch release primarily fixes Windows version from not allowing dcrd and dcrwallet to be shutdown gracefully. Upon decrediton close, shutdown requests are given to the 2 child-processes to cleanly shutdown now.

This commit also marks the first unit test of the React components we are including. In the upcoming releases we plan on expanding test coverage to hopefully ensure that each release is as bug free as possible.

We can now get transaction details for pending transactions and the transaction notifactions are clickable to see that details page.

App versions are now pulled directly from the binaries themselves instead of any hardcoding so users can be assured they are running specific versions of dcrd and dcrwallet underneath.

Bug Fixes

  • Disable rescan, add ApiKey and Import Script buttons if there is an outstanding rescan request processing. Otherwise you can issue multiple requests at the same time and it will lead to unsightly UX.

  • Fix Stakepools Overview link that was resulting in a 404 previously.

  • Add total subsidy to the tickets page.

  • Fix Add Stakepool Button in Stakepool Config page.

Changelog

All commits since the last release may be viewed on GitHub here.

Loading