Mike Hearn [ARCHIVE] on Nostr: 📅 Original date posted:2015-02-23 📝 Original message:> > I don't see how you ...
📅 Original date posted:2015-02-23
📝 Original message:>
> I don't see how you propose to treat the bitcoin address as a secp256k1
> public key, or do you mean something else?
>
Sorry, I skipped a step. I shouldn't make assumptions about what's obvious.
The server would provide the public key and the client would convert it to
address form then match against the URI it has scanned. If it didn't match,
stop at that point.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <
http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150224/2bf38af1/attachment.html>
Published at
2023-06-07 15:31:06Event JSON
{
"id": "b53ca472555b0d2254e46bd093e3da6cc5dc04e6788893c16ed4258efa46dacc",
"pubkey": "f2c95df3766562e3b96b79a0254881c59e8639f23987846961cf55412a77f6f2",
"created_at": 1686151866,
"kind": 1,
"tags": [
[
"e",
"dfefe04b212481eb3fe073238ab7d32774988526d8b8bf7f8fff0d7249ebe09f",
"",
"root"
],
[
"e",
"83b11773c899860ab06f544e773ed855ec21d92a5cbc6712f91388f832125ceb",
"",
"reply"
],
[
"p",
"82205f272f995d9be742779a3c19a2ae08522ca14824c3a3b01525fb5459161e"
]
],
"content": "📅 Original date posted:2015-02-23\n📝 Original message:\u003e\n\u003e I don't see how you propose to treat the bitcoin address as a secp256k1\n\u003e public key, or do you mean something else?\n\u003e\n\nSorry, I skipped a step. I shouldn't make assumptions about what's obvious.\nThe server would provide the public key and the client would convert it to\naddress form then match against the URI it has scanned. If it didn't match,\nstop at that point.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150224/2bf38af1/attachment.html\u003e",
"sig": "e5b265498ff959798ae7b17edc54520f0e84de0d752b00780877dc14681a645c4b51d8ee1cc0706614e2622b7955b98bc3226c3c1f07cf98e486e1e8eac9fdd8"
}