(Squash this) Be more explicit about the exact encoding of the secp signature
This commit is contained in:
parent
b3a3c8a192
commit
87f09adeec
|
@ -59,8 +59,8 @@ Use the canonical representation for signatures.
|
||||||
#### Secp256k1
|
#### Secp256k1
|
||||||
There isn't a clear canonical representation here.
|
There isn't a clear canonical representation here.
|
||||||
Signatures have two elements `r,s`.
|
Signatures have two elements `r,s`.
|
||||||
We should encode these bytes as `r || s`, where `r` and `s` are both exactly
|
These bytes are encoded as `r || s`, where `r` and `s` are both exactly
|
||||||
32 bytes long.
|
32 bytes long, encoded big-endian.
|
||||||
This is basically Ethereum's encoding, but without the leading recovery bit.
|
This is basically Ethereum's encoding, but without the leading recovery bit.
|
||||||
|
|
||||||
## Status
|
## Status
|
||||||
|
|
Loading…
Reference in New Issue