summaryrefslogtreecommitdiff
path: root/53/69b1cfcaa99957b236e07f75e8c5dccf070d9c
blob: 122ce0a8b2cfd1cd89d4c57f6bdca211a1d18c07 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
Return-Path: <benjamin.l.cordes@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id B753689D
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  8 Aug 2015 09:24:19 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-oi0-f43.google.com (mail-oi0-f43.google.com
	[209.85.218.43])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DB80A1A8
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat,  8 Aug 2015 09:24:18 +0000 (UTC)
Received: by oiev193 with SMTP id v193so36574331oie.3
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Sat, 08 Aug 2015 02:24:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=UfMRYeD3EgxuwOqOGHhodHusw0TiVJWcV1KHdUWhoOw=;
	b=XwfCmqG4vAXlIgWQzQTPtJ3xczXGdhTaf605sszO1BZIxdt/G1ddr0d/BBRO/CYv34
	pZ101PU3/SovYYy/uYyLOEnPSbpPBFdWy9yylNdPz3M3Vz9i4zMqvpxPNupespSeKqPv
	b85YUM0NyzxCfRZxYYjtgNelQAY6pKIT7mWlmZoEC09sPnk5jXRb3dnZrePYbjmYUiFa
	FBhGSiuMAR1kUA2wz5v67GdQxCIa7jKE2IqmyyycNVloU8ACBLPgzBbWveY1JyLKehXi
	43HPC4fJUEJiRz55lkTERexpcguNJ+3aSCYdRTHFneOwa2rHaNGx+Q2Ofm2o3Geho1Gt
	dNkw==
MIME-Version: 1.0
X-Received: by 10.202.179.87 with SMTP id c84mr10437154oif.110.1439025858239; 
	Sat, 08 Aug 2015 02:24:18 -0700 (PDT)
Received: by 10.202.224.212 with HTTP; Sat, 8 Aug 2015 02:24:18 -0700 (PDT)
In-Reply-To: <20150808085451.4689995.38052.4163@thomaszander.se>
References: <8185694.hShCHQnpze@coldstorage>
	<CALqxMTHpXymxg6ATcMM3gm73gww5tznzNsY5quNbRpzsnxS53g@mail.gmail.com>
	<20150808085451.4689995.38052.4163@thomaszander.se>
Date: Sat, 8 Aug 2015 11:24:18 +0200
Message-ID: <CAOoPuRYk_R+kyfyrROcL8y9Bdfq7ufsyXSH_Uva2GPGcK_jwkA@mail.gmail.com>
From: Benjamin <benjamin.l.cordes@gmail.com>
To: Thomas Zander <thomas@thomaszander.se>
Content-Type: multipart/alternative; boundary=001a113cd1f41a6533051cc95191
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
	smtp1.linux-foundation.org
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] trust
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
	<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Sat, 08 Aug 2015 09:24:19 -0000

--001a113cd1f41a6533051cc95191
Content-Type: text/plain; charset=UTF-8

>> The point was NOT to trust no-one, the point was to trust everyone, but
keep everyone honest by keeping the ledger open and publicly available.

Trust takes many different forms and is not a binary function. You trust a
surgeon to do an operation and a pilot to fly a jet, but not vice versa. To
trust someone explicitly, you need to know who they are. Most social
structures work without explicit identity and they still function quite
well. For example companies are mostly anonymous to the consumer - if you
buy something in a shop you trust a chain of people producing that good. A
priori there is little reason to trust others, but rather that trust is
already developed through social institutions. Money is one such
institution with specific trust problems, and the history of money is
indeed a very good way to study these problems. Unfortunately in Bitcoin
development such insights are rare to find.

Lightning assumes explicit trust and ID - much like Ripple. That's not
going to work, and I'm surprised that someone with basic knowledge of
crypto doesn't see this problem. Having explicit counter-parties is
something very different from Bitcoin where the entity doing transactions
verification is unknowable and changes all the time. Users of Bitcoin trust
nodes doing the verification because they know it is in their best interest
to be honest. Neither Sidechains nor LT have preserve that important
property, and so IMO there are no good proposals to make Bitcoin scale (if
that is possible at all).

