From 87f09adeec3c2c589d34a2902557fe4a92860a04 Mon Sep 17 00:00:00 2001 From: ValarDragon Date: Thu, 2 Aug 2018 23:27:16 -0700 Subject: [PATCH] (Squash this) Be more explicit about the exact encoding of the secp signature --- docs/architecture/adr-015-crypto-encoding.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/architecture/adr-015-crypto-encoding.md b/docs/architecture/adr-015-crypto-encoding.md index 98341127..67cce95f 100644 --- 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