📅 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>;
Mike Hearn [ARCHIVE] /
npub17t…4qgyd
2023-06-07 15:14:51
in reply to nevent1q…4drm
Author Public Key
npub17ty4mumkv43w8wtt0xsz2jypck0gvw0j8xrcg6tpea25z2nh7meqf4qgydPublished at
2023-06-07 15:14:51Event JSON
{
"id": "816df74aadeb6021914697f1de69244a04717f275e1d867b863aeffe2e16e8f4",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686150891,
"kind": 1,
"tags": [
[
"e",
"a596a87c6af457be0f805b03270c063d690d47775921aaf8262e434ce379245e",
"",
"root"
],
[
"e",
"664d50655aedfba45aa543336c2eb9d5eace05b94958ca56f3d351be845951cf",
"",
"reply"
],
[
"p",
"3215b3d77dff1f84eeb5ad46fb1206a8d1657b3ea765a80b5489ece3a702d2bc"
]
],
"content": "📅 Original date posted:2014-03-07\n📝 Original message:\u003e\n\u003e Interesting side note: They recommend messages transmitted via NFC to\n\u003e not exceed 1 KB in order for a snappy experience. This (again) questions\n\u003e usage of bulky X.509 certificates in our payment request messages.\n\u003e Bitcoin Wallet currently does not sign payment requests, so I could not\n\u003e try how it would feel.\n\n\nI think you could just put a signed PaymentRequest into an NFC tag and try\nreading it from that. It's the same underlying radio tech so the transfer\nspeeds should be similar, I'd think.\n\nCommon X.509 certs are bigger than they need to be for sure, but a lot of\nthe bulk comes from the use of RSA rather than ECC. An RSA signature alone\ncan be 256 bytes! There's nothing that states you have to use RSA for\ncertificates and ECC certs are out there (Google uses one), but I think\nthey are harder to get hold of. I guess over time SSL will migrate to\nmostly ECC (secp256r1) based certs.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20140307/5b262a28/attachment.html\u003e",
"sig": "20e0460f405fe7688acac8ea9c6f554c7d69858d091ce6a32ee0596864c59f93c2117724abc3e75a62340809345f5474a789670f6a6f364791113fa15a1045fe"
}