On Sat, Aug 8, 2015 at 10:54 AM, Thomas Zander via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I didn't say off-chain, and gave an example of on-chain usecase with
> trusted middleman.
>
> So, no, that's not what I meant.
>
> Sent on the go, excuse the brevity.
>   Original Message
> From: Adam Back
> Sent: Saturday, 8 August 2015 09:50
> To: Thomas Zander
> Cc: Bitcoin Dev
> Subject: Re: [bitcoin-dev] trust
>
> If you are saying that some people are happy trusting other people,
> and so would be perfectly fine with off-chain use of Bitcoin, then we
> agree and I already said that off-chain use case would be a
> constructive thing for someone to improve scale and interoperability
> of in the post you are replying to. However that use case is not a
> strong argument for weakening Bitcoin's security to get to more scale
> for that use case.
>
> In a world where we could have scale and decentralisation, then of
> course it would be nice to provide people with that outlook more
> security than they seem to want. And sometimes people dont understand
> why security is useful until it goes wrong, so it would be a useful
> thing to do. (Like insurance, your money being seized by paypal out
> of the blue etc). And indeed providing security at scale maybe
> possible with lightning like protocols that people are working on.
>
> Adam
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>

--001a113cd1f41a6533051cc95191
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><span style=3D"font-size:13px">&gt;&gt; The point was NOT =
to trust no-one, the point was to trust everyone, but keep=C2=A0</span><spa=
n style=3D"font-size:13px">everyone honest by keeping the ledger open and p=
ublicly available.</span><br style=3D"font-size:13px"><div><span style=3D"f=
ont-size:13px"><br></span></div><div>Trust takes many different forms and i=
s not a binary function. You trust a surgeon to do an operation and a pilot=
 to fly a jet, but not vice versa. To trust someone explicitly, you need to=
 know who they are. Most social structures work without explicit identity a=
nd they still function quite well. For example companies are mostly anonymo=
us to the consumer - if you buy something in a shop you trust a chain of pe=
ople=C2=A0producing that good. A priori there is little reason to trust oth=
ers, but rather that trust is already developed through social institutions=
. Money is one such institution with specific trust problems, and the histo=
ry of money is indeed a very good way to study these problems. Unfortunatel=
y in Bitcoin development such insights are rare to find.</div><div><br></di=
v><div>Lightning assumes explicit trust and ID - much like Ripple. That&#39=
;s not going to work, and I&#39;m surprised that someone with basic knowled=
ge of crypto doesn&#39;t see this problem. Having explicit counter-parties =
is something very different from Bitcoin where the entity doing transaction=
s verification is unknowable and changes all the time. Users of Bitcoin tru=
st nodes doing the verification because they know it is in their best inter=
est to be honest. Neither Sidechains nor LT have preserve that important pr=
operty, and so IMO there are no good proposals to make Bitcoin scale (if th=
at is possible at all).</div></div><div class=3D"gmail_extra"><br><div clas=
s=3D"gmail_quote">On Sat, Aug 8, 2015 at 10:54 AM, Thomas Zander via bitcoi=
n-dev <span dir=3D"ltr">&lt;<a href=3D"mailto:bitcoin-dev@lists.linuxfounda=
tion.org" target=3D"_blank">bitcoin-dev@lists.linuxfoundation.org</a>&gt;</=
span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex">I didn&#39;t say off-chain, =
and gave an example of on-chain usecase with trusted middleman.<br>
<br>
So, no, that&#39;s not what I meant.<br>
<br>
Sent=C2=A0on=C2=A0the=C2=A0go,=C2=A0excuse=C2=A0the=C2=A0brevity.=C2=A0<br>
=C2=A0 Original Message =C2=A0<br>
From: Adam Back<br>
Sent: Saturday, 8 August 2015 09:50<br>
To: Thomas Zander<br>
Cc: Bitcoin Dev<br>
Subject: Re: [bitcoin-dev] trust<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
If you are saying that some people are happy trusting other people,<br>
and so would be perfectly fine with off-chain use of Bitcoin, then we<br>
agree and I already said that off-chain use case would be a<br>
constructive thing for someone to improve scale and interoperability<br>
of in the post you are replying to. However that use case is not a<br>
strong argument for weakening Bitcoin&#39;s security to get to more scale<b=
r>
for that use case.<br>
<br>
In a world where we could have scale and decentralisation, then of<br>
course it would be nice to provide people with that outlook more<br>
security than they seem to want. And sometimes people dont understand<br>
why security is useful until it goes wrong, so it would be a useful<br>
thing to do. (Like insurance, your money being seized by paypal out<br>
of the blue etc). And indeed providing security at scale maybe<br>
possible with lightning like protocols that people are working on.<br>
<br>
Adam<br>
_______________________________________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.org/mail=
man/listinfo/bitcoin-dev</a><br>
</div></div></blockquote></div><br></div>

--001a113cd1f41a6533051cc95191--