mirror of
https://github.com/seigler/dash-docs
synced 2025-07-28 18:26:13 +00:00
7d98f798ab
Gemfile:
- Upgrade to Jekyll 3.x (3.0.1 tested). This brings several new
features I want to use, most notably *collections* which allows us
to add blog-like collections. I've converted the `_releases` and
`_alerts` pages into collections, although their plugins are
maintained to handle the Download and Active Alert features.
- Upgrade to latest Kramdown.
- Lock Less at 2.4.0. This prevents breaking our Less plugin. Jekyll
3.x provides native support for SCSS, so we may want to switch to
that in time.
- Lock HTML Proofer at 2.1.0. The most recent version was taking
forever to check our pages (I never actually got it to complete).
I'll look into it when I get more time.
Makefile:
- New `make clean` command. Jekyll 3.x by default attempts to do
incremental rebuilds. The new `jekyll clean` command cleans up the
metadata necessary for than so that a full build is performed, and
this new `make clean` command is a wrapper around it so that we
automatically do full rebuilds in the relevant cases. Note: our
plugins aren't fully compatible with the incremental rebuilds, but
I'd like to fix that in the future.
- Remove WEBrick hack to enable previewing with default URL paths (/
instead of /index.html).
- Filter out compliants from Rouge
README.md:
- Now that Alerts (_alerts) are part of a collection, the file names
are no longer parsed for dates, so instructions on adding the date
to the YAML metadata have been added.
_alerts/*:
- Now that alerts are part of a collection, the file names are no
longer parsed to provide dates, so a `date:` field has been added to
the YAML metadata.
_config.yml:
- Some variables renamed per upgrade instructions.
- Switched from old default syntax highlighter Pygments to new default
Rouge. I tried to use Rouge options to keep new output as similar
to old output as possible to making diffing easy, but Rouge adds
extra CSS class info.
- Move `_alerts` and `_releases` into Jekyll 3.x "collections", which
provide the organizational features we were using plugins to
manange. I haven't removed the old plugins because we still use
some of their features (alerts.rb provides active issue and banner
features; releases.rb provides info to Download page)
- _layouts/* can no longer provide default global metadata; that is now
provided in the new `defaults:` section in _config.yml.
_layouts/*:
- Default metadata can no longer be provided in the layout files for
collections, so I've removed it and left a message to see
_config.yml.
_plugins/*:
- Remove filter_for.rb. It's completely broken on Jekyll 3.x because
of changes to Liquid which prevent adding new arguments to the
inherited Liquid::For class. Existing uses of filter_for have been
migrated to built-in for loops prefaced by sorts.
- Remove remove-html-extension.rb: at it said in the comments, this
was a temporary hack to get us to Jekyll 3.0.
_releases/*:
- Rename all the files: prefix a v to the file name so the output html
(e.g. v10.0.0.html) is the same as the source filename (e.g.
v10.0.0.md). This is necessary to migrate them to a Jekyll collection.
- Remove %v from titles: we have to explicitly set the title, like we
used to. Again required for migration to collections.
_templates/events.html & en/rss/events.rss:
- Sort events by date and then loop with regular for loop rather than
filter_for
en/alerts.html & en/rss/alerts.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
en/bitcoin-core/index.md & en/version-history.html & en/rss/releases.rss:
- Sort alerts by date and then loop with regular for loop rather than
filter_for
168 lines
5.7 KiB
Markdown
168 lines
5.7 KiB
Markdown
---
|
|
# This file is licensed under the MIT License (MIT) available on
|
|
# http://opensource.org/licenses/MIT.
|
|
# Text originally from Bitcoin Core project
|
|
# Metadata and small formatting changes from Bitcoin.org project
|
|
|
|
## Please see _releases/0.10.0.md for a release template
|
|
required_version: 0.8.1
|
|
optional_date: 2013-03-18
|
|
title: Bitcoin-Qt version 0.8.1 released
|
|
---
|
|
Bitcoin-Qt version 0.8.1 is now available from:
|
|
<http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.1/>
|
|
|
|
This is a maintenance release that adds a new network rule to avoid
|
|
a chain-forking incompatibility with versions 0.7.2 and earlier.
|
|
|
|
Please report bugs using the issue tracker at github:
|
|
<https://github.com/bitcoin/bitcoin/issues>
|
|
|
|
|
|
|
|
How to Upgrade
|
|
--------------
|
|
|
|
If you are running an older version, shut it down. Wait
|
|
until it has completely shut down (which might take a few minutes for older
|
|
versions), then run the installer (on Windows) or just copy over
|
|
/Applications/Bitcoin-Qt (on Mac) or bitcoind/bitcoin-qt (on Linux).
|
|
|
|
If you are upgrading from version 0.7.2 or earlier, the first time you
|
|
run 0.8.1 your blockchain files will be re-indexed, which will take
|
|
anywhere from 30 minutes to several hours, depending on the speed of
|
|
your machine.
|
|
|
|
0.8.1 Release notes
|
|
===================
|
|
|
|
The 0.8.1 release has just two changes from the 0.8.0 release:
|
|
|
|
1. A new block-acceptance rule that will be enforced from 21 March 2013 until
|
|
15 May 2013 to prevent accepting blocks that fail to validate on pre-0.8 peers.
|
|
|
|
2. A new compiled-in checkpoint at block number 225,430 -- the first block
|
|
of the 11 March 2013 chain fork.
|
|
|
|
|
|
0.8.0 Release notes
|
|
===================
|
|
|
|
Incompatible Changes
|
|
--------------------
|
|
|
|
This release no longer maintains a full index of historical transaction ids
|
|
by default, so looking up an arbitrary transaction using the getrawtransaction
|
|
RPC call will not work. If you need that functionality, you must run once
|
|
with -txindex=1 -reindex=1 to rebuild block-chain indices (see below for more
|
|
details).
|
|
|
|
Improvements
|
|
------------
|
|
|
|
Mac and Windows binaries are signed with certificates owned by the Bitcoin
|
|
Foundation, to be compatible with the new security features in OSX 10.8 and
|
|
Windows 8.
|
|
|
|
LevelDB, a fast, open-source, non-relational database from Google, is
|
|
now used to store transaction and block indices. LevelDB works much better
|
|
on machines with slow I/O and is faster in general. Berkeley DB is now only
|
|
used for the wallet.dat file (public and private wallet keys and transactions
|
|
relevant to you).
|
|
|
|
Pieter Wuille implemented many optimizations to the way transactions are
|
|
verified, so a running, synchronized node uses less working memory and does
|
|
much less I/O. He also implemented parallel signature checking, so if you
|
|
have a multi-CPU machine all CPUs will be used to verify transactions.
|
|
|
|
New Features
|
|
------------
|
|
|
|
"Bloom filter" support in the network protocol for sending only relevant transactions to
|
|
lightweight clients.
|
|
|
|
contrib/verifysfbinaries is a shell-script to verify that the binary downloads
|
|
at sourceforge have not been tampered with. If you are able, you can help make
|
|
everybody's downloads more secure by running this occasionally to check PGP
|
|
signatures against download file checksums.
|
|
|
|
contrib/spendfrom is a python-language command-line utility that demonstrates
|
|
how to use the "raw transactions" JSON-RPC api to send coins received from particular
|
|
addresses (also known as "coin control").
|
|
|
|
New/changed settings (command-line or bitcoin.conf file)
|
|
--------------------------------------------------------
|
|
|
|
dbcache : controls LevelDB memory usage.
|
|
|
|
par : controls how many threads to use to validate transactions. Defaults to the number
|
|
of CPUs on your machine, use -par=1 to limit to a single CPU.
|
|
|
|
txindex : maintains an extra index of old, spent transaction ids so they will be found
|
|
by the getrawtransaction JSON-RPC method.
|
|
|
|
reindex : rebuild block and transaction indices from the downloaded block data.
|
|
|
|
New JSON-RPC API Features
|
|
-------------------------
|
|
|
|
lockunspent / listlockunspent allow locking transaction outputs for a period of time so
|
|
they will not be spent by other processes that might be accessing the same wallet.
|
|
|
|
addnode / getaddednodeinfo methods, to connect to specific peers without restarting.
|
|
|
|
importprivkey now takes an optional boolean parameter (default true) to control whether
|
|
or not to rescan the blockchain for transactions after importing a new private key.
|
|
|
|
Important Bug Fixes
|
|
-------------------
|
|
|
|
Privacy leak: the position of the "change" output in most transactions was not being
|
|
properly randomized, making network analysis of the transaction graph to identify
|
|
users' wallets easier.
|
|
|
|
Zero-confirmation transaction vulnerability: accepting zero-confirmation transactions
|
|
(transactions that have not yet been included in a block) from somebody you do not
|
|
trust is still not recommended, because there will always be ways for attackers to
|
|
double-spend zero-confirmation transactions. However, this release includes a bug
|
|
fix that makes it a little bit more difficult for attackers to double-spend a
|
|
certain type ("lockTime in the future") of zero-confirmation transaction.
|
|
|
|
Dependency Changes
|
|
------------------
|
|
|
|
Qt 4.8.3 (compiling against older versions of Qt 4 should continue to work)
|
|
|
|
|
|
Thanks to everybody who contributed to the 0.8.0 release:
|
|
---------------------------------------------------------
|
|
|
|
- Alexander Kjeldaas
|
|
- Andrey Alekseenko
|
|
- Arnav Singh
|
|
- Christian von Roques
|
|
- Eric Lombrozo
|
|
- Forrest Voight
|
|
- Gavin Andresen
|
|
- Gregory Maxwell
|
|
- Jeff Garzik
|
|
- Luke Dashjr
|
|
- Matt Corallo
|
|
- Mike Cassano
|
|
- Mike Hearn
|
|
- Peter Todd
|
|
- Philip Kaufmann
|
|
- Pieter Wuille
|
|
- Richard Schwab
|
|
- Robert Backhaus
|
|
- Rune K. Svendsen
|
|
- Sergio Demian Lerner
|
|
- Wladimir J. van der Laan
|
|
- burger2
|
|
- default
|
|
- fanquake
|
|
- grimd34th
|
|
- justmoon
|
|
- redshark1802
|
|
- tucenaber
|
|
- xanatos
|