On Tue, Oct 2, 2012 at 6:44 PM, Mike Hearn <[email protected]> wrote: > A simple way to solve this problem is just use the SSL identity of the > server that is taking part in the protocol, but it's not much harder
SSL itself (as opposed to using the certs as you suggest) is not non-reputablable, so it's not enough for the below concerns > A signed invoice + the blockchain transactions does this, BUT with a > major caveat: if you have not set up dispute mediation, there is > nobody to prove faultlessness to. To their prospective customer base. "I can prove to the public that you ripped me off" is protective, even if there isn't formal direct remedy available. ------------------------------------------------------------------------------ Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev _______________________________________________ Bitcoin-development mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/bitcoin-development
