fix(rpc)!: require proTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpc#5772
fix(rpc)!: require proTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpc#5772UdjinM6 wants to merge 3 commits into
proTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpc#5772Conversation
proTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpcproTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpc
proTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpcproTxHash to be unspecified when not asking for ENCRYPTED_CONTRIBUTIONS in quorum getdata rpc
|
Release notes + add text to "Breaking changes" section of pr? |
| @@ -730,6 +730,9 @@ static UniValue quorum_getdata(const JSONRPCRequest& request, const LLMQContext& | |||
| } else { | |||
| throw JSONRPCError(RPC_INVALID_PARAMETER, "proTxHash missing"); | |||
| } | |||
| } else if (!request.params[4].isNull()) { | |||
| // Require no proTxHash otherwise | |||
| throw JSONRPCError(RPC_INVALID_PARAMETER, "Should not specify proTxHash"); | |||
There was a problem hiding this comment.
is it easy to make functional test for this case? 🤔
PastaPastaPasta
left a comment
There was a problem hiding this comment.
will review when we branch of v21
c9752ea to
db09b6b
Compare
f635cd7 to
00a176f
Compare
00a176f to
5770763
Compare
5770763 to
f18b4e8
Compare
|
Anything blocking this? or should we merge it? |
ℹ️ Not a Bitcoin BackportThis PR is not a Bitcoin backport - it implements Dash-specific quorum functionality that doesn't exist in Bitcoin. Original Bitcoin commit: N/A (Dash-specific feature) Analysis Summary:
Reviewer Feedback Addressed:
This PR enhances the Recommendation: This PR is ready for merge as a Dash-specific enhancement. |
…PTED_CONTRIBUTIONS` in `quorum getdata` rpc
f18b4e8 to
50633c0
Compare
✅ No Merge Conflicts DetectedThis PR currently has no conflicts with other open PRs. |
50633c0 to
1db548f
Compare
Issue being fixed or feature implemented
Because when we ask for a quorum wide data only (
QUORUM_VERIFICATION_VECTOR) and not for a data about one specific MNproTxHashis not used in any way in this case and should not be provided. If it still was provided then maybe user doesn't quite understand what he is doing exactly or maybe he made a typo indataMask.What was done?
How Has This Been Tested?
Breaking Changes
quorum getdataRPC will no longer allowproTxHashto be specified whendataMaskis set to1.Checklist: