aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2014-10-17 13:11:59 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2014-10-21 14:56:28 +0200
commitc313d6ecb945f8d908b061989d31d53cb6d0297d (patch)
treecb294b92133c287bfcdd6caee72a64d735ebc72c /doc
parent6d3ab8564c3d4cd03e3f193d9029a4e271131edc (diff)
doc: add headers first backwards compat warning
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md21
1 files changed, 21 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 967a39a0e7..de13daf3e4 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -1,6 +1,27 @@
(note: this is a temporary file, to be added-to by anybody, and moved to
release-notes at release time)
+Block file backwards-compatibility warning
+===========================================
+
+Because release 0.10.0 makes use of headers-first synchronization and parallel
+block download, the block files and databases are not backwards-compatible
+with older versions of Bitcoin Core:
+
+* Blocks will be stored on disk out of order (in the order they are
+received, really), which makes it incompatible with some tools or
+other programs. Reindexing using earlier versions will also not work
+anymore as a result of this.
+
+* The block index database will now hold headers for which no block is
+stored on disk, which earlier versions won't support.
+
+If you want to be able to downgrade smoothly, make a backup of your entire data
+directory. Without this your node will need start syncing (or importing from
+bootstrap.dat) anew afterwards.
+
+This does not affect wallet forward or backward compatibility.
+
Transaction fee changes
=======================