lbrycrd/doc/release-notes.md

(note: this is a temporary file, to be added-to by anybody, and moved to
release-notes at release time)

Notable changes
===============

Random-cookie RPC authentication
---------------------------------

When no `-rpcpassword` is specified, the daemon now uses a special 'cookie'
file for authentication. This file is generated with random content when the
daemon starts, and deleted when it exits. Its contents are used as
authentication token. Read access to this file controls who can access through
RPC. By default it is stored in the data directory but its location can be
overridden with the option `-rpccookiefile`.

This is similar to Tor's CookieAuthentication: see
https://www.torproject.org/docs/tor-manual.html.en

This allows running bitcoind without having to do any manual configuration.

Low-level RPC API changes
--------------------------

- Monetary amounts can be provided as strings. This means that for example the
  argument to sendtoaddress can be "0.0001" instead of 0.0001. This can be an
  advantage if a JSON library insists on using a lossy floating point type for
  numbers, which would be dangerous for monetary amounts.

Option parsing behavior
-----------------------

Command line options are now parsed strictly in the order in which they are
specified. It used to be the case that `-X -noX` ends up, unintuitively, with X
set, as `-X` had precedence over `-noX`. This is no longer the case. Like for
other software, the last specified value for an option will hold.

0.12.0 Change log
=================

Detailed release notes follow. This overview includes changes that affect
behavior, not code moves, refactors and string updates. For convenience in locating
the code changes and accompanying discussion, both the pull request and
git merge commit are mentioned.

### RPC and REST

### Configuration and command-line options

### Block and transaction handling

### P2P protocol and network code

### Validation

### Build system

### Wallet

### GUI

### Tests

### Miscellaneous

- Removed bitrpc.py from contrib
doc: Empty release notes for next release Now that 0.9 is branched off, the new release notes for 0.10 or 0.11 or 1.0 should be added here. Edits to preliminary 0.9.0 release notes should be made in the 0.9.0 branch. 2014-03-03 09:41:18 +01:00			`(note: this is a temporary file, to be added-to by anybody, and moved to`
			`release-notes at release time)`
estimatefee / estimatepriority RPC methods New RPC methods: return an estimate of the fee (or priority) a transaction needs to be likely to confirm in a given number of blocks. Mike Hearn created the first version of this method for estimating fees. It works as follows: For transactions that took 1 to N (I picked N=25) blocks to confirm, keep N buckets with at most 100 entries in each recording the fees-per-kilobyte paid by those transactions. (separate buckets are kept for transactions that confirmed because they are high-priority) The buckets are filled as blocks are found, and are saved/restored in a new fee_estiamtes.dat file in the data directory. A few variations on Mike's initial scheme: To estimate the fee needed for a transaction to confirm in X buckets, all of the samples in all of the buckets are used and a median of all of the data is used to make the estimate. For example, imagine 25 buckets each containing the full 100 entries. Those 2,500 samples are sorted, and the estimate of the fee needed to confirm in the very next block is the 50'th-highest-fee-entry in that sorted list; the estimate of the fee needed to confirm in the next two blocks is the 150'th-highest-fee-entry, etc. That algorithm has the nice property that estimates of how much fee you need to pay to get confirmed in block N will always be greater than or equal to the estimate for block N+1. It would clearly be wrong to say "pay 11 uBTC and you'll get confirmed in 3 blocks, but pay 12 uBTC and it will take LONGER". A single block will not contribute more than 10 entries to any one bucket, so a single miner and a large block cannot overwhelm the estimates. 2014-03-17 13:19:54 +01:00
Autoprune release notes included 2015-05-26 21:32:25 +02:00			`Notable changes`
			`===============`

doc: mention RPC random cookie authentication in release notes 2015-07-13 13:31:38 +02:00			`Random-cookie RPC authentication`
			`---------------------------------`

			When no `-rpcpassword` is specified, the daemon now uses a special 'cookie'
			`file for authentication. This file is generated with random content when the`
			`daemon starts, and deleted when it exits. Its contents are used as`
			`authentication token. Read access to this file controls who can access through`
			`RPC. By default it is stored in the data directory but its location can be`
			overridden with the option `-rpccookiefile`.

			`This is similar to Tor's CookieAuthentication: see`
			`https://www.torproject.org/docs/tor-manual.html.en`

			`This allows running bitcoind without having to do any manual configuration.`

doc: Mention RPC strings for monetary amounts in release notes Add a section "low level RPC API changes" so that the changes with regard to error codes can be added later. 2015-07-27 13:56:40 +02:00			`Low-level RPC API changes`
			`--------------------------`
Autoprune release notes included 2015-05-26 21:32:25 +02:00
doc: Mention RPC strings for monetary amounts in release notes Add a section "low level RPC API changes" so that the changes with regard to error codes can be added later. 2015-07-27 13:56:40 +02:00			`- Monetary amounts can be provided as strings. This means that for example the`
			`argument to sendtoaddress can be "0.0001" instead of 0.0001. This can be an`
			`advantage if a JSON library insists on using a lossy floating point type for`
			`numbers, which would be dangerous for monetary amounts.`
Autoprune release notes included 2015-05-26 21:32:25 +02:00
doc: mention change to option parsing behavior in release notes 2015-07-27 14:54:53 +02:00			`Option parsing behavior`
			`-----------------------`

			`Command line options are now parsed strictly in the order in which they are`
			specified. It used to be the case that `-X -noX` ends up, unintuitively, with X
			set, as `-X` had precedence over `-noX`. This is no longer the case. Like for
			`other software, the last specified value for an option will hold.`

Now that 0.11 has been branched, master is 0.11.99 ... in preparation for 0.12 2015-06-01 10:33:51 +02:00			`0.12.0 Change log`
doc: Add preliminary changelog for 0.11 to release notes 2015-05-26 14:35:48 +02:00			`=================`

			`Detailed release notes follow. This overview includes changes that affect`
doc: Add to 0.11 release notes Add information about further notable changes: - Big endian support - Memory usage optimization - Disable wallet transaction broadcast - Stream isolation for Tor 2015-05-29 17:32:15 +02:00			`behavior, not code moves, refactors and string updates. For convenience in locating`
			`the code changes and accompanying discussion, both the pull request and`
			`git merge commit are mentioned.`
doc: Add preliminary changelog for 0.11 to release notes 2015-05-26 14:35:48 +02:00
			`### RPC and REST`

			`### Configuration and command-line options`

			`### Block and transaction handling`

			`### P2P protocol and network code`

			`### Validation`

			`### Build system`

			`### Wallet`

			`### GUI`

			`### Tests`

			`### Miscellaneous`

Removed contrib/bitrpc It's unclear if people are using this and if it's worth maintaining. 2015-08-03 18:36:01 +02:00			`- Removed bitrpc.py from contrib`