1 byte for good luck?
Keys are 64 bytes, right? So why does the golang implementation of secp256k1 want a 65 byte public key?
https://github.com/decred/dcrd/blob/master/dcrec/secp256k1/pubkey.go
Discussion
64 bytes is raw, 65 includes a prefix to say what kind of key it is apparently
no, 64 bytes only, it's from BIP-340
that extra byte is not going to be correct
also, no, an uncompressed ECDSA key is 64 bytes, a compressed key has only the sign of the second coordinate, only two are really needed, which is 33 bytes
65 bytes is not the length, that is a typical signature, i could be wrong, maybe there is a type byte for uncompressed ones, i never deal in uncompressed signatures as they aren't used in bitcoin, lightning or nostr
anyhow, point is if it's uncompressed pubkey then it's redundant to include any more than the 257th bit, the sign bit from the second coordinate
*uncompressed keys