Topic: BIP70 : Question about canonical representation of signed data - page 2. (Read 1934 times)
I think there should be no "optional" fields in the proto schema. The would fix the problem.
BIP70 signs the "protocol buffer" serialized data.
One big implementation problem I had, is that the same message can be encoded differently, because default fields are most of the time not serialized by protobuf implementations.
So what I'm doing, is that I'm verifying the signature against the message as I receive it, and just put the signature to empty.
This works fine, but I suspect a canonical representation of the protocol message would be easier to implement.
I see nothing specified in the BIP, am I missing something ?
One big implementation problem I had, is that the same message can be encoded differently, because default fields are most of the time not serialized by protobuf implementations.
So what I'm doing, is that I'm verifying the signature against the message as I receive it, and just put the signature to empty.
This works fine, but I suspect a canonical representation of the protocol message would be easier to implement.
I see nothing specified in the BIP, am I missing something ?
Jump to: