From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UkdUd-0000uJ-7c for bitcoin-development@lists.sourceforge.net; Thu, 06 Jun 2013 16:56:55 +0000 Received: from mail-lb0-f176.google.com ([209.85.217.176]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UkdUb-0006sV-A4 for bitcoin-development@lists.sourceforge.net; Thu, 06 Jun 2013 16:56:55 +0000 Received: by mail-lb0-f176.google.com with SMTP id z5so3313722lbh.35 for ; Thu, 06 Jun 2013 09:56:46 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding:x-gm-message-state; bh=TAA0jG31PGsHh4uDH+htvLvCI7F1jt4cfWXGhYFeSwQ=; b=ltmgAZj03Mi3j5jfiITbWlHXP9otcg4no2C0NoBeXNfsZoYBIAc8Ql4erKyVzePNGc o0DwAgENUV/6utp6m/ESgj7lBTb6ejTgTuV9Ctyl9EY7muVQl/CrKw+fsr0/C++31+uJ Wk2NGw6ns3hOzCeWu9nKtCDI+gGe+JZrunBNVydPsic6JFDI9jxIzgpu6OPKHNc3Dnom X5X1tg3KeVSMAzQOhFiDtpCuDlcf+tBnazG8qedjPdYK8GPe6fBY0TQWpbGGWk+uG2Yc uOECR6lJ15FJeOeCjH1XvbU1EFG4pIWjigCXU0Y9wGPneZBVTiVpscNSA6FKLS8j7Hp1 q7Vw== MIME-Version: 1.0 X-Received: by 10.152.88.5 with SMTP id bc5mr516627lab.81.1370536294925; Thu, 06 Jun 2013 09:31:34 -0700 (PDT) Received: by 10.112.164.65 with HTTP; Thu, 6 Jun 2013 09:31:34 -0700 (PDT) X-Originating-IP: [77.228.5.145] In-Reply-To: <99A37B1BAC174809801AB928F07F4F46@Leszek> References: <20130606083116.GA23658@savin> <99A37B1BAC174809801AB928F07F4F46@Leszek> Date: Thu, 6 Jun 2013 18:31:34 +0200 Message-ID: From: =?ISO-8859-1?Q?Jorge_Tim=F3n?= To: Leszek Rychlewski Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQmebQQZyRfdCkOD4Dbsz4YzihLzuWgLnJhk+DnI6vKfoaxqLMSQJp4FbAv5PQXNt6KzzlKr X-Spam-Score: 0.0 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. X-Headers-End: 1UkdUb-0006sV-A4 Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Revocability with known trusted escrow services? X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 06 Jun 2013 16:56:55 -0000 P2SH with 2 of 3: the payer, recipient and a trusted third party. It is explained here: https://en.bitcoin.it/wiki/Contracts#Example_2:_Escrow_and_dispute_mediatio= n Nothing can be done at the protocol level if you want it to remain p2p. Much like the tainted coins stuff. Maybe offtopic but I disliked what everyone but Alan said in that bitcoin2013 "security panel" about it. Well, I didn't like several claims on that panel... On 6/6/13, Leszek Rychlewski wrote: > Transactions with cash are even less revocable (there is no negative cash > balance while a btc wallet can have a negative balance) so it looks like > the > authorities are exploiting differences between crypto currencies and the > banking system as an excuse to prosecute members of the new industry. > > Collecting arguments against such accusations should suffice [but I like > the > maturation concept for dedicated accounts/transactions :-)]. > > Leszek > > > -------------------------------------------------------------------------= ----- > How ServiceNow helps IT people transform IT departments: > 1. A cloud service to automate IT design, transition and operations > 2. Dashboards that offer high-level views of enterprise services > 3. A single system of record for all IT processes > http://p.sf.net/sfu/servicenow-d2d-j > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > --=20 Jorge Tim=F3n http://freico.in/