-
Notifications
You must be signed in to change notification settings - Fork 104
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
client/btc: Improve ReturnCoins processing #2425
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Assuming nothing has changed from the other pr.
The same exactly |
// return 'true' but do nothing so a warning is issued below. | ||
// | ||
// See Also: btc_test.go: RawRequest case: methodLockUnspent | ||
func (wc *rpcClient) lockAllUnspent(unlock bool) error { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why accept an unlock
argument at all? Also, why name the method lock
when it unlocks?
wc.log.Warn("attempting to lock all unspent outputs 'lockunspent false'") | ||
} | ||
var rpcReturn bool | ||
err := wc.call(methodLockUnspent, anylist{unlock}, &rpcReturn) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Verified that this works for Dogecoin and Firo. Doesn't work for Zcash, but doesn't matter because #2553.
Reopen if it's important. |
Improve processing for ReturnCoins.
original pr