rich1.0npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydhttps://nostr.ae/npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydnjumphttps://nostr.ae📅 Original date posted:2014-03-07 📝 Original message:> > Interesting side note: They recommend messages transmitted via NFC to > not exceed 1 KB in order for a snappy experience. This (again) questions > usage of bulky X.509 certificates in our payment request messages. > Bitcoin Wallet currently does not sign payment requests, so I could not > try how it would feel. I think you could just put a signed PaymentRequest into an NFC tag and try reading it from that. It's the same underlying radio tech so the transfer speeds should be similar, I'd think. Common X.509 certs are bigger than they need to be for sure, but a lot of the bulk comes from the use of RSA rather than ECC. An RSA signature alone can be 256 bytes! There's nothing that states you have to use RSA for certificates and ECC certs are out there (Google uses one), but I think they are harder to get hold of. I guess over time SSL will migrate to mostly ECC (secp256r1) based certs. -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140307/5b262a28/attachment.html>