doc: add release note for submitSolution IPC changes
What changed, and why it matters
This commit only adds a release note describing a previous change to the inter-process communication (IPC) interface for submitting block solutions. It does not change any code, behavior, or configuration. There is no security issue in this documentation-only commit.
No action required. This is a documentation-only release note. Review the underlying PR #34672 separately if assessing the actual IPC behavior change.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates doc/release-notes-34672.md, documenting that BlockTemplate.submitSolution now returns additional rejection details and reports duplicate blocks as failures. The diff is purely documentation (+11 lines, 0 code changes). No executable code, protocol logic, or security controls are modified.
Changed components
doc/release-notes-34672.mdInspect captured patch +11 / −0
diff --git a/doc/release-notes-34672.md b/doc/release-notes-34672.md
new file mode 100644
index 00000000..060d9142
--- /dev/null
+++ b/doc/release-notes-34672.md
@@ -0,0 +1,11 @@
+IPC Interface
+-------------
+
+- `BlockTemplate.submitSolution` now returns `reason` and `debug` rejection
+ details in addition to the boolean result. Clients must regenerate IPC
+ bindings from the updated `mining.capnp` schema to use the new method. The
+ previous `@7` method now returns an error directing clients to update. (#34672)
+
+- `BlockTemplate.submitSolution` now reports duplicate blocks as failures with
+ `reason="duplicate"`, matching `Mining.submitBlock`, instead of returning
+ success for duplicate submissions. (#34672)
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.