public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: "Jorge Timón" <jtimon@monetize.io>
To: Leszek Rychlewski <leszek@bioinfo.pl>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Revocability with known trusted escrow services?
Date: Thu, 6 Jun 2013 18:31:34 +0200	[thread overview]
Message-ID: <CAC1+kJMtt5JWULMUDqyVVQrdOB+2NEnG3pez6qpeRvfwWsrHmQ@mail.gmail.com> (raw)
In-Reply-To: <99A37B1BAC174809801AB928F07F4F46@Leszek>

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_mediation

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 <leszek@bioinfo.pl> 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
>


-- 
Jorge Timón

http://freico.in/



  reply	other threads:[~2013-06-06 16:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-06  0:19 [Bitcoin-development] Revocability with known trusted escrow services? Peter Vessenes
2013-06-06  0:34 ` Alan Reiner
2013-06-06  1:06 ` Melvin Carvalho
2013-06-06  8:31 ` Peter Todd
2013-06-06  9:01   ` Leszek Rychlewski
2013-06-06 16:31     ` Jorge Timón [this message]
2013-06-06  9:03 ` Mike Hearn
2013-06-06 18:18 ` Mark Friedenbach
2013-06-06 22:22 ` Melvin Carvalho
2013-06-07  5:46   ` Caleb James DeLisle

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAC1+kJMtt5JWULMUDqyVVQrdOB+2NEnG3pez6qpeRvfwWsrHmQ@mail.gmail.com \
    --to=jtimon@monetize.io \
    --cc=bitcoin-development@lists.sourceforge.net \
    --cc=leszek@bioinfo.pl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox