Dpowcoin Core 31.3 is now available. This is a maintenance release featuring backports from Bitcoin Core on top of the 31.x branch.
⚠️ IMPORTANT! ALWAYS BACK UP YOUR WALLET DATA BEFORE ANY UPDATE. Shut down your wallet completely, then copy your
wallet.datfile to a safe place before updating. If possible, always encrypt your wallet with a strong password.
Upgrade from 31.2
If you are already running Dpowcoin Core 31.2, upgrading to 31.3 is straightforward:
- Shut down your node completely.
- Back up your
wallet.datto a safe location outside the data directory. - Install Dpowcoin Core 31.3.
- Start the node — it will continue syncing from where it left off.
No rescan or migration is required when upgrading from 31.2.
What's new in 31.3
This release brings in 22 upstream Bitcoin Core pull requests that are already part of the official 31.x branch: 19 in the first batch (private broadcast, file/socket/network fixes, transaction INV de-duplication, asmap, tests) and 3 more in the second (peer disconnection, CMake and Clang cleanups). Consensus rules are unchanged.
Chain sync metadata refreshed to height 257100
Minimum chain work, assumevalid, the checkpoint list and the AssumeUTXO entry have been
updated to block 257100 (previously 226000), together with the built-in chain transaction
statistics used for sync-progress estimates. A new node therefore skips script verification for
a much larger part of the chain during initial sync, and the progress estimate is more accurate.
The bundled asmap data (ip_asn.dat) was also refreshed.
Private broadcast hardening (-privatebroadcast)
- The feature is now explicitly marked experimental in
-helpand in thesendrawtransactionRPC documentation. The documentation now states that it provides best-effort concealment of a transaction's origin and that the transaction reaches the local mempool through normal acceptance when it is received back from the network. - Misbehaving private broadcast peers are now simply disconnected instead of being discouraged by address. These connections are short-lived and use Tor or I2P, so a shared exit address should not penalise unrelated peers.
- The
-proxyrandomizestartup warning was reworded to say that disabling it can correlate Tor circuits of private broadcast connections with other Tor connections, and how to reduce that risk.
Network and P2P fixes
- Only the misbehaving peer is disconnected. Previously, a misbehaving peer caused every connection from the same IP to be dropped (for example, all peers behind a shared Tor exit node). Now only that one connection is closed. Discouragement by address is unchanged.
- Stuck send buffers are cleaned up. A peer whose send buffer stays full for longer than the standard 20-minute inactivity timeout is now disconnected.
- Duplicate transaction announcements are ignored. Repeated txid/wtxid entries inside a
single
invmessage are now de-duplicated, which reduces wasted work from spammy peers. - The new IPv6 documentation range
3fff::/20(RFC 9637) is now treated as non-routable and is not stored or relayed as a valid address.
Large file handling
Block and undo data positions (nDataPos, nUndoPos) and block file seeking, truncation and
allocation now use 64-bit offsets throughout. This removes potential overflows on files above
2–4 GiB, particularly on Windows where long is 32-bit.
Configuration and documentation
-proxy=addr:port=NETWORKis now parsed and documented from a single list of network names (ipv4,ipv6,onion,cjdns), so the help text and the parser can no longer diverge. Network names are no longer lower-cased silently, so error messages show exactly what was typed.doc/tor.mdand the examples now useonioninstead oftor.- Updated man pages and the
dpowcoin.confexample (newassumevalidhash). - Build documentation refreshed for NetBSD and macOS; fixed unused variables in the OpenRC init script.
Build and developer changes
- CMake:
include_directories()replaced bytarget_include_directories(), and theWarnAboutGlobalPropertiesmodule removed. This fixes the-Wnon-target-directivewarning on CMake 4.5+. - Fixed an unused-private-field warning on Clang 24 (
memusage). - Avoided
pipe2on Darwin, and enlarged Boost.Test signal stacks. - New and updated tests: transaction INV de-duplication, pruned stale-fork handling,
m_blocks_unlinkedcoverage inLoadBlockIndex,-proxynetworks, send-buffer timeout; several unused variables removed from tests and fuzz harnesses.
Carried over from 31.2
The header PoW verification cache (-headerpowcachesize), the parallel header PoW check queue,
the 600-second future-block time limit and the backported fixes from the 31.2 release remain
unchanged.
See release notes on GitHub for the full changelog.
Troubleshooting
- Node won't start after upgrade — make sure you're upgrading from 31.x. If you're coming from an older release, install 31.2 first.
- Balance shows zero after upgrade — run
dpowcoin-cli rescanblockchainto rescan the chain.
Issues or questions? Use the issue tracker or join the community on the resources page.