just had a remembering about how #bitcoin compactly combines the signature with the pubkey in transactions

i forget what the procedure was exactly, but it can also be done to schnorr signatures also

essentially, the normal route you have to combine the signature and pubkey to get either zero or one, true or false

the method used by bitcoin transactions (ecdsa ones, up to segwit) instead you get the pubkey when you combine the hash and the signature

someone was talking about how it's silly that nostr events have the IDs in them, well, you can even go further and bundle the pubkey into the signature, though that also means you have to omit the pubkey from the canonical form

i'm thinking, if i'm gonna make a binary form of the protocol, that i should use both features, and sign on the binary canonical form, which would require an alteration in the NIPs to designate the canonical hash derivation type

it's certainly not going to be friendly to application runtimes like the web browser, even with wasm, but that shit needs to die long ago, such a waste of resources

if you are an environmentalist and you aren't campaigning against web browsers you are a hypocrite, such a total waste