From 7131c30c33c980f0ba1d37dfc6a3fbe8c319813e Mon Sep 17 00:00:00 2001
From: Bitflash <btf01@proton.me>
Date: Sat, 1 Aug 2026 12:56:16 -0300
Subject: wallet: generate keys ahead of use so a backup outlives the next
 block (#85)

The wallet made a key per address and per block mined, so a backup only ever
contained the keys that existed the moment it was taken -- mine one block and
the coin lands on a key the backup has never heard of. The README warned about
it, which is an admission rather than a fix.

Keys are now generated a hundred at a time and handed out one at a time, each
written to wallet.dat before it can be pointed at. A backup covers the next
hundred addresses. Deterministic derivation (#47) stays open; this buys back the
distance between a backup and the next mistake.
---
 src/db.cpp | 8 ++++++++
 1 file changed, 8 insertions(+)

(limited to 'src/db.cpp')

diff --git a/src/db.cpp b/src/db.cpp
index a503cae..3af87fb 100644
--- a/src/db.cpp
+++ b/src/db.cpp
@@ -636,6 +636,14 @@ bool CWalletDB::LoadWallet(vector<unsigned char>& vchDefaultKeyRet)
             {
                 ssValue >> vchDefaultKeyRet;
             }
+            else if (strType == "pool")
+            {
+                int64 nIndex;
+                ssKey >> nIndex;
+                vector<unsigned char> vchPubKey;
+                ssValue >> vchPubKey;
+                mapKeyPool[nIndex] = vchPubKey;
+            }
             else if (strType == "setting")  /// or settings or option or options or config?
             {
                 string strKey;
-- 
cgit v1.2.3