@dajohi dajohi released this Sep 21, 2018

Assets 18

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:

dcrd command-line flags and configuration:

dcrctl utility changes:

Documentation:

Developer-related package and module changes:

Testing and Quality Assurance:

Misc:

Code Contributors (alphabetical order):

  • Dave Collins
  • David Hill
  • Dmitry Fedorov
  • Donald Adu-Poku
  • harzo
  • hypernoob
  • J Fixby
  • Jonathan Chappelow
  • Josh Rickmar
  • Markus Richter
  • matadormel
  • Matheus Degiovani
  • Michael Eze
  • Orthomind
  • Shuai Qi
  • Tibor Bősze
  • Victor Oliveira
Pre-release
Pre-release

@dajohi dajohi released this Sep 4, 2018

Assets 18

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:

Developer-related package and module changes:

Testing and Quality Assurance:

Misc:

Code Contributors (alphabetical order):

  • Dave Collins
  • David Hill
  • Dmitry Fedorov
  • Donald Adu-Poku
  • harzo
  • hypernoob
  • J Fixby
  • Jonathan Chappelow
  • Josh Rickmar
  • Markus Richter
  • matadormel
  • Matheus Degiovani
  • Michael Eze
  • Orthomind
  • Shuai Qi
  • Tibor Bősze
  • Victor Oliveira
Pre-release
Pre-release

@dajohi dajohi released this Aug 10, 2018

Assets 18

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:

dcrd command-line flags and configuration:

dcrctl utility changes:

Documentation:

Developer-related package changes:

Testing and Quality Assurance:

Misc:

Code Contributors (alphabetical order):

  • Dave Collins
  • David Hill
  • Dmitry Fedorov
  • Donald Adu-Poku
  • harzo
  • hypernoob
  • J Fixby
  • Jonathan Chappelow
  • Josh Rickmar
  • Markus Richter
  • matadormel
  • Matheus Degiovani
  • Michael Eze
  • Orthomind
  • Shuai Qi
  • Tibor Bősze
  • Victor Oliveira

dcrwallet v1.3.0-rc1

This release focuses on bringing initial simplified payment verification (SPV)
and committed filter (CF) support to dcrwallet as an optional, experimental
synchronization mode. As usual, the release also contains various other
improvements and bug fixes, iterated below.

This release contains a database upgrade and once upgraded it is not possible to
downgrade to previous wallet releases without performing a seed restore with the
old version.

Bug fixes

  • When code executing under a database transaction panics, the transaction is
    now rolled back. Closing the transaction avoids a deadlock when closing the
    database in the case that the panic is recovered instead of crashing the
    process.

  • Deleting private keys from the database no longer modifies the database with
    an active bucket cursor. Doing so is unsafe and has been the cause of
    database corruption in the past.

  • The JSON-RPC method version no longer panics dereferencing a nil dcrd RPC
    client when one does not exist or has not been associated with the server.

  • Callers of an internal method to return unencrypted scripts have been fixed
    for a breaking API change in the case that the script was not present. This
    subsequently fixes synchronization from exiting prematurely when various
    scripts were not recorded.

  • The JSON-RPC method signrawtransaction has been fixed to avoid a panic in
    cases where an unknown input must have been fetched from dcrd, and the input
    is already spent in the main chain.

  • Fee estimation when spending a P2SH output has been fixed by considering the
    nested script length instead of using the same size estimation performed when
    spending a P2PKH output.

  • gRPC transaction notifications now handle the case of a transaction being
    invalidated by voters in the next block. An invalidated transaction is
    considered to have -1 confirmations, but in most cases the transaction (if not
    double spent) will reappear in mempool with a confirmation count of 0.

