If TLS signed the messages with a public key, you put any TLS conversation on-chain immediately. Some web2 apis already implement signed responses that can be u

If TLS signed the messages with a public key, you put any TLS conversation on-chain immediately. Some web2 apis already implement signed responses that can be used in this way. TLS doesn't though, so you have a provenance problem. You can prove the integrity of the data but not the participants of the conversation. I'm building the piece that works with TLS to add identity verification.