Update release notes for 1.14 (#1464)
* Move old release notes out of the way * Removed very old Bitcoin release notes as of minimal value in the context of Dogecoin. * Move remaining Bitcoin release notes into their own folder. * Move Bitcoin 0.9 release notes into Bitcoin release notes folder. * Start cleaning up release notes to reflect Doge
This commit is contained in:
Ross Nicoll
parent
a3a2e890ce
commit
e85c0fdb90
|
|
@ -1,30 +1,42 @@
|
|||
Bitcoin Core version 0.14.2 is now available from:
|
||||
Dogecoin Core version 1.14.2 is now available from:
|
||||
|
||||
<https://bitcoin.org/bin/bitcoin-core-0.14.2/>
|
||||
<https://github.com/dogecoin/dogecoin/releases/tag/v1.14.0/>
|
||||
|
||||
This is a new minor version release, including various bugfixes and
|
||||
performance improvements, as well as updated translations.
|
||||
This is a new major version release, including new features, various bugfixes
|
||||
and performance improvements, as well as updated translations.
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
|
||||
<https://github.com/bitcoin/bitcoin/issues>
|
||||
<https://github.com/dogecoin/dogecoin/issues>
|
||||
|
||||
To receive security and update notifications, please subscribe to:
|
||||
To receive security and update notifications, please watch reddit or Twitter:
|
||||
|
||||
<https://bitcoincore.org/en/list/announcements/join/>
|
||||
* https://www.reddit.com/r/dogecoin/
|
||||
* @Dogecoin on Twitter for high priority announcements
|
||||
* @dogecoin\_devs on Twitter for updates on development work
|
||||
|
||||
The developers also maintain personal Twitter accounts:
|
||||
|
||||
* @langer\_hans
|
||||
* @JRossNicoll
|
||||
|
||||
Lastly the founders are on Twitter, although as of the time of writing not involved in
|
||||
maintaining Dogecoin:
|
||||
|
||||
* @ummjackson
|
||||
* @BillyM2k
|
||||
|
||||
Compatibility
|
||||
==============
|
||||
|
||||
Bitcoin Core is extensively tested on multiple operating systems using
|
||||
the Linux kernel, macOS 10.8+, and Windows Vista and later.
|
||||
Dogecoin Core is extensively tested on Ubuntu Server LTS, Mac OS X and Windows 10.
|
||||
|
||||
Microsoft ended support for Windows XP on [April 8th, 2014](https://www.microsoft.com/en-us/WindowsForBusiness/end-of-xp-support),
|
||||
No attempt is made to prevent installing or running the software on Windows XP, you
|
||||
can still do so at your own risk but be aware that there are known instabilities and issues.
|
||||
Please do not report issues about Windows XP to the issue tracker.
|
||||
|
||||
Bitcoin Core should also work on most other Unix-like systems but is not
|
||||
Dogecoin Core should also work on most other Unix-like systems but is not
|
||||
frequently tested on them.
|
||||
|
||||
Notable changes
|
||||
|
|
@ -87,6 +99,147 @@ Bundled miniupnpc was updated to 2.0.20170509. This fixes an integer signedness
|
|||
(within the LAN) to cause a denial of service or possibly have unspecified
|
||||
other impact.
|
||||
|
||||
Performance Improvements
|
||||
--------------
|
||||
|
||||
Validation speed and network propagation performance have been greatly
|
||||
improved, leading to much shorter sync and initial block download times.
|
||||
|
||||
- The script signature cache has been reimplemented as a "cuckoo cache",
|
||||
allowing for more signatures to be cached and faster lookups.
|
||||
- Assumed-valid blocks have been introduced which allows script validation to
|
||||
be skipped for ancestors of known-good blocks, without changing the security
|
||||
model. See below for more details.
|
||||
- In some cases, compact blocks are now relayed before being fully validated as
|
||||
per BIP152.
|
||||
- P2P networking has been refactored with a focus on concurrency and
|
||||
throughput. Network operations are no longer bottlenecked by validation. As a
|
||||
result, block fetching is several times faster than previous releases in many
|
||||
cases.
|
||||
- The UTXO cache now claims unused mempool memory. This speeds up initial block
|
||||
download as UTXO lookups are a major bottleneck there, and there is no use for
|
||||
the mempool at that stage.
|
||||
|
||||
|
||||
Manual Pruning
|
||||
--------------
|
||||
|
||||
Dogecoin Core introduces pruning the blockchain in 1.14. Pruning
|
||||
the blockchain allows for significant storage space savings as the vast majority of
|
||||
the downloaded data can be discarded after processing so very little of it remains
|
||||
on the disk.
|
||||
|
||||
Manual block pruning can now be enabled by setting `-prune=1`. Once that is set,
|
||||
the RPC command `pruneblockchain` can be used to prune the blockchain up to the
|
||||
specified height or timestamp.
|
||||
|
||||
`getinfo` Deprecated
|
||||
--------------------
|
||||
|
||||
The `getinfo` RPC command has been deprecated. Each field in the RPC call
|
||||
has been moved to another command's output with that command also giving
|
||||
additional information that `getinfo` did not provide. The following table
|
||||
shows where each field has been moved to:
|
||||
|
||||
|`getinfo` field | Moved to |
|
||||
|------------------|-------------------------------------------|
|
||||
`"version"` | `getnetworkinfo()["version"]`
|
||||
`"protocolversion"`| `getnetworkinfo()["protocolversion"]`
|
||||
`"walletversion"` | `getwalletinfo()["walletversion"]`
|
||||
`"balance"` | `getwalletinfo()["balance"]`
|
||||
`"blocks"` | `getblockchaininfo()["blocks"]`
|
||||
`"timeoffset"` | `getnetworkinfo()["timeoffset"]`
|
||||
`"connections"` | `getnetworkinfo()["connections"]`
|
||||
`"proxy"` | `getnetworkinfo()["networks"][0]["proxy"]`
|
||||
`"difficulty"` | `getblockchaininfo()["difficulty"]`
|
||||
`"testnet"` | `getblockchaininfo()["chain"] == "test"`
|
||||
`"keypoololdest"` | `getwalletinfo()["keypoololdest"]`
|
||||
`"keypoolsize"` | `getwalletinfo()["keypoolsize"]`
|
||||
`"unlocked_until"` | `getwalletinfo()["unlocked_until"]`
|
||||
`"paytxfee"` | `getwalletinfo()["paytxfee"]`
|
||||
`"relayfee"` | `getnetworkinfo()["relayfee"]`
|
||||
`"errors"` | `getnetworkinfo()["warnings"]`
|
||||
|
||||
ZMQ On Windows
|
||||
--------------
|
||||
|
||||
Previously the ZeroMQ notification system was unavailable on Windows
|
||||
due to various issues with ZMQ. These have been fixed upstream and
|
||||
now ZMQ can be used on Windows. Please see [this document](https://github.com/bitcoin/bitcoin/blob/master/doc/zmq.md) for
|
||||
help with using ZMQ in general.
|
||||
|
||||
Nested RPC Commands in Debug Console
|
||||
------------------------------------
|
||||
|
||||
The ability to nest RPC commands has been added to the debug console. This
|
||||
allows users to have the output of a command become the input to another
|
||||
command without running the commands separately.
|
||||
|
||||
The nested RPC commands use bracket syntax (i.e. `getwalletinfo()`) and can
|
||||
be nested (i.e. `getblock(getblockhash(1))`). Simple queries can be
|
||||
done with square brackets where object values are accessed with either an
|
||||
array index or a non-quoted string (i.e. `listunspent()[0][txid]`). Both
|
||||
commas and spaces can be used to separate parameters in both the bracket syntax
|
||||
and normal RPC command syntax.
|
||||
|
||||
Network Activity Toggle
|
||||
-----------------------
|
||||
|
||||
A RPC command and GUI toggle have been added to enable or disable all p2p
|
||||
network activity. The network status icon in the bottom right hand corner
|
||||
is now the GUI toggle. Clicking the icon will either enable or disable all
|
||||
p2p network activity. If network activity is disabled, the icon will
|
||||
be grayed out with an X on top of it.
|
||||
|
||||
Additionally the `setnetworkactive` RPC command has been added which does
|
||||
the same thing as the GUI icon. The command takes one boolean parameter,
|
||||
`true` enables networking and `false` disables it.
|
||||
|
||||
Out-of-sync Modal Info Layer
|
||||
----------------------------
|
||||
|
||||
When Dogecoin Core is out-of-sync on startup, a semi-transparent information
|
||||
layer will be shown over top of the normal display. This layer contains
|
||||
details about the current sync progress and estimates the amount of time
|
||||
remaining to finish syncing. This layer can also be hidden and subsequently
|
||||
unhidden by clicking on the progress bar at the bottom of the window.
|
||||
|
||||
Support for JSON-RPC Named Arguments
|
||||
------------------------------------
|
||||
|
||||
Commands sent over the JSON-RPC interface and through the `bitcoin-cli` binary
|
||||
can now use named arguments. This follows the [JSON-RPC specification](http://www.jsonrpc.org/specification)
|
||||
for passing parameters by-name with an object.
|
||||
|
||||
`bitcoin-cli` has been updated to support this by parsing `name=value` arguments
|
||||
when the `-named` option is given.
|
||||
|
||||
Some examples:
|
||||
|
||||
src/bitcoin-cli -named help command="help"
|
||||
src/bitcoin-cli -named getblockhash height=0
|
||||
src/bitcoin-cli -named getblock blockhash=000000000019d6689c085ae165831e934ff763ae46a2a6c172b3f1b60a8ce26f
|
||||
src/bitcoin-cli -named sendtoaddress address="(snip)" amount="1.0" subtractfeefromamount=true
|
||||
|
||||
The order of arguments doesn't matter in this case. Named arguments are also
|
||||
useful to leave out arguments that should stay at their default value. The
|
||||
rarely-used arguments `comment` and `comment_to` to `sendtoaddress`, for example, can
|
||||
be left out. However, this is not yet implemented for many RPC calls, this is
|
||||
expected to land in a later release.
|
||||
|
||||
The RPC server remains fully backwards compatible with positional arguments.
|
||||
|
||||
Opt into RBF When Sending
|
||||
-------------------------
|
||||
|
||||
A new startup option, `-walletrbf`, has been added to allow users to have all
|
||||
transactions sent opt into RBF support. The default value for this option is
|
||||
currently `false`, so transactions will not opt into RBF by default. The new
|
||||
`bumpfee` RPC can be used to replace transactions that opt into RBF.
|
||||
|
||||
Sensitive Data Is No Longer Stored In Debug Console History
|
||||
-----------------------------------------------------------
|
||||
|
||||
This only affects users that have explicitly enabled UPnP through the GUI
|
||||
setting or through the `-upnp` option, as since the last UPnP vulnerability
|
||||
(in Bitcoin Core 0.10.3) it has been disabled by default.
|
||||
|
|
@ -97,13 +250,13 @@ possible.
|
|||
Known Bugs
|
||||
==========
|
||||
|
||||
Since 0.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
|
||||
Since 1.14.0 the approximate transaction fee shown in Bitcoin-Qt when using coin
|
||||
control and smart fee estimation does not reflect any change in target from the
|
||||
smart fee slider. It will only present an approximate fee calculated using the
|
||||
default target. The fee calculated using the correct target is still applied to
|
||||
the transaction and shown in the final send confirmation dialog.
|
||||
|
||||
0.14.2 Change log
|
||||
1.14.0 Change log
|
||||
=================
|
||||
|
||||
Detailed release notes follow. This overview includes changes that affect
|
||||
|
|
@ -132,6 +285,157 @@ git merge commit are mentioned.
|
|||
### Wallet
|
||||
- #10294 `1847642` Unset change position when there is no change (instagibbs)
|
||||
|
||||
GUI Changes
|
||||
-----------
|
||||
|
||||
- After resetting the options by clicking the `Reset Options` button
|
||||
in the options dialog or with the `-resetguioptions` startup option,
|
||||
the user will be prompted to choose the data directory again. This
|
||||
is to ensure that custom data directories will be kept after the
|
||||
option reset which clears the custom data directory set via the choose
|
||||
datadir dialog.
|
||||
|
||||
- Multiple peers can now be selected in the list of peers in the debug
|
||||
window. This allows for users to ban or disconnect multiple peers
|
||||
simultaneously instead of banning them one at a time.
|
||||
|
||||
- An indicator has been added to the bottom right hand corner of the main
|
||||
window to indicate whether the wallet being used is a HD wallet. This
|
||||
icon will be grayed out with an X on top of it if the wallet is not a
|
||||
HD wallet.
|
||||
|
||||
Low-level RPC changes
|
||||
----------------------
|
||||
|
||||
- `importprunedfunds` only accepts two required arguments. Some versions accept
|
||||
an optional third arg, which was always ignored. Make sure to never pass more
|
||||
than two arguments.
|
||||
|
||||
- The first boolean argument to `getaddednodeinfo` has been removed. This is
|
||||
an incompatible change.
|
||||
|
||||
- RPC command `getmininginfo` loses the "testnet" field in favor of the more
|
||||
generic "chain" (which has been present for years).
|
||||
|
||||
- A new RPC command `preciousblock` has been added which marks a block as
|
||||
precious. A precious block will be treated as if it were received earlier
|
||||
than a competing block.
|
||||
|
||||
- A new RPC command `importmulti` has been added which receives an array of
|
||||
JSON objects representing the intention of importing a public key, a
|
||||
private key, an address and script/p2sh
|
||||
|
||||
- Use of `getrawtransaction` for retrieving confirmed transactions with unspent
|
||||
outputs has been deprecated. For now this will still work, but in the future
|
||||
it may change to only be able to retrieve information about transactions in
|
||||
the mempool or if `txindex` is enabled.
|
||||
|
||||
- A new RPC command `getmemoryinfo` has been added which will return information
|
||||
about the memory usage of Dogecoin Core. This was added in conjunction with
|
||||
optimizations to memory management. See [Pull #8753](https://github.com/bitcoin/bitcoin/pull/8753)
|
||||
for more information.
|
||||
|
||||
- A new RPC command `bumpfee` has been added which allows replacing an
|
||||
unconfirmed wallet transaction that signaled RBF (see the `-walletrbf`
|
||||
startup option above) with a new transaction that pays a higher fee, and
|
||||
should be more likely to get confirmed quickly.
|
||||
|
||||
HTTP REST Changes
|
||||
-----------------
|
||||
|
||||
- UTXO set query (`GET /rest/getutxos/<checkmempool>/<txid>-<n>/<txid>-<n>
|
||||
/.../<txid>-<n>.<bin|hex|json>`) responses were changed to return status
|
||||
code `HTTP_BAD_REQUEST` (400) instead of `HTTP_INTERNAL_SERVER_ERROR` (500)
|
||||
when requests contain invalid parameters.
|
||||
|
||||
Fee Estimation Changes
|
||||
----------------------
|
||||
|
||||
- Fee estimation for a confirmation target of 1 block has been
|
||||
disabled. The fee slider will no longer be able to choose a target of 1 block.
|
||||
This is only a minor behavior change as there was often insufficient
|
||||
data for this target anyway. `estimatefee 1` will now always return -1 and
|
||||
`estimatesmartfee 1` will start searching at a target of 2.
|
||||
|
||||
- The default target for fee estimation is changed to 6 blocks in both the GUI
|
||||
(previously 25) and for RPC calls (previously 2).
|
||||
|
||||
Removal of Priority Estimation
|
||||
------------------------------
|
||||
|
||||
- Estimation of "priority" needed for a transaction to be included within a target
|
||||
number of blocks has been removed. The RPC calls are deprecated and will either
|
||||
return -1 or 1e24 appropriately. The format for `fee_estimates.dat` has also
|
||||
changed to no longer save these priority estimates. It will automatically be
|
||||
converted to the new format which is not readable by prior versions of the
|
||||
software.
|
||||
|
||||
- Support for "priority" (coin age) transaction sorting for mining is
|
||||
considered deprecated in Core and will be removed in the next major version.
|
||||
This is not to be confused with the `prioritisetransaction` RPC which will remain
|
||||
supported by Core for adding fee deltas to transactions.
|
||||
|
||||
P2P connection management
|
||||
--------------------------
|
||||
|
||||
- Peers manually added through the `-addnode` option or `addnode` RPC now have their own
|
||||
limit of eight connections which does not compete with other inbound or outbound
|
||||
connection usage and is not subject to the limitation imposed by the `-maxconnections`
|
||||
option.
|
||||
|
||||
- New connections to manually added peers are performed more quickly.
|
||||
|
||||
Introduction of assumed-valid blocks
|
||||
-------------------------------------
|
||||
|
||||
- A significant portion of the initial block download time is spent verifying
|
||||
scripts/signatures. Although the verification must pass to ensure the security
|
||||
of the system, no other result from this verification is needed: If the node
|
||||
knew the history of a given block were valid it could skip checking scripts
|
||||
for its ancestors.
|
||||
|
||||
- A new configuration option 'assumevalid' is provided to express this knowledge
|
||||
to the software. Unlike the 'checkpoints' in the past this setting does not
|
||||
force the use of a particular chain: chains that are consistent with it are
|
||||
processed quicker, but other chains are still accepted if they'd otherwise
|
||||
be chosen as best. Also unlike 'checkpoints' the user can configure which
|
||||
block history is assumed true, this means that even outdated software can
|
||||
sync more quickly if the setting is updated by the user.
|
||||
|
||||
- Because the validity of a chain history is a simple objective fact it is much
|
||||
easier to review this setting. As a result the software ships with a default
|
||||
value adjusted to match the current chain shortly before release. The use
|
||||
of this default value can be disabled by setting -assumevalid=0
|
||||
|
||||
Fundrawtransaction change address reuse
|
||||
----------------------------------------
|
||||
|
||||
- Before 1.14, `fundrawtransaction` was by default wallet stateless. In
|
||||
almost all cases `fundrawtransaction` does add a change-output to the
|
||||
outputs of the funded transaction. Before 1.14, the used keypool key was
|
||||
never marked as change-address key and directly returned to the keypool
|
||||
(leading to address reuse). Before 1.14, calling `getnewaddress`
|
||||
directly after `fundrawtransaction` did generate the same address as
|
||||
the change-output address.
|
||||
|
||||
- Since 0.14, fundrawtransaction does reserve the change-output-key from
|
||||
the keypool by default (optional by setting `reserveChangeKey`, default =
|
||||
`true`)
|
||||
|
||||
- Users should also consider using `getrawchangeaddress()` in conjunction
|
||||
with `fundrawtransaction`'s `changeAddress` option.
|
||||
|
||||
Unused mempool memory used by coincache
|
||||
----------------------------------------
|
||||
|
||||
- Before 1.14, memory reserved for mempool (using the `-maxmempool` option)
|
||||
went unused during initial block download, or IBD. In 0.14, the UTXO DB cache
|
||||
(controlled with the `-dbcache` option) borrows memory from the mempool
|
||||
when there is extra memory available. This may result in an increase in
|
||||
memory usage during IBD for those previously relying on only the `-dbcache`
|
||||
option to limit memory during that time.
|
||||
>>>>>>> Update release notes for 1.14 (#1464)
|
||||
|
||||
Credits
|
||||
=======
|
||||
|
||||
|
|
@ -143,6 +447,33 @@ Thanks to everyone who directly contributed to this release:
|
|||
- Gregory Sanders
|
||||
- Jonas Schnelli
|
||||
- Matt Corallo
|
||||
<<<<<<< HEAD
|
||||
=======
|
||||
- Matthew King
|
||||
- matthias
|
||||
- Max Keller
|
||||
- Micha
|
||||
- Michael Ford
|
||||
- Michael Rotarius
|
||||
- Mitchell Cash
|
||||
- mrbandrews
|
||||
- mruddy
|
||||
- Nicolas DORIER
|
||||
- nomnombtc
|
||||
- Patrick Lodder
|
||||
- Patrick Strateman
|
||||
- Pavel Janík
|
||||
- Pedro Branco
|
||||
- Peter Todd
|
||||
- Pieter Wuille
|
||||
- poole\_party
|
||||
- practicalswift
|
||||
- R E Broadley
|
||||
- randy-waterhouse
|
||||
- Richard Kiss
|
||||
- Robert McLaughlin
|
||||
- rodasmith
|
||||
- Ross Nicoll
|
||||
- Russell Yanofsky
|
||||
- Shigeya Suzuki
|
||||
- Wladimir J. van der Laan
|
||||
|
|
|
|||
29
doc/release-notes/RELEASE_NOTES_1.8.2.md
Normal file
29
doc/release-notes/RELEASE_NOTES_1.8.2.md
Normal file
|
|
@ -0,0 +1,29 @@
|
|||
# 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
|
||||
24
doc/release-notes/RELEASE_NOTES_1.8.3.md
Normal file
24
doc/release-notes/RELEASE_NOTES_1.8.3.md
Normal file
|
|
@ -0,0 +1,24 @@
|
|||
# Dogecoin Core 1.8.3
|
||||
|
||||
Dogecoin Core 1.8.3 is a security release. It fixes issues in regards to an upcoming announcement of possible DoS vulnerabilities.
|
||||
See [the announcement on the bitcoin-dev mailing list](https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2015-June/009135.html) 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 usptream 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.
|
||||
|
||||
## 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
|
||||
68
doc/release-notes/RELEASE_NOTES_1_8.1.md
Normal file
68
doc/release-notes/RELEASE_NOTES_1_8.1.md
Normal file
|
|
@ -0,0 +1,68 @@
|
|||
# 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=<n> and -maxorphanblocks=<n> 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
|
||||
|
|
@ -1,13 +0,0 @@
|
|||
Version 0.3.12 is now available.
|
||||
|
||||
Features:
|
||||
* json-rpc errors return a more standard error object. (thanks to Gavin Andresen)
|
||||
* json-rpc command line returns exit codes.
|
||||
* json-rpc "backupwallet" command.
|
||||
* Recovers and continues if an exception is caused by a message you received. Other nodes shouldn't be able to cause an exception, and it hasn't happened before, but if a way is found to cause an exception, this would keep it from being used to stop network nodes.
|
||||
|
||||
If you have json-rpc code that checks the contents of the error string, you need to change it to expect error objects of the form {"code":<number>,"message":<string>}, which is the standard. See this thread:
|
||||
http://www.bitcoin.org/smf/index.php?topic=969.0
|
||||
|
||||
Download:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.12/
|
||||
|
|
@ -1,26 +0,0 @@
|
|||
Version 0.3.13 is now available. You should upgrade to prevent potential problems with 0/unconfirmed transactions. Note: 0.3.13 prevents problems if you haven't already spent a 0/unconfirmed transaction, but if that already happened, you need 0.3.13.2.
|
||||
|
||||
Changes:
|
||||
* Don't count or spend payments until they have 1 confirmation.
|
||||
* Internal version number from 312 to 31300.
|
||||
* Only accept transactions sent by IP address if -allowreceivebyip is specified.
|
||||
* Dropped DB_PRIVATE Berkeley DB flag.
|
||||
* Fix problem sending the last cent with sub-cent fractional change.
|
||||
* Auto-detect whether to use 128-bit 4-way SSE2 on Linux.
|
||||
Gavin Andresen:
|
||||
* Option -rpcallowip= to accept json-rpc connections from another machine.
|
||||
* Clean shutdown on SIGTERM on Linux.
|
||||
|
||||
Download:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.13/
|
||||
|
||||
(Thanks Laszlo for the Mac OSX build!)
|
||||
|
||||
Note:
|
||||
The SSE2 auto-detect in the Linux 64-bit version doesn't work with AMD in 64-bit mode. Please try this instead and let me know if it gets it right:
|
||||
http://www.bitcoin.org/download/bitcoin-0.3.13.1-specialbuild-linux64.tar.gz
|
||||
|
||||
You can still control the SSE2 use manually with -4way and -4way=0.
|
||||
|
||||
Version 0.3.13.2 (SVN rev 161) has improvements for the case where you already had 0/unconfirmed transactions that you might have already spent. Here's a Windows build of it:
|
||||
http://www.bitcoin.org/download/bitcoin-0.3.13.2-win32-setup.exe
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
Version 0.3.14 is now available
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.14/
|
||||
|
||||
Changes:
|
||||
* Key pool feature for safer wallet backup
|
||||
Gavin Andresen:
|
||||
* TEST network mode with switch -testnet
|
||||
* Option to use SSL for JSON-RPC connections on unix/osx
|
||||
* validateaddress RPC command
|
||||
eurekafag:
|
||||
* Russian translation
|
||||
|
|
@ -1,6 +0,0 @@
|
|||
* paytxfee switch is now per KB, so it adds the correct fee for large transactions
|
||||
* sending avoids using coins with less than 6 confirmations if it can
|
||||
* BitcoinMiner processes transactions in priority order based on age of dependencies
|
||||
* make sure generation doesn't start before block 74000 downloaded
|
||||
* bugfixes by Dean Gores
|
||||
* testnet, keypoololdest and paytxfee added to getinfo
|
||||
|
|
@ -1 +0,0 @@
|
|||
Never released.
|
||||
|
|
@ -1,12 +0,0 @@
|
|||
Version 0.3.17 is now available.
|
||||
|
||||
Changes:
|
||||
* new getwork, thanks m0mchil
|
||||
* added transaction fee setting in UI options menu
|
||||
* free transaction limits
|
||||
* sendtoaddress returns transaction id instead of "sent"
|
||||
* getaccountaddress <account>
|
||||
|
||||
The UI transaction fee setting was easy since it was still there from 0.1.5 and all I had to do was re-enable it.
|
||||
|
||||
The accounts-based commands: move, sendfrom and getbalance <account> will be in the next release. We still have some more changes to make first.
|
||||
|
|
@ -1,11 +0,0 @@
|
|||
Changes:
|
||||
* Fixed a wallet.dat compatibility problem if you downgraded from 0.3.17 and then upgraded again
|
||||
* IsStandard() check to only include known transaction types in blocks
|
||||
* Jgarzik's optimisation to speed up the initial block download a little
|
||||
|
||||
The main addition in this release is the Accounts-Based JSON-RPC commands that Gavin's been working on (more details at http://www.bitcoin.org/smf/index.php?topic=1886.0).
|
||||
* getaccountaddress
|
||||
* sendfrom
|
||||
* move
|
||||
* getbalance
|
||||
* listtransactions
|
||||
|
|
@ -1,9 +0,0 @@
|
|||
There's more work to do on DoS, but I'm doing a quick build of what I have so far in case it's needed, before venturing into more complex ideas. The build for this is version 0.3.19.
|
||||
|
||||
- Added some DoS controls
|
||||
As Gavin and I have said clearly before, the software is not at all resistant to DoS attack. This is one improvement, but there are still more ways to attack than I can count.
|
||||
|
||||
I'm leaving the -limitfreerelay part as a switch for now and it's there if you need it.
|
||||
|
||||
- Removed "safe mode" alerts
|
||||
"safe mode" alerts was a temporary measure after the 0.3.9 overflow bug. We can say all we want that users can just run with "-disablesafemode", but it's better just not to have it for the sake of appearances. It was never intended as a long term feature. Safe mode can still be triggered by seeing a longer (greater total PoW) invalid block chain.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Never released or release notes were lost.
|
||||
|
|
@ -1,17 +0,0 @@
|
|||
The maxsendbuffer bug (0.3.20.1 clients not being able to download the block chain from other 0.3.20.1 clients) was only going to get
|
||||
worse as people upgraded, so I cherry-picked the bug fix and created a minor release yesterday.
|
||||
|
||||
The Amazon Machine Images I used to do the builds are available:
|
||||
|
||||
ami-38a05251 Bitcoin-v0.3.20.2 Mingw (Windows; Administrator password 'bitcoin development')
|
||||
ami-30a05259 Bitcoin_0.3.20.2 Linux32
|
||||
ami-8abc4ee3 Bitcoin_0.3.20.2 Linux64
|
||||
|
||||
(mac build will be done soon)
|
||||
|
||||
If you have already downloaded version 0.3.20.1, please either add this to your bitcoin.conf file:
|
||||
|
||||
maxsendbuffer=10000
|
||||
maxreceivebuffer=10000
|
||||
|
||||
... or download the new version.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
Please checkout the git integration branch from:
|
||||
|
||||
https://github.com/bitcoin/bitcoin
|
||||
|
||||
... and help test. The new features that need testing are:
|
||||
|
||||
* -nolisten : https://github.com/bitcoin/bitcoin/pull/11
|
||||
* -rescan : scan block chain for missing wallet transactions
|
||||
* -printtoconsole : https://github.com/bitcoin/bitcoin/pull/37
|
||||
* RPC gettransaction details : https://github.com/bitcoin/bitcoin/pull/24
|
||||
* listtransactions new features : https://github.com/bitcoin/bitcoin/pull/10
|
||||
|
||||
Bug fixes that also need testing:
|
||||
|
||||
* -maxconnections= : https://github.com/bitcoin/bitcoin/pull/42
|
||||
* RPC listaccounts minconf : https://github.com/bitcoin/bitcoin/pull/27
|
||||
* RPC move, add time to output : https://github.com/bitcoin/bitcoin/pull/21
|
||||
* ...and several improvements to --help output.
|
||||
|
||||
This needs more testing on Windows! Please drop me a quick private message, email, or IRC message if you are able to do some testing. If you find bugs, please open an issue at:
|
||||
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
Binaries for Bitcoin version 0.3.21 are available at:
|
||||
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.21/
|
||||
|
||||
Changes and new features from the 0.3.20 release include:
|
||||
|
||||
* Universal Plug and Play support. Enable automatic opening of a port for incoming connections by running bitcoin or bitcoind with the - -upnp=1 command line switch or using the Options dialog box.
|
||||
|
||||
* Support for full-precision bitcoin amounts. You can now send, and bitcoin will display, bitcoin amounts smaller than 0.01. However, sending fewer than 0.01 bitcoins still requires a 0.01 bitcoin fee (so you can send 1.0001 bitcoins without a fee, but you will be asked to pay a fee if you try to send 0.0001).
|
||||
|
||||
* A new method of finding bitcoin nodes to connect with, via DNS A records. Use the -dnsseed option to enable.
|
||||
|
||||
For developers, changes to bitcoin's remote-procedure-call API:
|
||||
|
||||
* New rpc command "sendmany" to send bitcoins to more than one address in a single transaction.
|
||||
|
||||
* Several bug fixes, including a serious intermittent bug that would sometimes cause bitcoind to stop accepting rpc requests.
|
||||
|
||||
* -logtimestamps option, to add a timestamp to each line in debug.log.
|
||||
|
||||
* Immature blocks (newly generated, under 120 confirmations) are now shown in listtransactions.
|
||||
|
|
@ -1,16 +0,0 @@
|
|||
Download URL: https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.22/
|
||||
|
||||
This is largely a bugfix and TX fee schedule release. We also hope to make 0.3.23 a quick release, to fix problems that the network has seen due to explosive growth in the past week.
|
||||
|
||||
Notable changes:
|
||||
* Client will accept and relay TX's with 0.0005 BTC fee schedule (users still pay 0.01 BTC per kb, until next version)
|
||||
* Non-standard transactions accepted on testnet
|
||||
* Source code tree reorganized (prep for autotools build)
|
||||
* Remove "Generate Coins" option from GUI, and remove 4way SSE miner. Internal reference CPU miner remains available, but users are directed to external miners for best hash production.
|
||||
* IRC is overflowing. Client now bootstraps to channels #bitcoin00 - #bitcoin99
|
||||
* DNS names now may be used with -addnode, -connect (requires -dns to enable)
|
||||
|
||||
RPC changes:
|
||||
* 'listtransactions' adds 'from' param, for range queries
|
||||
* 'move' may take account balances negative
|
||||
* 'settxfee' added, to manually set TX fee
|
||||
|
|
@ -1,10 +0,0 @@
|
|||
Win32, Linux, MacOSX and source releases for bitcoin v0.3.23 have been uploaded to
|
||||
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.23/
|
||||
|
||||
This is another quick bugfix release, trying to deal with the influx of new bitcoin users.
|
||||
|
||||
Main items of note:
|
||||
|
||||
* P2P connect-to-node logic changed to reduce timeout a bit. The network saw a huge influx of new users, who do not permit incoming connections. This change is a short-term hack, to more quickly hunt for useful P2P connections. Better "leaf node" logic is in the works, but this should let us limp along until then. One may use -upnp to properly forward ports, and help the network.
|
||||
* Transaction fee reduced to 0.0005 for new transactions
|
||||
* Client will relay transactions with fees as low as 0.0001 BTC
|
||||
|
|
@ -1,20 +0,0 @@
|
|||
Bitcoin v0.3.24 is now available for download at
|
||||
https://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.3.24/
|
||||
|
||||
This is another bug fix release. We had hoped to have wallet encryption ready for release, but more urgent fixes for existing clients were needed -- most notably block download problems were getting severe. Wallet encryption is ready for testing at https://github.com/bitcoin/bitcoin/pull/352 for the git-savvy, and hopefully will follow shortly in the next release, v0.4.
|
||||
|
||||
Notable fixes in v0.3.24, and the main reasons for this release:
|
||||
|
||||
F1) Block downloads were failing or taking unreasonable amounts of time to complete, because the increased size of the block chain was bumping up against some earlier buffer-size DoS limits.
|
||||
|
||||
F2) Fix crash caused by loss/lack of network connection.
|
||||
|
||||
Notable changes in v0.3.24:
|
||||
|
||||
C1) DNS seeding enabled by default.
|
||||
|
||||
C2) UPNP enabled by default in the GUI client. The percentage of bitcoin clients that accept incoming connections is quite small, and that is a problem. This should help. bitcoind, and unofficial builds, are unchanged (though we encourage use of "-upnp" to help the network!)
|
||||
|
||||
C3) Initial unit testing framework. Bitcoin sorely needs automated tests, and this is a beginning. Contributions welcome.
|
||||
|
||||
C4) Internal wallet code cleanup. While invisible to an end user, this change provides the basis for v0.4's wallet encryption.
|
||||
|
|
@ -1,70 +0,0 @@
|
|||
Bitcoin version 0.4.0 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.0/
|
||||
|
||||
The main feature in this release is wallet private key encryption;
|
||||
you can set a passphrase that must be entered before sending coins.
|
||||
See below for more information; if you decide to encrypt your wallet,
|
||||
WRITE DOWN YOUR PASSPHRASE AND PUT IT IN A SECURE LOCATION. If you
|
||||
forget or lose your wallet passphrase, you lose your bitcoins.
|
||||
Previous versions of bitcoin are unable to read encrypted wallets,
|
||||
and will crash on startup if the wallet is encrypted.
|
||||
|
||||
Also note: bitcoin version 0.4 uses a newer version of Berkeley DB
|
||||
(bdb version 4.8) than previous versions (bdb 4.7). If you upgrade
|
||||
to version 0.4 and then revert back to an earlier version of bitcoin
|
||||
the it may be unable to start because bdb 4.7 cannot read bdb 4.8
|
||||
"log" files.
|
||||
|
||||
|
||||
Notable bug fixes from version 0.3.24:
|
||||
|
||||
Fix several bitcoin-becomes-unresponsive bugs due to multithreading
|
||||
deadlocks.
|
||||
|
||||
Optimize database writes for large (lots of inputs) transactions
|
||||
(fixes a potential denial-of-service attack)
|
||||
|
||||
|
||||
Wallet Encryption
|
||||
|
||||
Bitcoin supports native wallet encryption so that people who steal your
|
||||
wallet file don't automatically get access to all of your Bitcoins.
|
||||
In order to enable this feature, choose "Encrypt Wallet" from the
|
||||
Options menu. You will be prompted to enter a passphrase, which
|
||||
will be used as the key to encrypt your wallet and will be needed
|
||||
every time you wish to send Bitcoins. If you lose this passphrase,
|
||||
you will lose access to spend all of the bitcoins in your wallet,
|
||||
no one, not even the Bitcoin developers can recover your Bitcoins.
|
||||
This means you are responsible for your own security, store your
|
||||
passphrase in a secure location and do not forget it.
|
||||
|
||||
Remember that the encryption built into bitcoin only encrypts the
|
||||
actual keys which are required to send your bitcoins, not the full
|
||||
wallet. This means that someone who steals your wallet file will
|
||||
be able to see all the addresses which belong to you, as well as the
|
||||
relevant transactions, you are only protected from someone spending
|
||||
your coins.
|
||||
|
||||
It is recommended that you backup your wallet file before you
|
||||
encrypt your wallet. To do this, close the Bitcoin client and
|
||||
copy the wallet.dat file from ~/.bitcoin/ on Linux, /Users/(user
|
||||
name)/Application Support/Bitcoin/ on Mac OSX, and %APPDATA%/Bitcoin/
|
||||
on Windows (that is /Users/(user name)/AppData/Roaming/Bitcoin on
|
||||
Windows Vista and 7 and /Documents and Settings/(user name)/Application
|
||||
Data/Bitcoin on Windows XP). Once you have copied that file to a
|
||||
safe location, reopen the Bitcoin client and Encrypt your wallet.
|
||||
If everything goes fine, delete the backup and enjoy your encrypted
|
||||
wallet. Note that once you encrypt your wallet, you will never be
|
||||
able to go back to a version of the Bitcoin client older than 0.4.
|
||||
|
||||
Keep in mind that you are always responsible for your own security.
|
||||
All it takes is a slightly more advanced wallet-stealing trojan which
|
||||
installs a keylogger to steal your wallet passphrase as you enter it
|
||||
in addition to your wallet file and you have lost all your Bitcoins.
|
||||
Wallet encryption cannot keep you safe if you do not practice
|
||||
good security, such as running up-to-date antivirus software, only
|
||||
entering your wallet passphrase in the Bitcoin client and using the
|
||||
same passphrase only as your wallet passphrase.
|
||||
|
||||
See the doc/README file in the bitcoin source for technical details
|
||||
of wallet encryption.
|
||||
|
|
@ -1,38 +0,0 @@
|
|||
Bitcoin version 0.4.1 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.4.1/
|
||||
|
||||
This is a bugfix only release based on 0.4.0.
|
||||
|
||||
Please report bugs by replying to this forum thread.
|
||||
|
||||
MAJOR BUG FIX (CVE-2011-4447)
|
||||
|
||||
The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
|
||||
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
|
||||
associated coins.
|
||||
|
||||
If you have a previously encrypted wallet.dat, the first time you run wxbitcoin or bitcoind the wallet will be rewritten, Bitcoin will
|
||||
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.
|
||||
|
||||
If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
|
||||
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.
|
||||
|
||||
Wallets encrypted with this version of Bitcoin are written properly.
|
||||
|
||||
Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
|
||||
new private keys are properly backed up you should:
|
||||
|
||||
1. Run Bitcoin and let it rewrite the wallet.dat file
|
||||
|
||||
2. Run it again, then ask it for a new bitcoin address.
|
||||
wxBitcoin: new address visible on main window
|
||||
bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet, then run the 'getnewaddress' RPC command.
|
||||
|
||||
3. If your encrypted wallet.dat may have been copied or stolen, send all of your bitcoins to the new bitcoin address.
|
||||
|
||||
4. Shut down Bitcoin, then backup the wallet.dat file.
|
||||
IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.
|
||||
|
||||
"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.
|
||||
|
||||
Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.
|
||||
|
|
@ -1 +0,0 @@
|
|||
Never released or release notes were lost.
|
||||
|
|
@ -1,21 +0,0 @@
|
|||
bitcoind version 0.4.3 is now available for download at:
|
||||
http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.4.3/ (until Gavin uploads to SourceForge)
|
||||
|
||||
This is a bugfix-only release based on 0.4.0.
|
||||
|
||||
Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.
|
||||
|
||||
Please report bugs for the daemon only using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Stable source code is hosted at Gitorious:
|
||||
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.4.3#.tar.gz
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download).
|
||||
Fixed some address-handling deadlocks (client freezes).
|
||||
No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak).
|
||||
Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed).
|
||||
Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).
|
||||
|
||||
|
|
@ -1,30 +0,0 @@
|
|||
Bitcoin version 0.4.4 is now available for download at:
|
||||
http://luke.dashjr.org/programs/bitcoin/files/bitcoind-0.4.4/
|
||||
|
||||
This is a bugfix-only release based on 0.4.0.
|
||||
|
||||
Please note that the wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.
|
||||
|
||||
Please report bugs for the daemon only using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Stable source code is hosted at Gitorious:
|
||||
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.4.4#.tar.gz
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all.
|
||||
Fix possible buffer overflow on systems with very long application data paths. This is not exploitable.
|
||||
Resolved multiple bugs preventing long-term unlocking of encrypted wallets (issue #922).
|
||||
Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable.
|
||||
Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting.
|
||||
Various memory leaks and potential null pointer deferences have been
|
||||
fixed.
|
||||
Several shutdown issues have been fixed.
|
||||
Check that keys stored in the wallet are valid at startup, and if not,
|
||||
report corruption.
|
||||
Various build fixes.
|
||||
If no password is specified to bitcoind, recommend a secure password.
|
||||
Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0.
|
||||
Add checkpoint at block 168,000.
|
||||
|
||||
|
|
@ -1 +0,0 @@
|
|||
Never released or release notes were lost.
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
bitcoind version 0.4.6 is now available for download at:
|
||||
Windows: installer | zip (sig)
|
||||
Source: tar.gz
|
||||
bitcoind and Bitcoin-Qt version 0.6.0.7 are also tagged in git, but it is recommended to upgrade to 0.6.1.
|
||||
|
||||
These are bugfix-only releases.
|
||||
|
||||
Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
|
||||
Verify status of encrypt/decrypt calls to detect failed padding
|
||||
Check blocks for duplicate transactions earlier. Fixes #1167
|
||||
Upgrade Windows builds to OpenSSL 1.0.1b
|
||||
Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
|
||||
JSON-RPC listtransactions's from/count handling is now fixed
|
||||
Optimize and fix multithreaded access, when checking whether we already know about transactions
|
||||
Fix potential networking deadlock
|
||||
Proper support for Growl 1.3 notifications
|
||||
Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
|
||||
Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
|
||||
Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
|
||||
Missing error condition checking added
|
||||
Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
|
||||
Increase time ago of last block for "up to date" status from 30 to 90 minutes
|
||||
Show a message box when runaway exception happens (Bitcoin-Qt)
|
||||
Use a messagebox to display the error when -server is provided without providing a rpc password
|
||||
Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
|
||||
Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
|
||||
Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
|
||||
Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
|
||||
Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
|
||||
Work around issue in boost::program_options that prevents from compiling in clang
|
||||
Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
|
||||
Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
|
||||
Various trivial internal corrections to types used for counting/size loops and warnings
|
||||
|
|
@ -1,70 +0,0 @@
|
|||
Bitcoin version 0.5.0 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.0/
|
||||
|
||||
The major change for this release is a completely new graphical interface that uses the Qt user interface toolkit.
|
||||
|
||||
This release include German, Spanish, Spanish-Castilian, Norwegian and Dutch translations. More translations are welcome; join the project at Transifex if you can help:
|
||||
https://www.transifex.net/projects/p/bitcoin/
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
For Ubuntu users, there is a new ppa maintained by Matt Corallo which you can add to your system so that it will automatically keep bitcoin up-to-date. Just type "sudo apt-add-repository ppa:bitcoin/bitcoin" in your terminal, then install the bitcoin-qt package.
|
||||
|
||||
MAJOR BUG FIX (CVE-2011-4447)
|
||||
|
||||
The wallet encryption feature introduced in Bitcoin version 0.4.0 did not sufficiently secure the private keys. An attacker who
|
||||
managed to get a copy of your encrypted wallet.dat file might be able to recover some or all of the unencrypted keys and steal the
|
||||
associated coins.
|
||||
|
||||
If you have a previously encrypted wallet.dat, the first time you run bitcoin-qt or bitcoind the wallet will be rewritten, Bitcoin will
|
||||
shut down, and you will be prompted to restart it to run with the new, properly encrypted file.
|
||||
|
||||
If you had a previously encrypted wallet.dat that might have been copied or stolen (for example, you backed it up to a public
|
||||
location) you should send all of your bitcoins to yourself using a new bitcoin address and stop using any previously generated addresses.
|
||||
|
||||
Wallets encrypted with this version of Bitcoin are written properly.
|
||||
|
||||
Technical note: the encrypted wallet's 'keypool' will be regenerated the first time you request a new bitcoin address; to be certain that the
|
||||
new private keys are properly backed up you should:
|
||||
|
||||
1. Run Bitcoin and let it rewrite the wallet.dat file
|
||||
|
||||
2. Run it again, then ask it for a new bitcoin address.
|
||||
Bitcoin-Qt: Address Book, then New Address...
|
||||
bitcoind: run the 'walletpassphrase' RPC command to unlock the wallet, then run the 'getnewaddress' RPC command.
|
||||
|
||||
3. If your encrypted wallet.dat may have been copied or stolen, send all of your bitcoins to the new bitcoin address.
|
||||
|
||||
4. Shut down Bitcoin, then backup the wallet.dat file.
|
||||
IMPORTANT: be sure to request a new bitcoin address before backing up, so that the 'keypool' is regenerated and backed up.
|
||||
|
||||
"Security in depth" is always a good idea, so choosing a secure location for the backup and/or encrypting the backup before uploading it is recommended. And as in previous releases, if your machine is infected by malware there are several ways an attacker might steal your bitcoins.
|
||||
|
||||
Thanks to Alan Reiner (etotheipi) for finding and reporting this bug.
|
||||
|
||||
MAJOR GUI CHANGES
|
||||
|
||||
"Splash" graphics at startup that show address/wallet/blockchain loading progress.
|
||||
|
||||
"Synchronizing with network" progress bar to show block-chain download progress.
|
||||
|
||||
Icons at the bottom of the window that show how well connected you are to the network, with tooltips to display details.
|
||||
|
||||
Drag and drop support for bitcoin: URIs on web pages.
|
||||
|
||||
Export transactions as a .csv file.
|
||||
|
||||
Many other GUI improvements, large and small.
|
||||
|
||||
RPC CHANGES
|
||||
|
||||
getmemorypool : new RPC command, provides everything needed to construct a block with a custom generation transaction and submit a solution
|
||||
|
||||
listsinceblock : new RPC command, list transactions since given block
|
||||
|
||||
signmessage/verifymessage : new RPC commands to sign a message with one of your private keys or verify that a message signed by the private key associated with a bitcoin address.
|
||||
|
||||
GENERAL CHANGES
|
||||
|
||||
Faster initial block download.
|
||||
|
|
@ -1,43 +0,0 @@
|
|||
Bitcoin version 0.5.1 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.1/
|
||||
|
||||
This is a bugfix-only release.
|
||||
|
||||
This release includes 13 translations, including 5 new translations:
|
||||
Italian, Hungarian, Ukranian, Portuguese (Brazilian) and Simplified Chinese.
|
||||
More translations are welcome; join the project at Transifex if you can help:
|
||||
https://www.transifex.net/projects/p/bitcoin/
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Project source code is hosted at github; we are no longer
|
||||
distributing .tar.gz files here, you can get them
|
||||
directly from github:
|
||||
https://github.com/bitcoin/bitcoin/tarball/v0.5.1 # .tar.gz
|
||||
https://github.com/bitcoin/bitcoin/zipball/v0.5.1 # .zip
|
||||
|
||||
For Ubuntu users, there is a new ppa maintained by Matt Corallo which
|
||||
you can add to your system so that it will automatically keep
|
||||
bitcoin up-to-date. Just type
|
||||
sudo apt-add-repository ppa:bitcoin/bitcoin
|
||||
in your terminal, then install the bitcoin-qt package.
|
||||
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Re-enable SSL support for the JSON-RPC interface (it was unintentionally
|
||||
disabled for the 0.5.0 release binaries).
|
||||
|
||||
The code that finds peers via "dns seeds" no longer stops bitcoin startup
|
||||
if one of the dns seed machines is down.
|
||||
|
||||
Tooltips on the transaction list view were rendering incorrectly (as black boxes
|
||||
or with a transparent background).
|
||||
|
||||
Prevent a denial-of-service attack involving flooding a bitcoin node with
|
||||
orphan blocks.
|
||||
|
||||
The wallet passphrase dialog now warns you if the caps lock key was pressed.
|
||||
|
||||
Improved searching in addresses and labels in bitcoin-qt.
|
||||
|
|
@ -1,22 +0,0 @@
|
|||
Bitcoin version 0.5.2 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.2/
|
||||
|
||||
This is a bugfix-only release based on 0.5.1.
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Stable source code is hosted at Gitorious:
|
||||
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.2#.tar.gz
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Check all transactions in blocks after the last checkpoint (0.5.0 and 0.5.1 skipped checking ECDSA signatures during initial blockchain download).
|
||||
Cease locking memory used by non-sensitive information (this caused a huge performance hit on some platforms, especially noticable during initial blockchain download; this was
|
||||
not a security vulnerability).
|
||||
Fixed some address-handling deadlocks (client freezes).
|
||||
No longer accept inbound connections over the internet when Bitcoin is being used with Tor (identity leak).
|
||||
Re-enable SSL support for the JSON-RPC interface (it was unintentionally disabled for the 0.5.0 and 0.5.1 release Linux binaries).
|
||||
Use the correct base transaction fee of 0.0005 BTC for accepting transactions into mined blocks (since 0.4.0, it was incorrectly accepting 0.0001 BTC which was only meant to be relayed).
|
||||
Don't show "IP" for transactions which are not necessarily IP transactions.
|
||||
Add new DNS seeds (maintained by Pieter Wuille and Luke Dashjr).
|
||||
|
|
@ -1,42 +0,0 @@
|
|||
Bitcoin version 0.5.3 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.3/
|
||||
|
||||
This is a bugfix-only release based on 0.5.1.
|
||||
It also includes a few protocol updates.
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Stable source code is hosted at Gitorious:
|
||||
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.3#.tar.gz
|
||||
|
||||
PROTOCOL UPDATES
|
||||
|
||||
BIP 30: Introduce a new network rule: "a block is not valid if it contains a transaction whose hash already exists in the block chain, unless all that transaction's outputs were already spent before said block" beginning on March 15, 2012, 00:00 UTC.
|
||||
On testnet, allow mining of min-difficulty blocks if 20 minutes have gone by without mining a regular-difficulty block. This is to make testing Bitcoin easier, and will not affect normal mode.
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Limit the number of orphan transactions stored in memory, to prevent a potential denial-of-service attack by flooding orphan transactions. Also never store invalid transactions at all.
|
||||
Fix possible buffer overflow on systems with very long application data paths. This is not exploitable.
|
||||
Resolved multiple bugs preventing long-term unlocking of encrypted wallets
|
||||
(issue #922).
|
||||
Only send local IP in "version" messages if it is globally routable (ie, not private), and try to get such an IP from UPnP if applicable.
|
||||
Reannounce UPnP port forwards every 20 minutes, to workaround routers expiring old entries, and allow the -upnp option to override any stored setting.
|
||||
Skip splash screen when -min is used, and fix Minimize to Tray function.
|
||||
Do not blank "label" in Bitcoin-Qt "Send" tab, if the user has already entered something.
|
||||
Correct various labels and messages.
|
||||
Various memory leaks and potential null pointer deferences have been fixed.
|
||||
Handle invalid Bitcoin URIs using "bitcoin://" instead of "bitcoin:".
|
||||
Several shutdown issues have been fixed.
|
||||
Revert to "global progress indication", as starting from zero every time was considered too confusing for many users.
|
||||
Check that keys stored in the wallet are valid at startup, and if not, report corruption.
|
||||
Enable accessible widgets on Windows, so that people with screen readers such as NVDA can make sense of it.
|
||||
Various build fixes.
|
||||
If no password is specified to bitcoind, recommend a secure password.
|
||||
Automatically focus and scroll to new "Send coins" entries in Bitcoin-Qt.
|
||||
Show a message box for --help on Windows, for Bitcoin-Qt.
|
||||
Add missing "About Qt" menu option to show built-in Qt About dialog.
|
||||
Don't show "-daemon" as an option for Bitcoin-Qt, since it isn't available.
|
||||
Update hard-coded fallback seed nodes, choosing recent ones with long uptime and versions at least 0.4.0.
|
||||
Add checkpoint at block 168,000.
|
||||
|
|
@ -1,39 +0,0 @@
|
|||
Bitcoin version 0.5.4 is now available for download at:
|
||||
http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.5.4/
|
||||
NOTE: 0.5.4rc3 is being renamed to 0.5.4 final with no changes.
|
||||
|
||||
This is a bugfix-only release in the 0.5.x series, plus a few protocol updates.
|
||||
|
||||
Please report bugs using the issue tracker at github:
|
||||
https://github.com/bitcoin/bitcoin/issues
|
||||
|
||||
Stable source code is hosted at Gitorious:
|
||||
http://gitorious.org/bitcoin/bitcoind-stable/archive-tarball/v0.5.4#.tar.gz
|
||||
|
||||
PROTOCOL UPDATES
|
||||
|
||||
BIP 16: Special-case "pay to script hash" logic to enable minimal validation of new transactions.
|
||||
Support for validating message signatures produced with compressed public keys.
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Build with thread-safe MingW libraries for Windows, fixing a dangerous memory corruption scenario when exceptions are thrown.
|
||||
Fix broken testnet mining.
|
||||
Stop excess inventory relay during initial block download.
|
||||
When disconnecting a node, clear the received buffer so that we do not process any already received messages.
|
||||
Yet another attempt at implementing "minimize to tray" that works on all operating systems.
|
||||
Fix Bitcoin-Qt notifications under Growl 1.3.
|
||||
Increase required age of Bitcoin-Qt's "not up to date" status from 30 to 90 minutes.
|
||||
Implemented missing verifications that led to crash on entering some wrong passphrases for encrypted wallets.
|
||||
Fix default filename suffixes in GNOME save dialog.
|
||||
Make the "Send coins" tab use the configured unit type, even on the first attempt.
|
||||
Print detailed wallet loading errors to debug.log when it is corrupt.
|
||||
Allocate exactly the amount of space needed for signing transactions, instead of a fixed 10k buffer.
|
||||
Workaround for improbable memory access violation.
|
||||
Check wallet's minimum version before trying to load it.
|
||||
Remove wxBitcoin properly when installing Bitcoin-Qt over it. (Windows)
|
||||
Detail reorganization information better in debug log.
|
||||
Use a messagebox to display the error when -server is provided without configuring a RPC password.
|
||||
Testing suite build now honours provided CXXFLAGS.
|
||||
Removed an extraneous line-break in mature transaction tooltips.
|
||||
Fix some grammatical errors in translation process documentation.
|
||||
|
|
@ -1,37 +0,0 @@
|
|||
bitcoind and Bitcoin-Qt version 0.5.5 are now available for download at:
|
||||
Windows: installer | zip (sig)
|
||||
Source: tar.gz
|
||||
bitcoind and Bitcoin-Qt version 0.6.0.7 are also tagged in git, but it is recommended to upgrade to 0.6.1.
|
||||
|
||||
These are bugfix-only releases.
|
||||
|
||||
Please report bugs by replying to this forum thread. Note that the 0.4.x wxBitcoin GUI client is no longer maintained nor supported. If someone would like to step up to maintain this, they should contact Luke-Jr.
|
||||
|
||||
BUG FIXES
|
||||
|
||||
Version 0.6.0 allowed importing invalid "private keys", which would be unspendable; 0.6.0.7 will now verify the private key is valid, and refuse to import an invalid one
|
||||
Verify status of encrypt/decrypt calls to detect failed padding
|
||||
Check blocks for duplicate transactions earlier. Fixes #1167
|
||||
Upgrade Windows builds to OpenSSL 1.0.1b
|
||||
Set label when selecting an address that already has a label. Fixes #1080 (Bitcoin-Qt)
|
||||
JSON-RPC listtransactions's from/count handling is now fixed
|
||||
Optimize and fix multithreaded access, when checking whether we already know about transactions
|
||||
Fix potential networking deadlock
|
||||
Proper support for Growl 1.3 notifications
|
||||
Display an error, rather than crashing, if encoding a QR Code failed (0.6.0.7)
|
||||
Don't erroneously set "Display addresses" for users who haven't explicitly enabled it (Bitcoin-Qt)
|
||||
Some non-ASCII input in JSON-RPC expecting hexadecimal may have been misinterpreted rather than rejected
|
||||
Missing error condition checking added
|
||||
Do not show green tick unless all known blocks are downloaded. Fixes #921 (Bitcoin-Qt)
|
||||
Increase time ago of last block for "up to date" status from 30 to 90 minutes
|
||||
Show a message box when runaway exception happens (Bitcoin-Qt)
|
||||
Use a messagebox to display the error when -server is provided without providing a rpc password
|
||||
Show error message instead of exception crash when unable to bind RPC port (Bitcoin-Qt)
|
||||
Correct sign message bitcoin address tooltip. Fixes #1050 (Bitcoin-Qt)
|
||||
Removed "(no label)" from QR Code dialog titlebar if we have no label (0.6.0.7)
|
||||
Removed an ugly line break in tooltip for mature transactions (0.6.0.7)
|
||||
Add missing tooltip and key shortcut in settings dialog (part of #1088) (Bitcoin-Qt)
|
||||
Work around issue in boost::program_options that prevents from compiling in clang
|
||||
Fixed bugs occurring only on platforms with unsigned characters (such as ARM).
|
||||
Rename make_windows_icon.py to .sh as it is a shell script. Fixes #1099 (Bitcoin-Qt)
|
||||
Various trivial internal corrections to types used for counting/size loops and warnings
|
||||
57
doc/release-notes/release-notes-1.7.0.md
Normal file
57
doc/release-notes/release-notes-1.7.0.md
Normal file
|
|
@ -0,0 +1,57 @@
|
|||
# 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,
|
||||
with the same Scrypt PoW algorithm, same reward schedule, but there are 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 the risk 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 <command>", 1.7 adopts the model from Bitcoin Core 0.9 where there is
|
||||
a separate "dogecoin-cli" executable which is 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 with 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 "TestDoge" is essentially valueless, it can be acquired easily for testing,
|
||||
either by mining, or from a faucet such as http://testdoge.lionservers.de/
|
||||
99
doc/release-notes/release-notes-1.8.0.md
Normal file
99
doc/release-notes/release-notes-1.8.0.md
Normal file
|
|
@ -0,0 +1,99 @@
|
|||
# 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.0.0/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.
|
||||
Loading…
Reference in a new issue