You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's all zeroes, thus invalid signature. It's used in the implementation which could use MaybeUninit to avoid zeroing or, if we're too paranoid for that, there could be an internal constant ZEROED. If there's anyone actually using zeroed signatures we could make it pub.
The text was updated successfully, but these errors were encountered:
b18f5d0 Removed `Default` from `SerializedSignature` (Martin Habovstiak)
Pull request description:
`Default` was pointless, so it was replaced with internal
`from_raw_parts` method which also checks the length.
This commit also documents changes to `SerializedSignature`.
Closes#454
ACKs for top commit:
tcharding:
utACK b18f5d0
apoelstra:
ACK b18f5d0
Tree-SHA512: 5ee32160721d4d22cfe7c5dcc433bf013fc78a350e86b3d8d42c207fec7f2bf11c47fce77269ae816567be77602fdc86231d86e2c62aa2d327540056ab445842
It's all zeroes, thus invalid signature. It's used in the implementation which could use
MaybeUninit
to avoid zeroing or, if we're too paranoid for that, there could be an internal constantZEROED
. If there's anyone actually using zeroed signatures we could make itpub
.The text was updated successfully, but these errors were encountered: