(Squash this) Be more explicit about the exact encoding of the secp signature

2018-08-02 23:27:16 -07:00 · 2018-08-02 23:27:16 -07:00 · 87f09adeec
parent b3a3c8a192
commit 87f09adeec
1 changed files with 2 additions and 2 deletions
--- a/docs/architecture/adr-015-crypto-encoding.md
+++ b/docs/architecture/adr-015-crypto-encoding.md
@ -59,8 +59,8 @@ Use the canonical representation for signatures.
 #### Secp256k1
 There isn't a clear canonical representation here.
 Signatures have two elements `r,s`.
-We should encode these bytes as `r || s`, where `r` and `s` are both exactly
-32 bytes long.
+These bytes are encoded as `r || s`, where `r` and `s` are both exactly
+32 bytes long, encoded big-endian.
 This is basically Ethereum's encoding, but without the leading recovery bit.

 ## Status