Add release note for #33050 and #33183 error string changes
What changed, and why it matters
This commit only adds a release note describing a previous change to error message wording in Bitcoin Core. It does not change any code, behavior, or security properties. The error strings were renamed from 'mandatory/non-mandatory-script-verify-flag' to 'block-script-verify-flag-failed' and 'mempool-script-verify-flag-failed' to make their meaning clearer. There is no security issue in this commit itself.
No action needed. This is a documentation-only commit with no security relevance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit creates doc/release-notes-33183.md, a documentation-only release note. It explains that prior PRs #33050 and #33183 changed the human-readable prefixes of transaction script validation RPC errors. No consensus, standardness, mempool, or wallet logic is modified. The change is purely a user-facing string clarification.
Changed components
doc/release-notes-33183.mdInspect captured patch +7 / −0
diff --git a/doc/release-notes-33183.md b/doc/release-notes-33183.md
new file mode 100644
index 00000000..fdc3f1fb
--- /dev/null
+++ b/doc/release-notes-33183.md
@@ -0,0 +1,7 @@
+Updated RPCs
+------------
+
+Transaction Script validation errors used to return the reason for the error prefixed by either
+"mandatory-script-verify-flag-failed" if it was a consensus error, or "non-mandatory-script-verify-flag"
+(without "-failed") if it was a standardness error. This has been changed to "block-script-verify-flag-failed"
+and "mempool-script-verify-flag-failed" for all block and mempool errors respectively.
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.