Bitmessage/PyBitmessage-2024-12-05
Archived
2
0
Fork 0
Code Issues 168 Pull Requests 53 Actions Packages Projects Releases 5 Wiki Activity

Updated Blind signature specification (markdown)

Peter Šurda 2020-03-28 17:12:45 +08:00
parent 3db162a906
commit ab69d3c96c
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
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 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 - 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 Private key (32B): private key is a 256 bit bignum