summaryrefslogtreecommitdiff
path: root/44/ae5812ee12e710bf6d32c488a7cd9a04d9e026
blob: 09fec25c79a62d4fd472620d422269361a1faf80 (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
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1WLbhm-0006TT-Bm
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 17:03:34 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.128.180 as permitted sender)
	client-ip=209.85.128.180; envelope-from=mh.in.england@gmail.com;
	helo=mail-ve0-f180.google.com; 
Received: from mail-ve0-f180.google.com ([209.85.128.180])
	by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1WLbhl-0004UT-F5
	for bitcoin-development@lists.sourceforge.net;
	Thu, 06 Mar 2014 17:03:34 +0000
Received: by mail-ve0-f180.google.com with SMTP id jz11so2868177veb.39
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 06 Mar 2014 09:03:28 -0800 (PST)
MIME-Version: 1.0
X-Received: by 10.58.201.5 with SMTP id jw5mr6032267vec.6.1394125407933; Thu,
	06 Mar 2014 09:03:27 -0800 (PST)
Sender: mh.in.england@gmail.com
Received: by 10.52.24.38 with HTTP; Thu, 6 Mar 2014 09:03:27 -0800 (PST)
In-Reply-To: <CALDj+BZE1KtMGpMH3UHtxjN2vXxu39o_hAWPdg==KLsWpe1zqA@mail.gmail.com>
References: <CANEZrP3w9c_UX3dd+7LdWNXCEwjnAG+bYWxqKYo_fzakWQu=Bg@mail.gmail.com>
	<CALDj+BZE1KtMGpMH3UHtxjN2vXxu39o_hAWPdg==KLsWpe1zqA@mail.gmail.com>
Date: Thu, 6 Mar 2014 18:03:27 +0100
X-Google-Sender-Auth: wKQ6aIxNUPoMrrN_Lo7PH9fChd0
Message-ID: <CANEZrP1Rwk6BnY79+RWontgK7Q1AFu3B191uJ1d80xAhaG1AgA@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Alex Kotenko <alexykot@gmail.com>
Content-Type: multipart/alternative; boundary=047d7bd6aea2b65b3404f3f31d7e
X-Spam-Score: -0.5 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1WLbhl-0004UT-F5
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Instant / contactless payments
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 06 Mar 2014 17:03:34 -0000

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

Thanks Alex!

About the video - I'm curious how your device is better than just a regular
tablet. Could you give us the elevator pitch? :)

On Thu, Mar 6, 2014 at 3:39 PM, Alex Kotenko <alexykot@gmail.com> wrote:

> I mean - if with Bitcoin v0.9 transaction fees will become really
> floating, and it should eventually reach equilibrium that will reflect some
> real world value. Probably a tiny value, but probably also rather stable
> value. So confirmationless payment cap may be defined as
> <current_average_transaction_fee>x10000.
>

I guess fees will wander up and down depending on system load rather than
real world value - but maybe you're right. That said, all wallets sync
exchange rates automatically already.

In some Star Trek future, perhaps we would want Bitcoin to be independent
of other value units. But I'm not convinced such a world will ever exist.
Arguably, a stable currency would slowly become worth more over time in
line with economic growth. But then for stable prices you would need
something like a fake currency that was "backed by" (really: represented
by) a basket of goods. Otherwise over time your rent would go up in real
terms, for good real reason.

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

<div dir=3D"ltr">Thanks Alex!<div><br></div><div>About the video - I&#39;m =
curious how your device is better than just a regular tablet. Could you giv=
e us the elevator pitch? :)</div><div class=3D"gmail_extra"><br><div class=
=3D"gmail_quote">
On Thu, Mar 6, 2014 at 3:39 PM, Alex Kotenko <span dir=3D"ltr">&lt;<a href=
=3D"mailto:alexykot@gmail.com" target=3D"_blank">alexykot@gmail.com</a>&gt;=
</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">
<div dir=3D"ltr"><div style=3D"font-family:&#39;courier new&#39;,monospace;=
color:rgb(0,51,0)">I mean - if with Bitcoin v0.9 transaction fees will beco=
me really floating, and it should eventually reach equilibrium that will re=
flect some real world value. Probably a tiny value, but probably=C2=A0also=
=C2=A0rather stable value. So confirmationless payment cap may be defined a=
s &lt;current_average_transaction_fee&gt;x10000.</div>
</div></blockquote><div><br></div><div>I guess fees will wander up and down=
 depending on system load rather than real world value - but maybe you&#39;=
re right. That said, all wallets sync exchange rates automatically already.=
</div>
<div><br></div><div>In some Star Trek future, perhaps we would want Bitcoin=
 to be independent of other value units. But I&#39;m not convinced such a w=
orld will ever exist. Arguably, a stable currency would slowly become worth=
 more over time in line with economic growth. But then for stable prices yo=
u would need something like a fake currency that was &quot;backed by&quot; =
(really: represented by) a basket of goods. Otherwise over time your rent w=
ould go up in real terms, for good real reason.</div>
</div></div></div>

--047d7bd6aea2b65b3404f3f31d7e--