New features

  • A SPV synchronization mode has been introduced. SPV may be enabled with the
    --spv config option. The SPV sync mode uses local committed filter matching
    (as opposed to remote filtering as commonly done in other SPV implementations)
    to provide greater privacy and security guarantees by only fetching complete
    blocks on matches. SPV mode uses the Decred wire protocol and peer-to-peer
    network to sync to a target 8 outbound peers. The --spvconnect option is
    provided to manually specify the addresses of outbound peers rather than
    discovering these over DNS and from other peers.

  • A new ticket buyer implementation has been added. This buyer does not rely on
    any features unavailable to SPV mode. All config options which only apply to
    the original ticket buyer are now deprecated, and using only options available
    to the new buyer will cause the new buyer to be run instead. It is not
    possible to use the deprecated ticket buyer with SPV.

  • The gRPC method CreateWatchingOnlyWallet has been added to allow the
    creation of a watching-only wallet for an account extended pubkey.

  • The gRPC method SignTransactions has been added to sign multiple
    transactions in a single method.

  • The gRPC method ConstructTransaction now returns the index of any added
    change output, or -1 if no change was added.

  • The gRPC method GetAccountExtendedKey has been added to return an account's
    extended pubkey.

  • The gRPC method SpvSync has been added to execute the SPV synchronizer.
    This RPC returns a message stream used to notify clients of the syncer's
    activity.

  • A new config option --accountgaplimit allows the number of unused accounts to
    be user-configurable. The default has been dropped from 100 unused accounts
    to 10 to improve performance of account rediscovery. This option may be set
    to 100 to restore the previous behavior.

  • The JSON-RPC getstakeinfo result has been modified to include two new
    fields. unspent returns the number of tickets that have not been spent by a
    vote or revocation, and unspentexpired returns the number of unspent tickets
    that are past ticket expiry and cannot possibly be live. Unlike the missed
    and expired fields, these new fields are populated when running in SPV mode.

Other improvements

  • Unnecessarily-verbose debug logs have been removed when filtering ticket
    hashes for owned tickets.

  • The walletdb and snacl packages have been made internal packages to prevent
    these from being exposed by the public API. This is part of an ongoing effort
    to support module-aware builds with vgo and Go 1.11.

  • The error message for the unsupported operation of calling the JSON-RPC method
    listtransactions with an account name been improved by adding a hint to use
    * instead.

  • go vet is now tested by the CI infrastructure and several string formatting
    issues discovered by vet have been resolved.

  • The operating system and machine architecture are now logged at process
    startup together with the wallet release and Go versions.

  • The description for the --createtemp config option now references the
    requirement of additionally setting --appdata rather than the deprecated
    --datadir option.

  • Input amounts of previous outputs are now set before signing transactions.
    This will be required as proposed signature hash algorithms commit to the
    input amount.

Changelog

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

decrediton v1.3.0-rc1

This release of Decrediton marks the dawn of a large milestone in development.
SPV (simple payment verification) has been added in dcrwallet which allows
wallets to connect directly to peers and not required a fully synced node to be
connected. For now this feature will be turned OFF by default, then when we
have gotten thorough feedback and a confident in the usage, it will be turned
on by default.

While it's hard to give details of speed increases due to variances in systems,
we've seen roughly a 5x increase in syncing a previously used seed to tip on
mainnet. Previously, syncing the chain would take roughly 1hr plus another 5-10
mins for the wallet to become synced. Now, we're seeing about 20mins total time
to being able to fully use a wallet to send or purchase tickets.

In the coming releases, we are going to work on further speeding this process up,
as well as providing more feedback from dcrwallet to Decrediton to make a
richer user experience.

*Note: Automatic ticket purchasing has been disabled for SPV. We will be
implementing a way to start and stop the new v2 ticketbuyer in dcrwallet. This
new version is much simpler and really only has 1 option to set which would
be an absolute balance to maintain. This new version will also allow users to
run multiple ticket purchases for each account.

This release also has been audited by our design team at Eeter, LLC. Most of the
pages have received an update to the styling to add more polish and be more
resilient to various sizing and displays. In the near future, we will be
focusing on color themes and window sizing for small, medium and large displays.

We are also proud to announce the intial release of the Politeia integration.
While this functionality is still in beta-testing, what you see will be roughly
the final form. Proposals up for vote will be shown and your possible tickets
will be compared to the proposal's allowed tickets to vote. If there are
tickets available to vote, you simply make your choice, enter your passphrase
and your tickets are used to send the Politeia server your cryptographic proof
of ownership.

New Features

  • SPV integration - *Note: This integration is currently hidden from normal
    usage, if you would like to test it, please set "spv_mode": true, in your
    config.json file. With this new integration, there has been a new way of
    syncing that has been added. Now instead of needing to do all of the wallet
    loader processes in the proper order, one can simply call the SpvSync grpc and
    that will handle everything within dcrwallet. This will lead to much less
    errors and other headaches down the road. We have also added an
    "spv_connect": [], option in the config.json file, which will allow users to
    connect directly to a known peer instead of relying on the DNS seeders to find
    peers.

  • Whitelisting and Proxy - We have added new support to control the connections
    to domains that are used for various information. We have also added proxy
    support for those that choose to have the extra security. These were both
    necessary since the addition of Politeia wallet's communicating with the outside
    world. We felt the users should have full control over where the wallet is
    communicating. This support will be further improved upon in future releases
    and requests for things are made.

  • Initial Politeia Integration - *Note: This integration is currently hidden
    from normal usage, but can be accessed by setting "politeia_beta": true, in
    your config.json file. When activated the user is shown a new page on the
    side bar menu, reading "Governance." This will show them the Politeia
    information, of which is pulled from a request to the proposals site.
    They will be shown currently live and past votes.

  • Animated Onboarding Slides - All new animated slides were added. Big thanks
    for all the hard work from @kyleFirethought and everyone at Eeter! They really
    make the wallet shine.

