1. Description

This is a part of #476.

1.1 Context & Purpose

The checks for validating reject-withdrawal-request contract call include the following is to create a report struct containing the key pieces of information about a withdrawal request. They include:

1. The request exists. Check whether the associated withdrawal request transaction is confirmed on the canonical stacks blockchain. Fail the withdrawal request if it is not on the canonical stacks blockchain.
2. The double spend check. Check whether the qualified request ID is in the bitcoin_withdrawals_outputs table, and that any of the associated txids are confirmed on the canonical bitcoin blockchain. Fail the withdrawal request if such a transaction was found.
3. The request is final. Check that we've seen six new bitcoin blocks since observing the bitcoin anchor block associated with the Stacks block confirming the withdrawal request transaction. Fail the withdrawal request if we’ve observed less than 6 bitcoin blocks since the anchor block.
4. The request is collectively rejected or expired. Check if the request does not have enough votes or if we've observed 24 new bitcoin blocks since observing the bitcoin anchor block associated with the Stacks block confirming the withdrawal request transaction. Fail otherwise.

I think that that's it. All other things are implicitly handled by the design laid out in #782.

2. Technical Details:

Validation of reject-withdrawal-request contract calls, happens inside the RejectWithdrawalV1::validate function. The task is to implement that function

2.1 Acceptance Criteria:

• We have a properly implemented function for validating reject-withdrawal-request contract call sign requests.

3. Related Issues and Pull Requests (optional):

I think that this ticket is the last part of #255