From ab69d3c96c07d2b8edaf1ee7bbe3c8d2610ec947 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Peter=20=C5=A0urda?= Date: Sat, 28 Mar 2020 17:12:45 +0800 Subject: [PATCH] Updated Blind signature specification (markdown) --- Blind-signature-specification.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Blind-signature-specification.md b/Blind-signature-specification.md index 6c0576f..e2a97f7 100644 --- a/Blind-signature-specification.md +++ b/Blind-signature-specification.md @@ -6,7 +6,7 @@ BigNum (32B): since the curve is secp256k1, the bignums are 256bits long (32 byt Eliptic curve points (33B): again, since we're using secp256k1, the coordinates X and Y are 32 bytes. We use compressed format compatible with OpenSSL's EC_POINT_set_compressed_coordinates. I tried to replicate how it's stored in other places and how OpenSSL behaves, so the data should be loadable by other software just like a bitcoin private key - the first byte is 0x02 or 0x03 (which determines which of the two Y coordinates it uses, the difference is that one is even and one is odd. Other bits are ignored by Bitmessage - and the next 32 bytes are the X coordinate (which is a bignum) +- the next 32 bytes are the X coordinate (which is a bignum) Private key (32B): private key is a 256 bit bignum