diff options
| author | Pieter Wuille <pieter.wuille@gmail.com> | 2015-08-11 21:03:31 +0200 |
|---|---|---|
| committer | Pieter Wuille <pieter.wuille@gmail.com> | 2015-09-22 18:51:07 +0200 |
| commit | 391dff16fe9ace90fc0f3308a5c63c453370e713 (patch) | |
| tree | 3337a40ad6bca7c57560c45d091bb9ebfd6523cf /doc/release-notes.md | |
| parent | e59d2a80f9167031521d882394a08b02fa9d0343 (diff) | |
Do not store Merkle branches in the wallet.
Assume that when a wallet transaction has a valid block hash and transaction position
in it, the transaction is actually there. We're already trusting wallet data in a
much more fundamental way anyway.
To prevent backward compatibility issues, a new record is used for storing the
block locator in the wallet. Old wallets will see a wallet file synchronized up
to the genesis block, and rescan automatically.
Diffstat (limited to 'doc/release-notes.md')
| -rw-r--r-- | doc/release-notes.md | 9 |
1 files changed, 9 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index a06075334a..bef9af60ef 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -105,6 +105,15 @@ In this version, it is only enforced for peers that send protocol versions removed. It is recommended to update SPV clients to check for the `NODE_BLOOM` service bit for nodes that report versions newer than 70011. +Merkle branches removed from wallet +----------------------------------- + +Previously, every wallet transaction stored a Merkle branch to prove its +presence in blocks. This wasn't being used for more than an expensive +sanity check. Since 0.12, these are no longer stored. When loading a +0.12 wallet into an older version, it will automatically rescan to avoid +failed checks. + 0.12.0 Change log ================= |