{"type":"rich","version":"1.0","author_name":"npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","author_url":"https://nostr.ae/npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3c","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2015-02-23\n📝 Original message:On 02/23/2015 03:11 PM, Mike Hearn wrote:\n\u003e\u003e I don't see how you propose to treat the bitcoin address as a\n\u003e\u003e secp256k1 public key, or do you mean something else?\n\u003e\n\u003e Sorry, I skipped a step. I shouldn't make assumptions about what's\n\u003e obvious.\n\nNo problem, we don't all have the same context. I may have missed prior\ndiscussion.\n\n\u003e The server would provide the public key and the client would\n\u003e convert it to address form then match against the URI it has scanned.\n\u003e If it didn't match, stop at that point.\n\nDoes this not also require the BT publication of the script for a P2SH\naddress?\n\ne\n\n-------------- next part --------------\nA non-text attachment was scrubbed...\nName: signature.asc\nType: application/pgp-signature\nSize: 473 bytes\nDesc: OpenPGP digital signature\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150223/d33deef7/attachment.sig\u003e"}