-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature]: Validate bitcoin transaction sign requests #286
Comments
@djordon hm, so based on the above, the signer not liking a single deposit/withdrawal (which maybe was accepted by all of the other signers) will cause the signer to withhold its vote on the entire sweep transaction, right? Feels kinda like the signer should sign anyway if they're part of the minority vote, otherwise if this happens continuously and sporadically it could deadlock the signers since I'm guessing they won't approve any re-attempts either? Not sure if I'm making any sense... |
Yeah that is correct.
I think I understand what your saying but I don't think that the signers should sign anyway. This is based on a couple reasons:
So, I don't think that there are any of the risks that you describe. But if we missed something, the fix is most likely with changing the coordinator's behavior. |
Context
In #285 the logic for responding to bitcoin transaction sign requests were introduced. In that PR, the signers accept all requests. However, we should ensure that the signers only respond to valid sign request. A sign request is considered valid for a signer to sign if:
max_fee
.Definition of done
The transaction signer only acknowledges valid bitcoin transactions.
The text was updated successfully, but these errors were encountered: