33bytes PK? (Migrating from curves => secp256k1)#113
Closed
Hello I tried switching to this smaller repo from curves. But a test that used `getPublickKey()` failed: ``` operator: equal expected: |- "b618af96fde8ba61d43dde06583e7a897256c10c1d11c4b32dc15b76726593e6" actual: |- "03b618af96fde8ba61d43dde06583e7a897256c10c1d11c4b32dc15b76726593e6" ``` 32bytes produced by `(@noble/curves).secp256k1.getPublicKey(sk)` 33bytes produced by `(@noble/secp256k1).get(publicKey(sk)` What's that first `03` byte? Can I discard it? **EDIT** after reading source, first byte is the compression-id/ y-coord ~~polarity~~ parity; But what do i do with all existing 32byte keys? How was the y-coord ~~polarity~~ parity decompressed before?
AI Analysis
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by telamon and has received 4 comments.
Add a comment
Comment form would go here