rich1.0npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3chttps://nostr.ae/npub1sgs97fe0n9wehe6zw7drcxdz4cy9yt9pfqjv8gasz5jlk4zezc0quppx3cnjumphttps://nostr.ae📅 Original date posted:2015-02-23 📝 Original message:On 02/23/2015 03:11 PM, Mike Hearn wrote: >> 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. No problem, we don't all have the same context. I may have missed prior discussion. > 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. Does this not also require the BT publication of the script for a P2SH address? e -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 473 bytes Desc: OpenPGP digital signature URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20150223/d33deef7/attachment.sig>