summaryrefslogtreecommitdiff
path: root/a6/8b67d3ca1cf921e12ed2aa872e800a093ec82a
blob: 9a518af8249e1436ba26763d1b58a79fc0e74aa3 (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
Return-Path: <vincent.truong@procabiak.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
	[172.17.192.35])
	by mail.linuxfoundation.org (Postfix) with ESMTPS id 21027360
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 24 Jul 2015 14:37:17 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-ig0-f179.google.com (mail-ig0-f179.google.com
	[209.85.213.179])
	by smtp1.linuxfoundation.org (Postfix) with ESMTPS id 8F79B8B
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 24 Jul 2015 14:37:16 +0000 (UTC)
Received: by igbpg9 with SMTP id pg9so37500699igb.0
	for <bitcoin-dev@lists.linuxfoundation.org>;
	Fri, 24 Jul 2015 07:37:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=procabiak.com; s=procabiakindustries;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type;
	bh=1sUK5u66Mo2n8480n8vHskydC1pcR01RZEcIjs+l1v4=;
	b=RJ5ysVagrhvwqX86sFOKR34+6KPGpAnBp8KEE0avNe6/fw3oe2gWjS1OzNDgYN1nNf
	z7jGlTIe9lEhr1Ml2krj6iCmen2408G16upBlf+djKfH4oi52YLlaSKiSon1O/ScPVqb
	FJ1n8bSIktUFrHwxJ9lhmBHOYdpnvd8z5mjqI=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
	d=1e100.net; s=20130820;
	h=x-gm-message-state:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:cc:content-type;
	bh=1sUK5u66Mo2n8480n8vHskydC1pcR01RZEcIjs+l1v4=;
	b=gTbGZzXrOq8dmyc+UwovtvuA4Tzc3lnydccFnSVW7uo4e5oGOrcVuHDqLZL2iYFFRa
	EGZV+GHvD0gkhOk8OG/KCZvA6KbhAGVqhE/sxHfEde4/ZBm0HZtxR9TM+I2hDBbOF6wu
	izqxKZHcQKhFoYGfvWcfmy77RzXtLGDTC9dYpgjVHt0KVWVe8H9MY2afKsu8GzFH/acv
	ZOz6WCdwKk+qXl6JxwG+RUNNCSa1AMePz0Iz9CvunJ8WLJmrhcXDO7AImVyZ71S/jF20
	ARx2wXlwXrssCrDh4cUZcN81AgICdp+CSYQ6x+ZhPft0zhVAnYBz48EjfmqMoPEPrqFm
	5g4Q==
X-Gm-Message-State: ALoCoQnHZY61KW3r4r2lWOMO1Y98Cv8w6uiAOwqezHttR2XWd8GcKnD8s8K0joa0/eJHbdVesIfa
MIME-Version: 1.0
X-Received: by 10.50.66.167 with SMTP id g7mr7904482igt.22.1437748635909; Fri,
	24 Jul 2015 07:37:15 -0700 (PDT)
Received: by 10.36.68.11 with HTTP; Fri, 24 Jul 2015 07:37:15 -0700 (PDT)
X-Originating-IP: [14.202.127.219]
Received: by 10.36.68.11 with HTTP; Fri, 24 Jul 2015 07:37:15 -0700 (PDT)
In-Reply-To: <CABm2gDqK0qd_JNHCUrnz4L1axG99i9=M7DjCQWatE3Lf0HOiyA@mail.gmail.com>
References: <l.com@mac.com> <D472C05D-7164-4ED1-B571-94415AD8E60F@gmail.com>
	<346D4CE0-E00D-4ABB-B131-EFA1416CB20C@me.com>
	<29363BE6-72A7-4D06-A974-C52BA12FD8BD@gmail.com>
	<55FFBC8F-A3C9-4109-89C7-AC359FBBD478@me.com>
	<4734381C-2000-4D9B-9099-DDE3D38D64A3@me.com>
	<DEF9C610-2FBC-40C1-9AFA-9E91903C7F96@petertodd.org>
	<DFA3CCE4-52F7-4D63-8982-2EB133AB6EAA@me.com>
	<B8F9DE4B-A8AA-490D-991B-11C28B2AA527@gmail.com>
	<D7EE14EC-B36D-43F2-8CEC-B63443FBBCA8@me.com>
	<0E15E07E-E21C-4541-869A-3C34CBA35774@gmail.com>
	<9AC88C7C-4BA4-4DF2-913F-9DC6874BD19D@me.com>
	<83982C1D-4FE6-4A5C-BC93-BFBD9756F3D2@gmail.com>
	<COL131-DS24D730A430CE77D648AE9CCD810@phx.gbl>
	<55B1FBCE.1080002@jonasschnelli.ch>
	<CABm2gDqK0qd_JNHCUrnz4L1axG99i9=M7DjCQWatE3Lf0HOiyA@mail.gmail.com>
