Quote from: Hyena on October 26, 2015, 10:36:40 PM

Quote from: knightdk on October 26, 2015, 10:28:45 PM

The whole request can be cryptographically signed with a X.509 certificate, but are not required to be.

You can read the full details of the bip at https://github.com/bitcoin/bips/blob/master/bip-0070.mediawiki

I think I remember when this was added and I was strongly against it since I don't think HTTPS should ever be relied on.

Quote

This BIP describes payment protocol messages encoded using Google's Protocol Buffers, authenticated using X.509 certificates, and communicated over http/https. Future BIPs might extend this payment protocol to other encodings, PKI systems, or transport protocols.

Everything in the above quote is utterly wrong and against my philosophy.

In my opinion, such messages should be exclusively deliver over the Bitcoin's own network, signed by the private keys of the sender's bitcoins, and perhaps encrypted using the message receiver's public key (PGP over Bitcoin). Is it technically possible? I don't know, but it should be, since Bitcoin utilizes PKI and PGP is based on that.

to cite yourself:

Quote

Who are you to dictate what is proper and what is not anyway?

IMHO creating unspendable outputs and bloating the UTXO is bad. it puts a burden for everyone and forever. no fee can cover that.