Other improvements

  • Launcher - The launcher UI was audited and has most of its issues smoothed
    out. There were some lingering issues and possible ways of users to get "stuck"
    while loading up their wallets.

  • Inputs and Errors - All inputs have been audited for consistency and proper
    input error states are now being used. We are very pleased with the look and
    feel of the input errors and believe they are not too intrusive for users while
    being very clear of what needs to be corrected.

  • Max Wallet Option - Users are now able to set the max wallets that are
    shown on the launcher screen. The default is currently set to 3. But keep in
    mind that it was styled assuming only 3 would be shown, so there may be some
    distortions as the number shown grows.

  • Refined About Modal - The additional window was removed in favor of a React
    modal. This allowed us to clean up the code and remove a redundant menu bar
    group.

  • Long Form Translations - Due issues translating large pieces of text that were
    split up into partial sentences, we are now keeping large sections of
    documentation that need to be translated together. This is for things like the
    onboarding slides and various informational modals.

Changelog

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

@dajohi dajohi released this May 1, 2018

Assets 9

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.

@dajohi dajohi released this Apr 26, 2018 · 3 commits to master since this release

Assets 19

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:

Testing and Quality Assurance:

Misc:

Code Contributors (alphabetical order):

  • Andrew Chiw
  • Daniel Krawsiz
  • Dave Collins
  • David Hill
  • Donald Adu-Poku
  • Javed Khan
  • Jolan Luff
  • Jon Gillham
  • Josh Rickmar
  • Markus Richter
  • Matheus Degiovani
  • Ryan Vacek

dcrwallet 1.2.0

This release provides bug fixes for issues reported by users as well as new RPC
features and additions which are required for Decrediton and Politeia. SPV work
is ongoing but these changes will not land until a future release and after most
of the network nodes are running with committed filter support.

This release contains a database upgrade and once upgraded it is not possible
to downgrade to previous wallet releases without performing a seed restore with
the old version.

Bug fixes

  • Orphan votes (votes which have become invalid for the new main chain tip block
    after a reorg or missed vote) are now rejected from reentering the wallet if
    still notified by dcrd.

  • Watching only wallets are now usable again, after a breaking change to them
    introduced in the 1.1.2 release.

  • The transaction fee when purchasing tickets with the purchaseticket JSON-RPC
    and WalletService.PurchaseTickets gRPC methods will now fallback to the
    wallet's configured fee rate if not specified by the RPC request.

  • Various gRPC methods which allowed specifying 0 DCR as a target amount (e.g.
    WalletService.FundTransaction) now follow their documentation and will
    return or use as many unspent outputs as possible.

  • Outputs of transactions with an expiry set are not spendable by consensus
    rules until having reached coinbase maturity. These outputs are no longer
    returned or used when selecting previous outputs to create new transactions.

New features

  • A new gRPC method WalletService.UnspentOutputs has been added to return a
    stream of all wallet unspent outputs. Outputs may be filtered by their
    associated account and required confirmations, as well as stopping once a
    total target amount has been reached or exceeded.

  • A new gRPC method WalletService.BestBlock has been added which will return
    the hash and height of the current main chain tip block. Previously, this
    information was only available as a unary RPC with the
    WalletService.Accounts method.

  • The gRPC method WalletService.GetTickets will paginate results if called
    with a new target ticket count parameter.

  • A new gRPC method WalletService.CommittedTickets has been added to find
    ticket purchase hashes specified by the request where the largest P2PKH
    commitment amount is controlled by the wallet. The commitment address is
    additionally returned by the result.

  • A new gRPC method WalletService.SignMessages has been added to sign multiple
    messages at a time without needing to unlock and lock the wallet before and
    after each call.

  • The gRPC BlockDetails and BlockInfoResponse messages now include a new
    field which specifies whether votes in the block disapprove of the parent
    block.

  • A new JSON-RPC method publishunminedtransactions has been added which
    resends all unmined transactions of the wallet.

  • A new JSON-RPC method sweepaccount has been added which can be used to move
    as much value as possible from an account to either (possibly the same)
    account or an address. This RPC can be used in place of the consolidate
    method but without knowing and specifying exactly how many inputs to use.

  • The new JSON-RPC methods startautobuyer and stopautobuyer have been added
    which can start and stop the automatic ticket purchaser over JSON-RPC, similar
    to the already existing StartAutoBuyer and StopAutoBuyer gRPC methods of
    the TicketBuyerService.

  • The JSON-RPC method getbalance now returns aggregate balances for all
    accounts if called with the special * account name.

