From: "Jorge Timón" <jtimon@jtimon.cc>
To: Thomas Zander <thomas@thomaszander.se>
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] trust
Date: Mon, 10 Aug 2015 22:17:52 +0200 [thread overview]
Message-ID: <CABm2gDrJH8-6VPp1Lk4ueJA2ShOU+evTgK-S1zNjuqN8h8Je+Q@mail.gmail.com> (raw)
In-Reply-To: <1725491.c810VbMBxP@coldstorage>
On Sat, Aug 8, 2015 at 2:37 PM, Thomas Zander via bitcoin-dev
<bitcoin-dev@lists.linuxfoundation.org> wrote:
> On Saturday 8. August 2015 12.54.36 Adam Back wrote:
>> On 8 August 2015 at 09:54, Thomas Zander <thomas@thomaszander.se> wrote:
>> > I didn't say off-chain, and gave an example of on-chain usecase with
>> > trusted middleman.
>> That's basically the definition of off-chain. When we say MtGox or
>> coinbase etc are off-chain transactions, that is because a middle man
>> has the private keys to the coins and gave you an IOU of some kind.
>
> I'm so sorry to have to correct you again, and please don't feel bad about
> misreading my post twice.
>
> Sending something to another Bitcoin on-chain user is really on-chain. Please
> believe me when I say that I actually understand my own example.
Adam, I think he means a multisig escrow transaction where the escrow
is trusted by both parties, and other examples like that.
But I don't see how that is relevant, allowing trust to be involved in
different ways is a feature, but it's optional.
I think the point "you don't need to trust anyone to use Bitcoin" remains.
next prev parent reply other threads:[~2015-08-10 20:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-08 6:10 [bitcoin-dev] trust Thomas Zander
2015-08-08 8:39 ` Adam Back
2015-08-08 8:54 ` Thomas Zander
2015-08-08 9:24 ` Benjamin
2015-08-08 11:08 ` s7r
2015-08-08 12:01 ` Benjamin
2015-08-11 4:17 ` Joseph Poon
2015-08-08 11:59 ` Milly Bitcoin
2015-08-08 11:54 ` Adam Back
2015-08-08 12:37 ` Thomas Zander
2015-08-10 20:17 ` Jorge Timón [this message]
2015-08-10 20:43 ` Milly Bitcoin
2015-08-10 21:43 ` Thomas Zander
2015-08-08 9:05 ` Venzen Khaosan
2015-08-10 21:45 ` Gregory Maxwell
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=CABm2gDrJH8-6VPp1Lk4ueJA2ShOU+evTgK-S1zNjuqN8h8Je+Q@mail.gmail.com \
--to=jtimon@jtimon.cc \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=thomas@thomaszander.se \
/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