Put things this way; if you manage (on a more or less distant future, don’t know) to run sort of a shop on surface web* with BC, you may want:
� Your customers to be identifiable - to know who is paying what and handle refunds � Your customers to leave notes along with the payment. � Your customers to have a friendly address to pay to (not an IP, not an unreadable hash) - unless you run thenerdsshop.com there is. � Your customers to not be nagged.
For this would be obviously interesting a TLS/SSL feature. Imagine this operation:
Client -> send BC 50 to bcpay.mysite.com bcpay.mysite.com -> send a certificate with the store’s data, client’s get a popup with this server’s information to confirm
eg: You’re about to make a payment to the following Bitcoin client:
SITE NAME: mystore.com COMMON NAME: Payments Gateway CA VERIFIED BY: BitcoinSSL
Client -> Confirm ? payment is sent: payment is cancelled.
- 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?