From c313d6ecb945f8d908b061989d31d53cb6d0297d Mon Sep 17 00:00:00 2001 From: "Wladimir J. van der Laan" Date: Fri, 17 Oct 2014 13:11:59 +0200 Subject: [PATCH] doc: add headers first backwards compat warning --- doc/release-notes.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/doc/release-notes.md b/doc/release-notes.md index 967a39a0e..de13daf3e 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 =======================