wallet: make wallet.dat a file you can actually back up (#46)

* wallet: make wallet.dat a file you can actually back up

Issue #40: a wallet.dat copied out on its own will not open
anywhere else. The file is intact -- same bytes, same keys --
and the node refuses it with "Db::put: Invalid argument",
thrown from a path that aborted the process. The reporter
believes they lost funds to this, having saved the one file
anybody would think to save.

The chain, from the bottom:

_endthread() is pthread_exit() on POSIX, and glibc implements
that by throwing abi::__forced_unwind through the stack. That
is not a real exception; catching it without rethrowing is a
fatal error by contract. CATCH_PRINT_EXCEPTION ended in a bare
catch(...), so every Linux shutdown ended:

    UNKNOWN EXCEPTION  bitflash-node in ThreadSocketHandler()
    FATAL: exception not rethrown

An abort, mid-shutdown, so nothing after StopNode() ran.

Which mattered because Berkeley DB stamps every page with a
log sequence number belonging to the environment that wrote
it. Carried elsewhere, those numbers point at logs that do not
exist and BDB refuses to write. DBFlush(true) calls lsn_reset,
which is precisely the cure -- and DBFlush has been declared
since 2009 and called from nowhere. Even had it been called,
the abort stood in front of it.

So the wallet was never released from its directory, and the
one file users copy was the one file that could not travel.

Three fixes, each covering a different case:

  - Rethrow abi::__forced_unwind, and call DBFlush(true) on
    both shutdown paths. Shutdown completes, and wallet.dat is
    left portable by construction.

  - Adopt orphaned files on open: a freshly created database
    environment beside pre-existing .dat files means they came
    from elsewhere, so reset their sequence numbers. This is
    what recovers wallets already stranded by older builds --
    including, if they still hold the file, the reporter's.

  - BackupWallet(), reachable as /backupwallet=FILE, which
    checkpoints, copies, and clears the copy's sequence
    numbers. Bitcoin 0.1.0 had a backup command; this tree
    lost it in the wxWidgets removal and has shipped with no
    way to take a backup since.

DBFlush's own txn_checkpoint and lsn_reset are wrapped too --
they throw, and throwing on the way out is how this started.

Verified on Linux and Windows: shutdown exits 0 rather than
134, DBFlush runs, and a lone wallet.dat opens in an empty
directory with no exceptions and byte-identical key records
(defaultkey, key, name, setting, version) before and after.

Not addressed here, and the larger half of #40: keys are
generated as they are needed rather than derived from a seed,
so any backup is a snapshot and coins paid to addresses
created after it are not in it. /backupwallet says so on every
run. The real answer is deterministic derivation, which is a
wallet format change and its own piece of work.

* README: document what a wallet backup actually requires

The PR description claimed this section existed and it did not.

Covers the two things that cost money and are not obvious: a lone
wallet.dat is refused elsewhere because Berkeley DB ties it to the
database/ directory beside it, and every backup is a snapshot
because keys are made on demand rather than derived from a seed.

1 files changed, 31 insertions, 0 deletions

diff --git a/README.md b/README.md
index 1720c46..da8183a 100644
--- a/README.md
+++ b/README.md
@@ -69,6 +69,37 @@ backup — it holds your keys.
 
 ---
 
+## Backing up your wallet
+
+Two things about this wallet will cost you money if you do not know them. Both
+are consequences of the 0.1.0 wallet format, and neither is obvious.
+
+**Copying `wallet.dat` on its own is not a backup.** Berkeley DB ties the file
+to the environment in the `database/` subdirectory beside it, so a lone
+`wallet.dat` will not open elsewhere — the keys are all still in there, and the
+file is refused anyway. Use the built-in command, which writes a copy that
+stands on its own:
+
+```
+bitflash -backupwallet=/path/to/wallet-backup.dat
+```
+
+It loads the wallet, writes the copy, and exits without starting the node. If
+you would rather copy by hand, shut the node down first and take the **whole**
+data directory, not just `wallet.dat`.
+
+**Every backup is a snapshot, so repeat it.** Keys are generated when they are
+needed rather than derived from a seed, so a backup contains only the keys that
+existed the moment it was taken. Mine a block or receive to a new address
+afterwards, and those coins sit on-chain at an address whose private key is in
+no backup you hold. Back up again whenever you use a new address.
+
+The second point is the pre-BIP32 problem that deterministic wallets were
+invented to solve; see [#47](https://github.com/Bitflash-sh/bitflash/issues/47).
+Until that lands, repetition is the only defence.
+
+---
+
 ## Mining
 
 Open **Options** from the menu bar. Under Mining Mode: