j"1LAnZuoQdcKCkpDBKQMCgziGMoPC4VQUckMÊ<div class="post">Put things this way; if you manage (on a more or less distant future, don't know) to run sort of a shop <b>on surface web</b>* with BC, you may want:<br/><br/>» Your customers to be identifiable - to know who is paying what and handle refunds<br/>» Your customers to leave notes along with the payment.<br/>» Your customers to have a friendly address to pay to (not an IP, not an unreadable hash) - unless you run thenerdsshop.com there is.<br/>» Your customers to not be nagged.<br/><br/>For this would be obviously interesting a TLS/SSL feature. Imagine this operation:<br/><br/>Client -> send BC 50 to bcpay.mysite.com<br/>bcpay.mysite.com -> send a certificate with the store's data, client's get a popup with this server's information to confirm<br/><br/>eg:<br/>You're about to make a payment to the following Bitcoin client:<br/><br/>SITE NAME: mystore.com<br/>COMMON NAME: Payments Gateway<br/>CA VERIFIED BY: BitcoinSSL<br/><br/>Client -> Confirm ? payment is sent: payment is cancelled.<br/><br/><br/>* Tor users: Let's call it a surface web shop shipping goods to your house, so you wouldn't go there anyway. What would be the point of hide your IP while give your home address?</div> text/html
https://whatsonchain.com/tx/ec25b1aecc5ee659098d9724d483e77df257d935cb8f4c0bee2bb390e9a89f3b