-
Notifications
You must be signed in to change notification settings - Fork 0
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
Fix address derivation from pubKey #10
Conversation
There's one issue with implementation, we can't throw the error. So, we have to assume, it's always best case when deriving the address. The error can't be thrown because we have inherit |
If we have to do this there like you're suggesting there is a larger design problem. The reason it is not throwable there is that it should always be valid by the time it reaches that point, empty is not a valid output either. Please see the original implementation for where the error for this should be thrown and how it is guaranteed to be valid thereafter: |
@metalurgical the problem is not whether I can throw the error, the problem is that the throwing error doesn't conform to the |
Yes, exactly, the address should have already been validated previously and assigned here, not trying to calculate what the address is here. Like I said, it is a larger design problem with the signing kit. |
@metalurgical I'm thinking to add the |
It still won't get rid of the |
Use uncompressed pubKey to derive the address.