Other improvements

  • The sendtosstx, sendtossgen, and sendtossrtx JSON-RPC methods have been
    removed. These RPCs were intended to manually send ticket purchases, votes,
    and revocations manually, but were unimplemented and would cause crashes if
    used.

  • Transaction size estimation has been improved to more accurately estimate
    fees, in particular when redeeming with pay-to-script-hash redeem scripts.

  • The help JSON-RPC method text for the getbalance RPC has been updated to
    reflect the changes made to the returned object.

  • Users are now informed with log messages to configure their public passphrase
    or enter it on startup if the wallet is encrypted with one but it was not
    specified.

  • Script execution errors during sanity checks after signing inputs now record
    additional information about the failure including the previous output and
    script being spent and the signature script used by the input.

Changelog

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

decrediton 1.2.0

This release of decrediton adds some major changes to the wallet startup,
overview page and adds the first round of statistics for better user
information. Now that the overall look and feel designed by Eeter has been
impletmented we will be focusing on refinement and adding improved
responsiveness (eg dark mode, resolving to various media widths).

Launcher has been redesigned to provide the user with a more intuitive startup
experience. In normal working mode, the daemon (of the chosen network) will
begin to sync and become operational while the user completes wallet
creation/selection. Then once both the wallet is ready and the daemon has
synced the wallet will fully load.

A tutorial, release notes, settings and logs have all been added to the
launcher for the user to utilize whilst they may be waiting for their daemon
to sync. Hopefully this will allow the user to more seamlessly create wallets
with less confusion or require any additional support.

The wallet creation by seed has received a substantial update as well. We now
allow the user to copy seeds (if they complete a warning screen) and also paste
seeds. And for confirmation for new wallets only requires the user to complete
1/3 of the words to confirm storage of wallet's seed.

Overview has been redesigned to give the user more information about their
wallet's current situation and to guide them where to find various features
of their wallet. Basic graphs covering balances, tickets and transactions have
been added. All recent transactions and recent ticket activity can be found
below the overview graphs. We will be adding more features to the overview page
as we gauge user interest and feedback on existing additions.

Introductory data prepartion and statistics have been implemented for this
release. For now we are providing a small window of lookback for transactions,
staking and other information. The reduced window size is mostly an issue
with unsatisfactory performance. When this performance improves, we will be
adding custom windows and window lengths for custom graphing and exporting
options.

New Features

  • Validate Addresses - a form to validate addresses has been added to the
    Security Center. This will allow users to test addresses to confirm address
    ownership and/or validity.

  • Filter by address - now transactions can be filtered by address in History.
    When the user enters a string into the address filter form, it will show any
    address that has an output with a matching address.

  • Charts - we have decided to use recharts as our first
    charting solution.

  • Import wallet from hex seed - instead of entering in the 33 word
    mnemonic, they are now able to use the hex representation of their seed.

  • Export data to CSV - we now all users to export various types of data to csv.
    These options are found under the Transactions page.

  • Show logs - logs can now be found on the launcher and on the help page.
    For now, we only show the logs of the current instance of wallet and daemon.
    This is mostly due to performance with pulling in thousands of lines of text.

Changelog

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

@dajohi dajohi released this Dec 21, 2017 · 5 commits to master since this release

Assets 9

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.

@dajohi dajohi released this Dec 15, 2017 · 6 commits to master since this release

Assets 27

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 range. The results are streamed to
    the client.

  • A new gRPC method WalletService.ValidateAddress has been added with similar
    semantics and usage to the validateaddress JSON-RPC method. It can be used
    to decode an address string, ensuring that it is a valid address, as well as
    returning whether the address is owned by the wallet.

  • A new gRPC service DecodeMessageService has been introduced to make it
    easier for clients not able to decode raw Decred wire messages themselves to
    decode a message into a gRPC message. Currently, one method exists in the
    service, DecodeRawTransaction, which decodes a Decred transaction.

  • Pagination support has been added to the WalletService.GetTransactions
    method through the introduction of a new target_transaction_count parameter
    in the request. Responses are immediately streamed to the client when the
    target is reached.

  • The TX IPC pipe has been added (enabled with the pipetx option) to receive
    messages from the application by a parent process. When combined with the
    rpclistenerevents option, this allows the application to inform the parent
    process of the listener addresses used by the gRPC and JSON-RPC servers. This
    is especially useful when binding listeners to port 0 as the application is
    able to report the actual port chosen by the operating system to the parent
    process.

