release: bump to v1.3.1

dev is 22 commits past the v1.3.0 tag and still stamped 1.3.0, so a release built from it would be indistinguishable from v1.3.0 on the wire, in getnetworkinfo and to the wallet's updater. Bump REVISION, not MINOR: the delta is bug fixes and wallet performance. It adds no subsystem, and the new RPC-visible options (-notecachewarmup, -checknotecache) are debug-help only. configure.ac, src/clientversion.h 1.3.0 -> 1.3.1 (CLIENT_VERSION 1030150) doc/man/*.1 version strings restamped contrib/debian/changelog 1.3.1 entry src/chain.h the CLIENT_VERSION comment The man page content needs no regeneration: every option in `dragonxd --help` at 3032eb786 is already in dragonxd.1, and the two new options appear only in -help-debug. No consensus change since v1.3.0, so PROTOCOL_VERSION and MIN_PEER_PROTO_VERSION are unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-27 15:27:25 -05:00
parent 3032eb7868
commit fe988d6fbe
7 changed files with 41 additions and 12 deletions
@@ -3,7 +3,7 @@ AC_PREREQ([2.60])
 define(_CLIENT_VERSION_MAJOR, 1)
 dnl Must be kept in sync with src/clientversion.h , ugh!
 define(_CLIENT_VERSION_MINOR, 3)
-define(_CLIENT_VERSION_REVISION, 0)
+define(_CLIENT_VERSION_REVISION, 1)
 define(_CLIENT_VERSION_BUILD, 50)
 define(_ZC_BUILD_VAL, m4_if(m4_eval(_CLIENT_VERSION_BUILD < 25), 1, m4_incr(_CLIENT_VERSION_BUILD), m4_eval(_CLIENT_VERSION_BUILD < 50), 1, m4_eval(_CLIENT_VERSION_BUILD - 24), m4_eval(_CLIENT_VERSION_BUILD == 50), 1, , m4_eval(_CLIENT_VERSION_BUILD - 50)))
 define(_CLIENT_VERSION_SUFFIX, m4_if(m4_eval(_CLIENT_VERSION_BUILD < 25), 1, _CLIENT_VERSION_REVISION-beta$1, m4_eval(_CLIENT_VERSION_BUILD < 50), 1, _CLIENT_VERSION_REVISION-rc$1, m4_eval(_CLIENT_VERSION_BUILD == 50), 1, _CLIENT_VERSION_REVISION, _CLIENT_VERSION_REVISION-$1)))
@@ -1,3 +1,32 @@
+dragonx (1.3.1) stable; urgency=high
+
+  * Fix a file-descriptor double close that could corrupt wallets and block
+    files and crash the node. wolfSSL's CloseSocket macro turned every P2P
+    disconnect into a bare close() that left the socket handle set, so the
+    same fd number was closed again after another thread had reused it,
+    often for wallet.dat, a BDB log or a block file. Present in every
+    release since the 2020 move to wolfSSL.
+  * Defense in depth: block and undo files opened for reading are now
+    read-only; a wallet error while processing a block now shuts the node
+    down cleanly instead of crashing it; the BDB logs are kept when the
+    shutdown flush fails, so the next start can recover the wallet.
+  * Fix an abort on the next block after a note arrives at an address
+    imported with z_importviewingkey.
+  * Large wallets: break the replay -> witness rebuild -> kill loop. Witness
+    extension is much cheaper and parallel, the chainstate is flushed at
+    least hourly, replayed transactions keep their nullifiers (no mass
+    reseed), and the wallet locator never runs ahead of what the wallet has
+    processed.
+  * Much faster balance and note RPCs on wallets with thousands of Sapling
+    notes, through an in-memory cache of decrypted notes (warmed at startup,
+    -notecachewarmup) and by avoiding deep copies; history RPCs gather
+    Sapling keys once per call.
+  * -txindex=0 nodes now include fully shielded notes in queries with
+    minconf >= 2, so -zsweep and -consolidation now move them.
+  * No consensus change; PROTOCOL_VERSION is unchanged.
+
+ -- DragonX Developers <dev@dragonx.is>  Tue, 27 Oct 2026 12:00:00 +0000
+
 dragonx (1.3.0) stable; urgency=medium

  * RandomX stratum mining support: the daemon can serve stratum clients
@@ -1,9 +1,9 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.49.1.
-.TH DRAGONX-CLI "1" "August 2026" "dragonx-cli v1.3.0" "User Commands"
+.TH DRAGONX-CLI "1" "October 2026" "dragonx-cli v1.3.1" "User Commands"
 .SH NAME
-dragonx-cli \- manual page for dragonx-cli v1.3.0
+dragonx-cli \- manual page for dragonx-cli v1.3.1
 .SH DESCRIPTION
-DragonX RPC client version v1.3.0
+DragonX RPC client version v1.3.1
 .PP
 In order to ensure you are adequately protecting your privacy when using
 DragonX, please see <https://dragonx.is/security/>.
@@ -1,9 +1,9 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.49.1.
-.TH DRAGONX-TX "1" "August 2026" "dragonx-tx v1.3.0" "User Commands"
+.TH DRAGONX-TX "1" "October 2026" "dragonx-tx v1.3.1" "User Commands"
 .SH NAME
-dragonx-tx \- manual page for dragonx-tx v1.3.0
+dragonx-tx \- manual page for dragonx-tx v1.3.1
 .SH DESCRIPTION
-hush\-tx utility version v1.3.0
+hush\-tx utility version v1.3.1
 .SS "Usage:"
 .TP
 hush\-tx [options] <hex\-tx> [commands]
@@ -1,9 +1,9 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.49.1.
-.TH DRAGONXD "1" "August 2026" "dragonxd v1.3.0" "User Commands"
+.TH DRAGONXD "1" "October 2026" "dragonxd v1.3.1" "User Commands"
 .SH NAME
-dragonxd \- manual page for dragonxd v1.3.0
+dragonxd \- manual page for dragonxd v1.3.1
 .SH DESCRIPTION
-DragonX Daemon version v1.3.0
+DragonX Daemon version v1.3.1
 .PP
 In order to ensure you are adequately protecting your privacy when using
 DragonX, please see <https://dragonx.is/security/>.
@@ -35,7 +35,7 @@ extern bool fZindex;
 // These version thresholds control whether nSproutValue/nSaplingValue are
 // serialized in the block index. They must be <= CLIENT_VERSION or the
 // values will never be persisted, causing nChainSaplingValue to reset
-// to 0 after node restart. DragonX CLIENT_VERSION is 1030050 (v1.3.0.50).
+// to 0 after node restart. DragonX CLIENT_VERSION is 1030150 (v1.3.1.50).
 static const int SPROUT_VALUE_VERSION = 1000000;
 static const int SAPLING_VALUE_VERSION = 1000000;
 // Block-index records written at >= this version store nSaplingValue as a boost::optional
@@ -30,7 +30,7 @@
 // Must be kept in sync with configure.ac , ugh!
 #define CLIENT_VERSION_MAJOR 1
 #define CLIENT_VERSION_MINOR 3
-#define CLIENT_VERSION_REVISION 0
+#define CLIENT_VERSION_REVISION 1
 #define CLIENT_VERSION_BUILD 50

 //! Set to true for release, false for prerelease or test build