doc: add release note for #31560 (named pipe support for `dumptxoutset` RPC)
What the developer wrote
Authored by Sebastian Falbesoner
doc: add release note for #31560 (named pipe support for `dumptxoutset` RPC)
What changed, and why it matters
This commit only adds a release note describing a previously merged feature: the `dumptxoutset` RPC can now write its output to a named pipe on UNIX-like systems. There is no code change, no bug fix, and no security-related content in the diff.
No action required. This is a documentation-only release note with no security implications.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates doc/release-notes-31560.md, an 8-line release note documenting PR #31560. It explains that dumptxoutset can stream raw UTXO set data to a named pipe (created via mkfifo) so another process can consume it without an intermediate disk file. The actual functional change was merged separately; this is purely documentation.
Changed components
doc/release-notes-31560.mdInspect captured patch +8 / −0
diff --git a/doc/release-notes-31560.md b/doc/release-notes-31560.md
new file mode 100644
index 00000000..07a8f779
--- /dev/null
+++ b/doc/release-notes-31560.md
@@ -0,0 +1,8 @@
+Updated RPCs
+------------
+
+- The `dumptxoutset` RPC now supports writing to a named pipe
+ on UNIX-like systems (see mkfifo(1) and mkfifo(3) man pages).
+ This allows the raw UTXO set data to be consumed directly by
+ another process (e.g., the `contrib/utxo-tools/utxo_to_sqlite.py`
+ conversion script) without first writing it to disk. (#31560)
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.