Other improvements

  • Vendoring management of dependency source code has been switched from glide
    to dep. See the README.md for new build instructions.

  • The BIP0044 coin type has been seamlessly upgraded from the old Decred value
    of 20 to 42. The new coin type is the coin type reserved for Decred in
    SLIP0044 and
    will allow greater compatibility with third party wallets. New wallets are
    always created with the new coin type, but for legacy compatibility old
    wallets and seed restores which have address usage with the old coin type will
    not be upgraded.

  • The address discovery algorithm has been made more concurrent and should see
    performance improvements, especially on CPUs with high core counts.

  • Performance improvements were made to the WalletService.GetTransactions gRPC
    method by avoiding unnecessary JSON-RPC calls to dcrd.

  • The ticketaddress option has been deprecated and replaced by the
    ticketbuyer.votingaddress option.

  • Publishing duplicate vote transactions in a redundant voting wallet setup no
    longer logs an error for a rejected duplicate transaction.

Changelog

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

decrediton v1.1.2

This release marks a major turning point in our overall look and feel of
Decrediton. We have introduced consistent header areas with a new subpage/tab
interface. React-motion has been added to give a better feel for transitions
from page to page and expanded area reveals. All information modals and
passphrase modals have been consolidated to have a consistent feel whenever they
are used.

As part of the design overhaul, the Tickets page has begun its transformation
to provide a much better user experience. My Tickets subpage is the first step
into giving users a clearer picture into their current staking situation. In
the upcoming release, we will be adding extensive statistics and graphing to
further help visualize a given users' balance and staking history. Overall,
we aim to continue to add more tools that will help users' staking experience
be much more enjoyable and carefree.

We have also added advanced daemon setup abilities for users that want to use
remote daemons or use a different location for their blockchain data. In the
next release, we plan on also adding the ability to handle advanced back-end
wallet setups: easily switch between different wallet files on the same machine,
connecting to a remote wallet and other possible situations. But these advanced
options will also be completely transparent for users that choose to run with
the default settings.

We have added a Security Center page that will be a catch-all place to
store tools that we feel have utility, but aren't needed for everyday normal
wallet operation. The first 2 tools that have been added are for Signing and
Verifying messages using addresses and private keys to prove ownership of a
given address. Here is a typical use case: User A wants to prove to User B
that they control a given address. With the Sign Message tool, User A enters
the address, a message and their wallet's private passphrase. The tool produces
a hash that was created based on that address' private key and the given
message. With the Verify Message tool, User B can use the address in question,
the hash and the message from User A to verify that it was signed using that
address' private key.

We are also happy to announce the introduction of internationalization.
Brazilian Portuguese has been added for the first pass and we will be slowly
adding more languages on every new release.

Things to expect in the next release:

  • New overview page design
  • Rich historical Statistics/Graphs
  • New staking account user experience
  • Advanced wallet settings
  • More languages translated

Bug fixes

  • Fix issue on Windows caused by using "Aux" as a filename. Aux is a restricted
    filename with Windows and a simple filename change fixed it.

  • Fix shutdown issue with macOS. When cmd-Q or quitting Decrediton from the
    dock caused dcrd and dcrwallet to not be shutdown in the background. By
    adding a final closeClis() in app.on("before-quit",...) it ensures that
    everything is closed on any shutdown.

  • Removed Skip Sync button due to the new slip44 change in dcrwallet. With the
    new coin type change, dcrwallet needs to check if there has been any address
    usage up to that point in the chain for a given wallet.

  • Shorten account names in various areas to avoid obnoxious overflow.

  • Fix issue that was occuring when clearing out stakepool configurations. This
    would cause users to possibly have incorrect stakepool setups.

  • Change functionality of the space key during seed entry. Previously, when the
    user would enter the space key they would end up not "selecting" a word and
    then just type the whole seed. Now the space "selects" the word just as
    pressing tab does.

Changelog

All commits since the last release may be viewed on GitHub
here. Also see
all changes to dcrwallet
here.

@dajohi dajohi released this Sep 29, 2017 · 8 commits to master since this release

Assets 7

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.