Date: Sat, 25 Jul 2015 00:37:15 +1000
Message-ID: <CACrzPenbkh86bW9GQe1M4Zt1OxDTQNeMU6osatRDEvcwOyxHAg@mail.gmail.com>
From: Vincent Truong <vincent.truong@procabiak.com>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Content-Type: multipart/alternative; boundary=047d7bdca61ab85706051b9ff031
X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,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@lists.linuxfoundation.org
Subject: Re: [bitcoin-dev] Bitcoin, Perceptions, and Expectations
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: Fri, 24 Jul 2015 14:37:17 -0000

--047d7bdca61ab85706051b9ff031
Content-Type: text/plain; charset=UTF-8

"Fast transactions"
Fast transactions implies it is slower than Visa, and Visa is 'instant' by
comparison from the spender's POV. Bitcoin is still very instant because
wallets still send notifications/pings when transactions are first seen,
not when it goes into a block. We shouldn't mislead people into thinking a
transaction literally takes 10 minutes to travel the globe.

Maybe this feels like PR speak. But being too humble about Bitcoin's
attributes isn't a good idea either.

If we're going to look at perception, image and expectations, perhaps we
can start to look at redefining some terminology too. Like confirmations,
which is an arbitrary concept. Where possible we should describe it with
finance terminology.

"0 conf transaction"
0 conf is the 'transaction' - just the act of making an exchange. It
doesn't imply safe and I believe using the word 'settle' in place of
confirmations will automatically click with merchants.

"1st conf"
A 'confirmation' is a 'settlement'. If it is 'settled', it implies final
(except by court order), whereas confirmation usually means 'ah, I've seen
it come through'. I rarely hear any sales clerk call credit card
transactions confirmed. More often you will hear 'approved' instead.
Although 1st conf can be overtaken, so...

"n confirmations"
This term can probably stay since I can't come up with a better word.
Settlements only happen once, putting a number next to it breaks the
meaning of the word. "Settled with 4 confirmations" seems pretty clear.
Alternatively I think instead of displaying a meaningless number we ought
to go by a percentage (the double spend improbability) and go by
'confidence'. "Settled with 92% confidence." Or we can pick an arbitrary
number like 6 and use 'settling...' and 'settled' when reached.

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

<p dir=3D"ltr"><br>
&quot;Fast transactions&quot;<br>
Fast transactions implies it is slower than Visa, and Visa is &#39;instant&=
#39; by comparison from the spender&#39;s POV. Bitcoin is still very instan=
t because wallets still send notifications/pings when transactions are firs=
t seen, not when it goes into a block. We shouldn&#39;t mislead people into=
 thinking a transaction literally takes 10 minutes to travel the globe.</p>
<p dir=3D"ltr">Maybe this feels like PR speak. But being too humble about B=
itcoin&#39;s attributes isn&#39;t a good idea either.</p>
<p dir=3D"ltr">If we&#39;re going to look at perception, image and expectat=
ions, perhaps we can start to look at redefining some terminology too. Like=
 confirmations, which is an arbitrary concept. Where possible we should des=
cribe it with finance terminology.</p>
<p dir=3D"ltr">&quot;0 conf transaction&quot;<br>
0 conf is the &#39;transaction&#39; - just the act of making an exchange. I=
t doesn&#39;t imply safe and I believe using the word &#39;settle&#39; in p=
lace of confirmations will automatically click with merchants.</p>
<p dir=3D"ltr">&quot;1st conf&quot;<br>
A &#39;confirmation&#39; is a &#39;settlement&#39;. If it is &#39;settled&#=
39;, it implies final (except by court order), whereas confirmation usually=
 means &#39;ah, I&#39;ve seen it come through&#39;. I rarely hear any sales=
 clerk call credit card transactions confirmed. More often you will hear &#=
39;approved&#39; instead. Although 1st conf can be overtaken, so...</p>
<p dir=3D"ltr">&quot;n confirmations&quot;<br>
This term can probably stay since I can&#39;t come up with a better word. S=
ettlements only happen once, putting a number next to it breaks the meaning=
 of the word. &quot;Settled with 4 confirmations&quot; seems pretty clear. =
Alternatively I think instead of displaying a meaningless number we ought t=
o go by a percentage (the double spend improbability) and go by &#39;confid=
ence&#39;. &quot;Settled with 92% confidence.&quot; Or we can pick an arbit=
rary number like 6 and use &#39;settling...&#39; and &#39;settled&#39; when=
 reached.</p>

--047d7bdca61ab85706051b9ff031--